We are trying to set up managed identity for our db, we have managed to get it to work with our staging site. But for our production website where where we have a warmup slot that performs a swap with the live site we are facing problems. for context our warmup (deployment slot) slot is in Azure App service. It looks like this when the site is trying to swap that the slots no longer have access to the DB as this shows up:
Have you assigned the managed identity to the slot also?
Is the connection string set on the web app slot?
Azure treats them both as separate web apps even though your slot is part of the Production web app.
When you click the swap button in the portal are you seeing anything in the Source/target slot changes?
Like this?
The above screenshot indicates that the two slots (Production and your slot) don’t have the same appsettings. Notice in the screenshot above, the value for this appsetting with become false in the source slot when it swaps. This will then cause the target (Production) to have the appsetting removed when the swap completes.