Deploying your Sitecore customizations with Microsoft Azure


Learn more about the additional deployment functionality of Sitecore on Microsoft Azure.

You can deploy all of your Sitecore customizations to your Microsoft Azure® deployment in the same way as you do for your on-premise deployments. For example, you can use Sitecore packages, Web Deploy packages, and you can also publish items between Master and Web. This topic describes Azure's additional deployment functionality.

Through Azure, you can set up continuous deployment to the Microsoft Azure App service by connecting your source control system directly to a Web App and then automatically deploying the latest build from a branch into that Web app. This functionality enables you to have a fully automated deployment of your latest changes, as well as the option of rolling back to an older build if something goes wrong. With continuous deployment, you only need to check-in the files that you want to manage with source control and continuous deployment. The App Service environment deploys and manages them on top of your existing Sitecore Experience Platform installation.

This feature currently supports Microsoft Visual Studio® Team Services, Git, OneDrive®, and Drop Box®.

Visual Studio with the Azure SDK has seamless integration into Azure through the Cloud Explorer window. In this window, you can see all of the resources that you have deployed in Azure and can also manage some aspects of their functionality. Using the Cloud Explorer window as a developer, you can right-click on a Web App and attach your debugger to that Web App. From there, you can walk through the code locally. If you find an issue with your code, you can publish your code directly to that Web App without ever leaving Visual Studio. The Microsoft Azure documentation has more information on how to deploy an ASP.NET web app to the Azure App Service, using Visual Studio.

Microsoft Azure Web Apps® have a feature called Staging Slots for staged publishing. Using Staging Slots to set up a staging environment in the Azure App service means that you can perform alternating Blue-Green deployments very easily.