In the Deploying a Website recipe, we saw how to deploy an ASP.NET application into an Azure Website. We saw that there is almost no unique knowledge required (except the skills needed to write the web application), making the deployment process straightforward. However, deploying is just the beginning of the process—leading to tasks such as advanced configuration, monitoring, domain mapping, logging, disaster recovery, and more.

Such activities are performed entirely via the Azure Portal (or through PowerShell), making it the central point of administration of the entire website's infrastructure.

After deployment, we probably focus on the fine-tuning of the runtime environment, making some optimizations to load only the required frameworks, and disabling everything that is not needed by the application. If the deployment will be a production deployment, a custom domain should be mapped to the website and, if we want to avoid confusion in case of errors...