Do slots make virtual machines in Azure?

Question

I currently have a web application deployed to Azure on the free App Service plan, and as part of the concert, I am interested in moving to using slots.

This is primarily because it gives me the opportunity to deploy new code at the stage of setting, and then easily go under its check.

Now, to use the slots, I know that I need a standard plan, and this clock works on at least $X on the VM.

What I do not know (and, unfortunately, could not be found out from the Azure material on Microsoft web pages) is whether the second slot is considered to be another virtual machine.

In one place, at least it says that the deployment slots are live web applications with their own hostname, but this can be read in at least two ways. either as a separate application on the same virtual machine, or as a separate virtual machine.

Since the difference is significant ( $2X/month , not $X/month ), this is very important for planning. So does anyone know how (preferably with some support for quotes from Microsoft) the slots are processed and charged for?

Answer 1

All deployed Azure sites in a certain plan of web applications run on the same virtual machine instances. Just as if you deployed mysite1.azurewebsites.net and mysite2.azurewebsites.net in the same way, they will use the same virtual machine instances. Thus, add additional slots for deployment.

If you scale to 3 instances, you pay for 3 instances, and all deployments (all slots for all deployments) run in all three instances.

One way to make this easier: the "production" (or main) deployment slot is another slot.