I created a staging deployment slot in production environment App-Service with the idea that once everything looks okay in staging environment, I’ll swap it with production. I have successfully deployed the new changes to staging slot from Visual Studio multiple times since yesterday but still the new changes are not reflected when I browse staging url. They are same as production.

I have created an App Service with Microsoft Authentication (Entra ID) in Azure. So while trying to browse the app, I am directly getting this You do not have permission to view this directory or page. Now if I generate OAuth2.0 Token in Postman and access the App, it is working.
Now question is –

I have an Azure web app that was running for a couple weeks. I just created a “staging” slot and added a slot-specific connection string to it, which I also did for the prod slot. I swapped them and now my production and staging slots are both writing to the staging db.

I have an Azure web app that was running for a couple weeks. I just created a “staging” slot and added a slot-specific connection string to it, which I also did for the prod slot. I swapped them and now my production and staging slots are both writing to the staging db.

I have an Azure web app that was running for a couple weeks. I just created a “staging” slot and added a slot-specific connection string to it, which I also did for the prod slot. I swapped them and now my production and staging slots are both writing to the staging db.

I have an Azure web app that was running for a couple weeks. I just created a “staging” slot and added a slot-specific connection string to it, which I also did for the prod slot. I swapped them and now my production and staging slots are both writing to the staging db.

Let’s say I have a pipeline that deploys to my staging slot in Azure Web Apps. Then I swap staging into production. Is my staging slot now on the previous deployment commit? e.g.

I have a container that I am trying to run in Azure WebApps. Locally the container works fine and the container user nginx has the following id output

I would need a bit of help in finding out why my custom domain is not working.
I published a webapp on Azure, which I want to make it public. I bought a domain on GoDaddy, then I went to azure, added a custom domain, and then added in GoDaddy the {“A”, “@”} and {“TXT”, “asuid”} values.

I deployed my web application utilizing Azure App Services. I have startup script which runs the application via command “java -jar test jar -D parameter list”. Everything works good,but when I am trying to add a new addintnal parameter to java command using Azure portal, then I got the error popup with the message “failed to save ..”
Is it any limitation on startup script content?