This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 81%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENV%3C/text%3E%3C/svg%3E)
My Azure function has a staging and production slot. Both have vnet enabled, and have WEBSITE_CONTENTOVERVNET=1 & vnetRouteAllEnable=true. Deployment of the zip package to the staging and production slots works, and the function operates properly in both slots.
On swapping the staging slot to the production slot, I receive the following error: Failed to complete swap between slot 'staging' and slot 'production'. Error: {"_body":"{\"Code\":\"InternalServerError\",\"Message\":\"There was an unexpected error swapping slots 'staging' and 'production' for site 'qn-dev-we-fnc-exceptionhandling-resolve-1-0(staging)'. Please try to cancel your swap operation
The check swap operations log shows the following detailed error: 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. Storage volume is currently in R/O mode, Message: 04234).
Turning off the vnet fixes the issue. Any help would be appreciated!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 33%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
@Niels van der Kaap , could you please enable the below setting in app settings and see if it makes any difference?
WEBSITE_DNS_SERVER 168.63.129.16
https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#website_dns_server
That does not make a difference. I've tried this with and without private endpoints for blob and file in the storage account. Below is a listing of all settings for the staging and production slots from the bicep template:
'AzureWebJobsSecretStorageType': 'blob'
'StorageConnectionString': 'DefaultEndpointsProtocol=https;AccountName=${infra.storageAccount.name};AccountKey=${listKeys(infra.storageAccount.id, '2015-05-01-preview').key1}'
'APPINSIGHTS_INSTRUMENTATIONKEY': reference(resourceId(infra.environment.resourceGroupName, 'Microsoft.Insights/components', '${infra.environment.resourcePrefix}-appins'), '2014-04-01').InstrumentationKey
'AzureWebJobsStorage': 'DefaultEndpointsProtocol=https;AccountName=${infra.storageAccount.name};AccountKey=${listKeys(infra.storageAccount.id, '2015-05-01-preview').key1}'
'WEBSITE_FUNCTIONS_ARMCACHE_ENABLED': '0'
'IsDeveloperMode': 'false'
'FUNCTIONS_EXTENSION_VERSION': '~3'
'WEBSITE_ADD_SITENAME_BINDINGS_IN_APPHOST_CONFIG': '1'
'WEBSITE_RUN_FROM_PACKAGE': '1'
'WEBSITE_CONTENTOVERVNET': '1'
'WEBSITE_CONTENTAZUREFILECONNECTIONSTRING': 'DefaultEndpointsProtocol=https;AccountName=${infra.storageAccount.name};AccountKey=${listKeys(infra.storageAccount.id, '2015-05-01-preview').key1}'
'WEBSITE_DNS_SERVER': '168.63.129.16'
'WEBSITE_VNET_ROUTE_ALL': '1'
@Niels van der Kaap Did you find any solution for this? I am facing exactly same issue
My issue was fixed by switching to internal storage. I removed the WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING app settings.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 43%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELC%3C/text%3E%3C/svg%3E)
I tried to remove these 2 settings from
However, InternalServerError still happened during swap the deployment slot
This problem only happens if the storage account is set to blocked public access and restricted VNET/IP.
Anyone has idea on resolution?