Azure Functions deployment slots Swap failed

ELSONBATY Mahmoud 20

I had one and only one time successful swap worked staging to prod.

for any further swapping attempt, I'm getting the below internal server 500 error with details:

Swap failed. Details: System.ServiceModel.Web.WebFaultException`1[Microsoft.Web.Hosting.Administration.ErrorEntity]: Bad Request (Fault Detail is equal to Code: BadRequest, ExtendedCode: Storage access failed. WEBSITE_CONTENTAZUREFILECONNECTIONSTRING or WEBSITE_CONTENTSHARE appsetting is missing.

any idea on how to resolve this problem?

Swathi Dhanwada 18,781 Reputation points Microsoft Employee

2024-06-04T03:15:29.3633333+00:00
@ELSONBATY Mahmoud Here are some of things you need consider when attempting the swap. Kindly check and try to perform the swap and let me know how it goes.

Every function app requires a storage account to operate. If that account is deleted, your functions won't work.Either AzureWebJobsStorage or WEBSITE_CONTENTAZUREFILECONNECTIONSTRING contains the name of your storage account as part of a connection string. Search for your storage account in the Azure portal to see whether it still exists. If it has been deleted, re-create the storage account and replace your storage connection strings. Your function code is lost, and you need to redeploy it.

In the preceding step, if you can't find a storage account connection string, it was likely deleted or overwritten. Deleting application settings most commonly happens when you're using deployment slots or Azure Resource Manager scripts to set application settings. Required application settings

Required:

AzureWebJobsStorage

Required for Elastic Premium and Consumption plan functions:

WEBSITE_CONTENTAZUREFILECONNECTIONSTRING

WEBSITE_CONTENTSHARE

For more information, see App settings reference for Azure Functions. Kindly note,

Don't check slot setting for any of these settings. If you swap deployment slots, the function app breaks.

Don't modify these settings as part of automated deployments.

These settings must be provided and valid at creation time. An automated deployment that doesn't contain these settings results in a function app that won't run, even if the settings are added later.
ELSONBATY Mahmoud 20 Reputation points

2024-06-04T18:19:08.81+00:00
Function apps in prod or staging are working ..that means the linked storage is not deleted.

Swap worked only at the first time .. after that the swap never worked.

I checked the environment variables and they don't include WEBSITE_CONTENTAZUREFILECONNECTIONSTRING or WEBSITE_CONTENTSHARE

I don't use templates ..I was performing swap from the portal.
Swathi Dhanwada 18,781 Reputation points Microsoft Employee

2024-06-05T11:36:15.81+00:00

@ELSONBATY Mahmoud Thanks for the information. Can you please let me know on which plan are your function apps running?
ELSONBATY Mahmoud 20 Reputation points

2024-06-05T13:32:42.5166667+00:00

consumption plan

Share via

Azure Functions deployment slots Swap failed

Your answer