Posted by This article is a Companion article. Please have a look at the Main article Sitecore XP1 on Azure using Azure App Service.
Azure Resource Manager allows you to provision your applications using a declarative template. In a single template, you can deploy multiple services along with their dependencies.
In this article, we will use the Quick Start Template for configuring the Sitecore XP configuration located here
The Quick Start Templates has the following files.
- ReadMe
- json
- parameters.json
Let’s discuss about the above two JSON files.
- json – This file is the ARM template that contains all the Azure Services that are required for configuring the XP environment. Below are the most important Azure Services that will get created when the Azuredeploy.json file gets deployed and provisioned on Azure.
- App Services
- Databases
- Redis Cache
- Application Insights
- Azure Search
- parameters.json – you can provide the configuration values as parameters in this file. The configuration values that you provide will be used as inputs to the Azure deploy.json file. Below are the values that you provide in the Azuredeploy.paramters.json file.
| Parameter Name | Comments |
| deploymentId | The name of the Resource Group that Azure would create automatically. |
| sitecore.admin.password | Sitecore Admin Console Password. |
| sqlserver.login | Login Id of the Azure SQL Server |
| sqlserver.password | Password for Azure SQL Server |
| cm.msdeploy.packageurl | The Storage URL where the Content Management role’s Web Deploy Package is located. You might also need to append the Shared Access Signature. |
| cd.msdeploy.packageurl | The Storage URL where the Content Delivery role’s Web Deploy Package is located. You might also need to append the Shared Access Signature. |
| prc.msdeploy.packageurl | The Storage URL where the Processing role’s Web Deploy Package is located. You might also need to append the Shared Access Signature. |
| rep.msdeploy.packageurl | The Storage URL where the Reports role’s Web Deploy Package is located. You might also need to append the Shared Access Signature. |
| rep.authentication.apikey | A unique value (e.g. a GUID) that will be used as authentication when communicating from Content Management to the Reporting Web App. |
| analytics.mongodb.connectionstring | A MongoDB connection string for the analytics database. |
| tracking.live.mongodb.connectionstring | A MongoDB connection string for the tracking.live database. |
| tracking.history.mongodb.connectionstring | A MongoDB connection string for the tracking.history database. |
| tracking.contact.mongodb.connectionstring | A MongoDB connection string for the tracking.contact database. |
Below is the content of my azuredeploy.parameters.json file.
{
“deploymentId”: {
“value”: “xp3-rg”
},
“sitecore.admin.password”: {
“value”: “AdminSecr$t”
},
“rep.authentication.apikey”: {
“value”: “04660200-fb55-4c68-9bf1-2957acec7139”
},
“analytics.mongodb.connectionstring”: {
“value”: “mongodb://muser:mpassword@ds113650.mlab.com:13650/analyticsdb”
},
“tracking.live.mongodb.connectionstring”: {
“value”: “mongodb://muser:mpassword@ds113660.mlab.com:13660/tracking_live”
},
“tracking.history.mongodb.connectionstring”: {
“value”: “mongodb://muser:mpassword@ds113680.mlab.com:13680/tracking_history”
},
“tracking.contact.mongodb.connectionstring”: {
“value”: “mongodb://muser:mpassword@ds113670.mlab.com:13670/tracking_contact”
},
“sqlserver.login”: {
“value”: “sqlserveruser “
},
“sqlserver.password”: {
“value”: “Sqlpas$w1rd”
},
“cm.msdeploy.packageurl”: {
},
“cd.msdeploy.packageurl”: {
“value”: “https://xp1sa.blob.core.windows.net/xp1-container/Sitecore%208.2%20rev.%20161115_cd.scwdp.zip?sv=2016-05-31&ss=b&srt=sco&sp=rwdlac&se=2017-03-17T05:07:21Z&st=2017-03-07T21:07:21Z&spr=https,http&sig= V1gBhxFsc9of94U0aNeCpIbVEp9VUY4%3D”
},
“prc.msdeploy.packageurl”: {
“value”: “https://xp1sa.blob.core.windows.net/xp1-container/Sitecore%208.2%20rev.%20161115_prc.scwdp.zip?sv=2016-05-31&ss=b&srt=sco&sp=rwdlac&se=2017-03-17T05:07:21Z&st=2017-03-07T21:07:21Z&spr=https,http&sig= V1gBhxFsc9of94U0aNeCpIbVEp9VUY4%3D”
},
“rep.msdeploy.packageurl”: {
},
“licenseXml”: {
“value”: “”
}
}
Please note that the values of the attributes might vary at your end based on your configurations and settings.
Do you like this article? If you want to get more updates about these kind of articles, you can join my Learning Groups
Praveen Kumar Sreeram's Blog 
One comment