3 years later I’m working on my first real Azure project and being responsible for the whole infra. It felt like a complex service to manage and comprehend back then. Around those times the default way of hosting web applications on Azure PaaS was to use Azure Cloud Services.

It was roughly 7 years ago when I started to learn about Azure. Depending on your situation, you may prefer one of these approaches.Taking full control of your zero-downtime deployments in Azure App Service on Linux. On the other hand, system assigned identities will be deleted as soon as you delete a slot. User assigned identities won’t be removed whenever you delete a slot. Once you’ve generated or assigned an identity, don’t forget to then add it to any Azure resources your app needs access to.Īlso keep in mind the lifecycle of a managed identity. They don’t swap – so if you need to change these, you’ll need to intervene separately. When swapping slots, both system and user-assigned identities remain tied to the slot. These are configured to allow your App Service to access other Azure resources, without the need for sharing secrets and passwords. You might recall that for an App Service you can have both a system-assigned or a user-assigned identity. In short, managed identities are tied to the slot in which you first create or assign them, and do not change when you initiate a swap between two or more slots. Microsoft cover in depth what happens when you commence a swap, but what they don’t cover is what happens to any managed identities that you have setup for the app service. If you’ve configured a slot then you’ll want to swap deployments at a minimum between a production and pre-production environment. If you’re using an Azure App Service on a tier that offers staging slots (standard and above) then you might want to consider what happens when you swap a slot.

Azure web apps deployment slots swap