+1
Not exactly the greatest of confidence to see such problems hang around for such a long time. You all are making money over there with all the money we're paying you, right? :P
https://learn.microsoft.com/answers/answers/690772/view.html
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
When I attempt to add a deployment slot to a function app, I get this error:
Failed to create slot 'stage': Required parameter AccessKey is missing.
Any ideas on what would cause this? I don't see any method of providing an access key from the add slot screen.
+1
Not exactly the greatest of confidence to see such problems hang around for such a long time. You all are making money over there with all the money we're paying you, right? :P
https://learn.microsoft.com/answers/answers/690772/view.html
We had the exact same error when try to cloning into a new deployment slot.
Since AccessKey would normally only be used in Storage Account, we looked around and found
Settings -> Configuration -> Path mappings -> It was mounting a storage account (Currenly only avaliable in Linux App Service Plan)
Since we are not using this mount, we removed it and tried cloning again.
And it worked this time. But yes, I agree someone need to open up a ticket with MS to have this fixed permanantly.
We are also facing this issue. When trying to create a deployment slot, the creation fails with "Required parameter AccessKey is missing." from 1) Azure Portal, 2) Azure Portal Cloudshell and 3) local PS (using az cli tool).
Is there any status update?
we are seeing the same issue with a Webapp for containers, when creating another deployment slot
If someone is facing a similar issue feel free to tag me or create a support ticket. This issue needs to be looked at from the configuration end of the function app. Look's like there can be some default configuration that might be removed for the function app.
In multiple instances the issue could be that the AccessKey on the storage account mounted to the app services was have flagged null at our end. You could update the value in resource explorer or redeploy without the storage mount and remount it after deployment.