The Sitecore 8.2 update 1+  was the first major release that took Sitecore to a cloud as a service. The  Sitecore Azure Module was available since version 6, but it was never widely accepted due to support and installation challenges. With the support of PowerShell and Azure Toolkit, Sitecore can be installed as App Service in Azure with minimal effort now.

In this article, I’ll review Sitecore provisioning into AppService using PowerShell, Azure Toolkit and Environment Templates in 10 steps and under 45 minutes.

Prerequisites

  1. Provision Azure Account and obtain Subscription Id.
  2. Create Microsoft Storage account using this guide or just go to Azure Portal, click “+” -> Storage->Storage Account and select blob storage.

3. Using this table, select the appropriate configuration.  The source can be found here.

Configuration Description
XP0 This is Sitecore Experience Platform running as a single WebApp instance. Use this configuration for development and testing purposes. It is best practice to use the XM1 or XP1 configuration in production environments for security and scalability reasons.
XM1 This is Sitecore Experience Management configuration running two roles: Content Delivery and Content Management. Use this environment when you are not planning to use Analytics and Marketing features of Sitecore Experience Platform (that is, in CMS-only mode).
XP1 This is Sitecore Experience Platform configuration running four roles: Content Delivery, Content Management, Processing, and Reporting. Use this environment when you are planning a fully-featured Sitecore Experience Platform installation.

Download profile from this location

4. Upload profile file to  Azure Storage and set aside location URL. Make sure to secure the file as it is not designed for public download.

5. Download Sitecore Azure Toolkit and unzip it to your workplace location. Make sure to ‘unblock’ it before unzipping.

6. Clone or Download Sitecore Azure Quickstart Templates .Select templates that match profile selected in step  #3.

7. Put Sitecore license into your workplace folder.

8. Create 4 Mongo databases (analyticsdb, tracking_live, tracking_history and tracking_contact). For purpose of this article, I used free mlab account.

After you done, your local file structure should look like this:

Configuration

9. Updated azuredeploy.parameters.json file.

DeploymentId – Name of Azure Resource Group

sitecore.admin.password – default password to Sitecore admin interface.

analytics.mongodb.* – Mongo connection strings. Could be pulled from mlab interface.

sqlserver.* – new username/password that will be used in provisioning MS SQL DB

single.msdeploy.packageurl – location of Sitecore deployment package, created in step #4

Example:

10. Create a PowerShell script, based on this code.

11. Run above script and wait for 15 minutes (for XP0 profile). Navigate to Azure portal to review created assets.

.\Deploy.ps1