Azure SWA giving HTTP 500 Internal Server Error

Question

Azure SWA giving HTTP 500 Internal Server Error

Benjamin Hubert 20

This morning one of our Azure SWA started giving us internal server errors.

This is on the main environment, all the preview environments on the same SWA still work.

We did not do any deployments this morning prior to this happening.

We have tried re-deploying, we have tried splitting all traffic to the preview site, but none of those worked, we still get internal server error when going to our custom domain.

Please help get this online again.

Here's the JSON cfg of the SWA that's failing:

{
    "apiVersion": "2024-11-01",
    "id": "/subscriptions/<my tenant>/resourceGroups/<my resource group>/providers/Microsoft.Web/staticSites/<my SWA>",
    "name": "<swa name>",
    "type": "microsoft.web/staticsites",
    "sku": {
        "name": "Standard",
        "tier": "Standard"
    },
    "location": "westeurope",
    "properties": {
        "defaultHostname": "<swa host name>",
        "repositoryUrl": null,
        "branch": null,
        "customDomains": [
            "<my custom domain>"
        ],
        "stableInboundIP": "51.124.12.35",
        "privateEndpointConnections": [],
        "stagingEnvironmentPolicy": "Enabled",
        "allowConfigFileUpdates": true,
        "contentDistributionEndpoint": "https://content-am2.infrastructure.1.azurestaticapps.net",
        "keyVaultReferenceIdentity": "SystemAssigned",
        "userProvidedFunctionApps": null,
        "linkedBackends": [],
        "provider": "DevOps",
        "enterpriseGradeCdnStatus": "Disabled",
        "publicNetworkAccess": null,
        "databaseConnections": [],
        "trafficSplitting": {
            "environmentDistribution": {
                "default": 100
            }
        },
        "targetResourceGroupResourceId": null,
        "trialExpirationTimeUtc": null,
        "prettyNameStatus": null,
        "prettyName": null,
        "prettyNameHostname": null,
        "backendRegion": {
            "regionName": null,
            "status": null
        },
        "stagingEnvironmentRegion": null,
        "deploymentAuthPolicy": "DeploymentToken",
        "federatedIdentityTenantId": null,
        "federatedIdentityClientId": null,
        "federatedIdentitySubscriptionId": null,
        "deploymentStorageAccountResourceId": null,
        "deploymentStorageAccountReferenceIdentity": null,
        "networkConfigurations": null
    }
}

Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-12T08:41:08.44+00:00

Hi @Benjamin Hubert

To review this thoroughly, we need some additional information. Could you please provide the details requested in the private message?
Benjamin Hubert 20 Reputation points

2025-11-12T08:56:30.57+00:00

Private message with info sent.
Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-12T10:39:12.0833333+00:00
Hi @Benjamin Hubert

Thank you for posting your question on Microsoft Q&A.

To start troubleshooting, please use the “Diagnose and solve problems” blade in your Static Web App resource from the Azure portal. This tool can help identify issues related to backend connectivity, configuration, or authentication errors.

If your Static Web App is connected to an Azure Functions API, please also verify the following:

The Function App is not experiencing cold start delays, scaling issues, or quota limits.

The Function App keys and authentication settings are valid and haven’t expired.

CORS settings are properly configured if the Static Web App communicates with the Function App.

For reference, please see Troubleshoot your Azure Static Web App documentation for detailed guidance.

Feel free to share any log snippets or error codes if the issue persists — we’ll be glad to help you further.
Benjamin Hubert 20 Reputation points

2025-11-12T10:42:52.06+00:00

@Vimal Lalani

I already did the "Diagnose and solve problems" and it was unable to help me with anything at all.

I chose "Availability and Performance" as the category in which I wanted help/troubleshooting, and the only message it showed was "Unable to fetch Static App Config. Please try again later".

If your Static Web App is connected to an Azure Functions API

It is not.
Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-14T09:13:10.0633333+00:00
Hi @Benjamin Hubert

From our call, I noticed, the Azure DevOps pipeline release is working correctly for your Static Web App in Staging and UAT, but it is not working for the Production environment of the same SWA.

To help narrow down the cause, please double-check the following:

Deployment Token

Production often uses a different deployment token than Staging/UAT.

Ensure your pipeline is using the correct Production deployment token under the SWA Deploy task.

Environment Name in Pipeline

For production you must use: --env production

or leave it blank depending on the task type.

If you explicitly set another environment name (e.g., “prod” or “Production”), the deployment will not target real Production.

Azure Static Web App Configuration

Confirm that: The Production environment is not locked, No branch filters or protected branch rules are blocking deployment.

App Service Authentication / SWA Preview Environments

If your staging/UAT point to preview environments but production is tied to a Git branch, deployment from DevOps may get ignored unless configured as standalone.

Feel free to post back if it does not resolve
Benjamin Hubert 20 Reputation points

2025-11-14T09:48:51.9666667+00:00

Alright I posted some screenshots in our private conversation so you can see that the tokens match up, and that there is nothing in the environment text box, there are no locks. We use same deployment mechanism for both our staging and production environments (deploy through release pipelines).

From our call, I noticed, the Azure DevOps pipeline release is working correctly for your Static Web App in Staging and UAT, but it is not working for the Production environment of the same SWA.

Well you watched my screen as we both saw the release "succeeding", or at least it didn't report any errors and displayed a green checkmark after running.

I'm not so sure that this is a deployment issue, I think since the deployment gets marked as a success, but we're still getting HTTP 500, it is probably some hosting runtime issue.

Did you get in contact with one of the developers on Azure SWA?
Benjamin Hubert 20 Reputation points

2025-11-14T10:01:34.2733333+00:00

Shibboleet
Shree Hima Bindu Maganti 6,120 Reputation points Microsoft External Staff Moderator

2025-11-18T16:02:52.9533333+00:00

Hi @Benjamin Hubert
Apology for delay response
Thank you for the detailed update and for providing the screenshots. I noticed during the call that your Azure DevOps release completes successfully, and both Staging and UAT environments deploy without any issues. Since the same pipeline, token, and configuration work for your other environments, but Production still returns an HTTP 500 before serving content, this supports your assessment that the issue lies with the SWA production hosting runtime for that environment.
Let me know if you have any further assistances needed.
Benjamin Hubert 20 Reputation points

2025-11-19T08:11:23.8933333+00:00

Hi and thanks for your reply.

Yes I've come to the same conclusion based on what little data I have available.

Where do we go from here? Do you have any idea of what caused this? I'm looking for some kind of confirmation that whatever caused it has been identified and fixed, and some way to get my SWA into a good state again.

Let me know if you have any further assistances needed

Yes, I need assistance in getting my SWA into a good state again (i.e. not giving 500's), and I need reassurrance that this will not happen again (both to this SWA, but also any other SWAs).
Benjamin Hubert 20 Reputation points

2025-11-21T08:04:10.04+00:00

Hello?

@Shree Hima Bindu Maganti can you confirm that you've seen my reply, and intent to actually work towards fixing my issue, rather than just acknowledging that it exists?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

2 answers

Your answer

Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-12T08:41:08.44+00:00

Hi @Benjamin Hubert

To review this thoroughly, we need some additional information. Could you please provide the details requested in the private message?
Benjamin Hubert 20 Reputation points

2025-11-12T08:56:30.57+00:00

Private message with info sent.
Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-12T10:39:12.0833333+00:00

Hi @Benjamin Hubert

Thank you for posting your question on Microsoft Q&A.

To start troubleshooting, please use the “Diagnose and solve problems” blade in your Static Web App resource from the Azure portal. This tool can help identify issues related to backend connectivity, configuration, or authentication errors.

If your Static Web App is connected to an Azure Functions API, please also verify the following:

The Function App is not experiencing cold start delays, scaling issues, or quota limits.

The Function App keys and authentication settings are valid and haven’t expired.

CORS settings are properly configured if the Static Web App communicates with the Function App.

For reference, please see Troubleshoot your Azure Static Web App documentation for detailed guidance.

Feel free to share any log snippets or error codes if the issue persists — we’ll be glad to help you further.
Benjamin Hubert 20 Reputation points

2025-11-12T10:42:52.06+00:00

@Vimal Lalani

I already did the "Diagnose and solve problems" and it was unable to help me with anything at all.

I chose "Availability and Performance" as the category in which I wanted help/troubleshooting, and the only message it showed was "Unable to fetch Static App Config. Please try again later".

If your Static Web App is connected to an Azure Functions API

It is not.
Vimal Lalani 2,400 Reputation points Microsoft External Staff Moderator

2025-11-14T09:13:10.0633333+00:00

Hi @Benjamin Hubert

From our call, I noticed, the Azure DevOps pipeline release is working correctly for your Static Web App in Staging and UAT, but it is not working for the Production environment of the same SWA.

To help narrow down the cause, please double-check the following:

Deployment Token

Production often uses a different deployment token than Staging/UAT.

Ensure your pipeline is using the correct Production deployment token under the SWA Deploy task.

Environment Name in Pipeline

For production you must use: --env production

or leave it blank depending on the task type.

If you explicitly set another environment name (e.g., “prod” or “Production”), the deployment will not target real Production.

Azure Static Web App Configuration

Confirm that: The Production environment is not locked, No branch filters or protected branch rules are blocking deployment.

App Service Authentication / SWA Preview Environments

If your staging/UAT point to preview environments but production is tied to a Git branch, deployment from DevOps may get ignored unless configured as standalone.

Feel free to post back if it does not resolve
Benjamin Hubert 20 Reputation points

2025-11-14T09:48:51.9666667+00:00

Alright I posted some screenshots in our private conversation so you can see that the tokens match up, and that there is nothing in the environment text box, there are no locks. We use same deployment mechanism for both our staging and production environments (deploy through release pipelines).

From our call, I noticed, the Azure DevOps pipeline release is working correctly for your Static Web App in Staging and UAT, but it is not working for the Production environment of the same SWA.

Well you watched my screen as we both saw the release "succeeding", or at least it didn't report any errors and displayed a green checkmark after running.

I'm not so sure that this is a deployment issue, I think since the deployment gets marked as a success, but we're still getting HTTP 500, it is probably some hosting runtime issue.

Did you get in contact with one of the developers on Azure SWA?
Benjamin Hubert 20 Reputation points

2025-11-14T10:01:34.2733333+00:00

Shibboleet
Shree Hima Bindu Maganti 6,120 Reputation points Microsoft External Staff Moderator

2025-11-18T16:02:52.9533333+00:00

Hi @Benjamin Hubert
Apology for delay response
Thank you for the detailed update and for providing the screenshots. I noticed during the call that your Azure DevOps release completes successfully, and both Staging and UAT environments deploy without any issues. Since the same pipeline, token, and configuration work for your other environments, but Production still returns an HTTP 500 before serving content, this supports your assessment that the issue lies with the SWA production hosting runtime for that environment.
Let me know if you have any further assistances needed.
Benjamin Hubert 20 Reputation points

2025-11-19T08:11:23.8933333+00:00

Hi and thanks for your reply.

Yes I've come to the same conclusion based on what little data I have available.

Where do we go from here? Do you have any idea of what caused this? I'm looking for some kind of confirmation that whatever caused it has been identified and fixed, and some way to get my SWA into a good state again.

Let me know if you have any further assistances needed

Yes, I need assistance in getting my SWA into a good state again (i.e. not giving 500's), and I need reassurrance that this will not happen again (both to this SWA, but also any other SWAs).
Benjamin Hubert 20 Reputation points

2025-11-21T08:04:10.04+00:00

Hello?

@Shree Hima Bindu Maganti can you confirm that you've seen my reply, and intent to actually work towards fixing my issue, rather than just acknowledging that it exists?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

To troubleshoot the HTTP 500 Internal Server Error you're experiencing with your Azure Static Web App (SWA), consider the following steps:

Check Application Insights: If you have Application Insights configured, check the logs for any runtime errors or exceptions that might provide more context about the internal server error. You can access this by navigating to the Application Insights instance associated with your SWA in the Azure portal.
Review Deployment Logs: Since you mentioned that you redeployed the application, review the deployment logs in your GitHub repository under the Actions tab. Look for any errors that occurred during the build and deployment process.
Validate Configuration Settings: Ensure that your configuration settings in the SWA JSON are correct. Pay special attention to the api_location and app_location settings, as incorrect paths can lead to errors.
Check for Recent Changes: Although you mentioned no deployments were made, verify if there were any changes in the environment or dependencies that could affect the application. Sometimes, external services or APIs that your app relies on may have changed.
Inspect Custom Domain Configuration: Ensure that your custom domain is correctly configured and pointing to the right SWA. If there are issues with DNS or SSL certificates, it could lead to internal server errors.
Traffic Splitting: Since you mentioned splitting traffic to the preview site, double-check that the traffic splitting configuration is set correctly and that the preview site is functioning as expected.

If these steps do not resolve the issue, consider reaching out to Azure support for further assistance.

References:

Answer 2

Shree Hima Bindu Maganti 6,120 Microsoft External Staff Moderator

Hi @Benjamin Hubert
Thanks for your Conformation. The issue with your SWA production environment has now been resolved. After investigation, the problem was not related to your deployment pipeline or code the production environment was in an unhealthy state on the platform side. The backend instance hosting that environment was refreshed and brought back into a healthy state, which cleared the HTTP 500 errors.

Your SWA is now responding normally, and you should be able to deploy and access it without issues. We will continue to monitor to ensure stability, but no further action is required on your end.

Please let me know if you see anything unexpected or if you need additional assistance.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Benjamin Hubert 20 Reputation points

2025-12-05T08:06:23.27+00:00

Very nice, it appears to be working now!

As I suspected all along, as with many cases of something getting into a bad state, it just had to be restarted.

Is there a change that we can get a button in the azure portal to automatically do this?

It would have been the first thing I would have tried (the old turning it off and on again), and would have saved countless hours.

And if this is outside of your responsibility to see to, can you pass it along to the developers of Azure SWA? Thanks!

Share via

Azure SWA giving HTTP 500 Internal Server Error

2 answers

Your answer