Prerequisites:<\/h4>\n
To setup Sitecore 10.3 on Azure PaaS, we shall need the following:<\/p>\n
- \n
- Check PowerShellGet Module. If not found please install PowerShell Gallery<\/a>
\n![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/CheckPowerShellGet-e1676542038954.png?resize=2876%2C445&ssl=1\")
<\/li>\n- Install the Azure Az PowerShell<\/a> module.
\n![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/InstallAZ-e1676542152355.png?resize=3840%2C1324&ssl=1\")
<\/li>\n- Download Sitecore Azure Toolkit 2.8.0<\/a>. This will provide a zip file that can be extracted and used for setup.<\/li>\n<\/ul>\n
\u00a0Deployment Topologies<\/h4>\n
We will do the setup for Sitecore 10.3 XP. Sitecore XP\u00a0product edition is the full Sitecore Experience Platform, which includes all Sitecore roles and services, including xConnect.<\/p>\n
This is a Sitecore Experience Platform configuration that runs:<\/p>\n
- \n
- Three Sitecore roles:\u00a0Content Delivery,\u00a0Content Management, and\u00a0Processing, as a single WebApp instance.<\/li>\n
- All XP roles:\u00a0XConnect Search,\u00a0XConnect Collection,\u00a0xDB Reference Data,\u00a0xDB Marketing Automation,\u00a0xDB Marketing Automation Reporting,\u00a0Sitecore Cortex\u2122 Processing<\/em>,\u00a0Sitecore Cortex\u2122 Reporting<\/em>, Each role runs as a single WebApp instance.<\/li>\n<\/ul>\n
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/SitecoreXPScaledTopology.png?resize=1243%2C615&ssl=1\")
\nImage Credit: Sitecore<\/small><\/p>\nInstallation Step:<\/h4>\n
Step 1:<\/strong> Create a new folder E:\\Sitecore1030<\/p>\n
Step 2:<\/strong> Please copy License file in E:\\license\\license.xml<\/p>\n
Step 3:<\/strong> Download options for Azure AppService for Sitecore 10.3<\/a> in Sitecore1030 folder. Please download XP Scaled.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/DownloadSitecoreOptionsForAzureAppService.png?resize=3413%2C944&ssl=1\")
<\/p>\nStep 4: <\/strong>Download Sitecore.IdentityServer.7.0.325.scwdp<\/a> in Sitecore1030 folder.<\/p>\n
Step 5: <\/strong>Create Azure Storage AccountLogin to Azure portal and create a storage account. Ensure to select \u201cBlob Storage\u201d.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/Create-StorageAccount.png?resize=3840%2C2160&ssl=1\")
<\/p>\nStep 6: <\/strong>Upload all of the WDP\u2019s zips included in the chosen zip file that we downloaded.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/Sitecore10wdpFIles.png?resize=3840%2C2160&ssl=1\")
<\/p>\nStep 7: <\/strong>Now, in Azure to access these files publicly, we must enable a Shared Access Signature. This can be achieved using Azure Storage Explorer. Please select the expire date as per your convenient. Also make sure to copy the token generated for Blob.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/ContainerShareAccessToken.png?resize=3840%2C2160&ssl=1\")
<\/p>\nStep 8: <\/strong>Use PowerShell to create self-signed certificate in .pfx format, which we will use in setup configuration file. Please note the certificate password.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/CreateCertificate-e1676549416343.png?resize=3840%2C787&ssl=1\")
<\/p>\nStep 9: <\/strong>Select and download Sitecore Azure Quick Strat template. This is important because the templates are what Azure will utilize to actually build out the resources based on the chosen topology. We can find the link to the GitHub to the Sitecore Azure ARM Templates<\/a> on the Sitecore Azure Toolkit page. Here we need to select the proper Sitecore version to download the file. In our case we will download Sitecore 10.2.0<\/a> version, which is compatible for both 10.2 and 10.3.<\/p>\n
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/SitecoreAzureTemplate1.png?resize=3552%2C1242&ssl=1\")
<\/p>\nI am going to choose XP-<\/p>\n
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/SitecoreAzureTemplate2.png?resize=2555%2C1037&ssl=1\")
<\/p>\nFind the azuredeploy.parameters.json<\/strong> file and click on it.<\/p>\n
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/SitecoreAzureTemplate3.png?resize=3547%2C1289&ssl=1\")
<\/p>\nNow copy the URL without the trailing Slash and note it down. We will use it in configuration. For my case this is-
\nhttps:\/\/github.com\/Sitecore\/Sitecore-Azure-Quickstart-Templates\/blob\/master\/Sitecore%2010.2.0\/XP<\/small>
\nNow that we have the raw file in your browser, I\u2019ll save that file into Now E:\\Sitecore1030 directory as azuredeploy.parameters.json file. We will be configuring this file next.<\/p>\nStep 10: <\/strong>Now open the azuredeploy.parameters.json file using Visual Code and set the below parameter as instructed.
\nThe deploymentId<\/strong> and licenseXml<\/strong> parameters in azuredeploy.parameters.json are filled in by the PowerShell script using Name and LicenseXmlPath parameters respectively.<\/p>\n\u00a0<\/p>\n
\n\n
\n Parameter<\/strong><\/td>\n \u00a0Description<\/strong><\/td>\n<\/tr>\n \n location<\/td>\n The geographical region of the current deployment.<\/td>\n<\/tr>\n \n sqlServerLogin<\/td>\n The name of the administrator account for Azure SQL server that will be created.<\/td>\n<\/tr>\n \n sqlServerPassword<\/td>\n The password for the administrator account for Azure SQL server.<\/td>\n<\/tr>\n \n sitecoreAdminPassword<\/td>\n The new password for the Sitecore\u00a0admin\u00a0account.<\/td>\n<\/tr>\n \n repAuthenticationApiKey<\/td>\n A unique value (e.g. a GUID) that will be used as authentication key for communication between Content Management and the Processing Web App.\u00a0Note: The minimal required length is 32 symbols<\/td>\n<\/tr>\n \n siMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Sitecore Identity Server Web Deploy package.<\/td>\n<\/tr>\n \n cmMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Sitecore XP Content Management Web Deploy package.<\/td>\n<\/tr>\n \n cdMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Sitecore XP Content Delivery Web Deploy package.<\/td>\n<\/tr>\n \n prcMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Sitecore XP Processing Web Deploy package.<\/td>\n<\/tr>\n \n xcRefDataMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a XConnect Reference Data service Web Deploy package.<\/td>\n<\/tr>\n \n xcCollectMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a XConnect Collection service Web Deploy package.<\/td>\n<\/tr>\n \n xcSearchMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a XConnect Search service Web Deploy package.<\/td>\n<\/tr>\n \n maOpsMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Marketing Automation service Web Deploy package.<\/td>\n<\/tr>\n \n maRepMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Marketing Automation Reporting service Web Deploy package.<\/td>\n<\/tr>\n \n cortexProcessingMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Cortex Processing service Web Deploy package.<\/td>\n<\/tr>\n \n cortexReportingMsDeployPackageUrl<\/td>\n The HTTP(s) URL to a Cortex Reporting service Web Deploy package.<\/td>\n<\/tr>\n \n authCertificateBlob<\/td>\n A Base64-encoded blob of the authentication certificate in PKCS #12 format.<\/td>\n<\/tr>\n \n authCertificatePassword<\/td>\n A password to the authentication certificate.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n \u00a0<\/p>\n
There are a series of Package URL parameters for mapping to the WDP\u2019s that are in the Azure Storage Container. Each MsDeployPackageUrl maps to a role WDP.
\nTo obtain the full Uri, open up Azure Storage Explorer and navigate to the specific file, right click on it, and choose Properties.<\/p>\n![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/wdpfileURL.png?resize=2926%2C686&ssl=1\")
<\/p>\nNext, after we have pasted the Uri for the specific file into the parameters, paste the Token in the Query String of the Uri, that we saved from step 7<\/p>\n
Step 11: <\/strong>In the event we\u2019re using a self-signed certificate, so need to add allowInvalidClientCertificate parameter to your parameter JSON<\/p>\n
file.
\"allowInvalidClientCertificates\": {
\n\"value\": true
\n}<\/code>,<\/p>\nStep 12: <\/strong>\u00a0The following script can be utilized directly by copy\/pasting and changing the values to suit your need. I named this script DeploySitecore1030.ps1 but you can call it whatever you like.<\/p>\n
$SCSDK=\u201dE:\\Sitecore1030\\ToolKit\\Sitecore Azure Toolkit 2.8.0-r02542.1366\\tools\u201d
\n$SCTemplates=https:\/\/raw.githubusercontent.com\/Sitecore\/Sitecore-Azure-Quickstart-Templates\/master\/Sitecore%2010.2.0\/XP
\n$DeploymentId = \u201csitecore1030\u201d
\n$ResourceGroup = \u201csitecore1030\u201d
\n$LicenseFile = \u201cE:\\license\\license.xml\u201d
\n$CertificateFile = \u201cE:\\sitecore10cert\\58ACD57D7D788E890E08C4F168A93C0BE8D1F97D.pfx\u201d
\n$SubscriptionId = \u201c5777ffac-35e1-4e61-803d-2a259813e503\u2033
\n$Location=\u201dEast US\u201d
\n$ParamFile=\u201dE:\\Sitecore1030\\azuredeploy.parameters.json\u201d
\n$Parameters = @{\u201cdeploymentId\u201d=$DeploymentId;\u201dauthCertificateBlob\u201d = [System.Convert]::ToBase64String([System.IO.File]::ReadAllBytes($CertificateFile))}
\nImport-Module $SCSDK\\Sitecore.Cloud.Cmdlets.psm1
\nAdd-AzAccount
\nConnect-AzAccount -SubscriptionId $SubscriptionId
\nStart-SitecoreAzureDeployment -Name $ResourceGroup -Location $Location -ArmTemplateUrl \u201c$SCTemplates\/azuredeploy.json\u201d -ArmParametersPath $ParamFile -LicenseXmlPath $LicenseFile -SetKeyValue $Parameters -Verbose<\/p>\n$SCSDK \u2013 Point this to the tools directory that was added by the Sitecore Azure Toolkit.
\n$SCTemplates \u2013 Point this to the ARM Template URL saved in point 9
\n$DeploymentId \u2013 Can be anything up to 60 characters. I used same as Azure Resource group name.
\n$ResourceGroup \u2013 The name of the Azure Resource Group to install the services in.
\n$LicenseFile \u2013 the location of your license.xml.
\n$CertificateFile \u2013 the location of your client certificate.
\n$Location \u2013 Azure Geographical Location.
\n$ParamFile \u2013 the location of your azuredeploy.parameters.json file.<\/small><\/code><\/p>\nStep 13: <\/strong>After all the steps previously are complete, now it\u2019s time to Run our PowerShell script!
\nOpen PowerShell as Administrator and change directory to E:\\Sitecore1030 (Where we have the PS1 file) and run the PS1 file.<\/p>\n![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/deploysitecore-e1676621381235.png?resize=3840%2C652&ssl=1\")
<\/p>\nStep 14: <\/strong>This will prompt Azure portal credential. Please provide proper credential.<\/p>\n
![\"Azure](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/AzureCredential-e1676621464605.png?resize=3840%2C1094&ssl=1\")
<\/p>\nStep 15: <\/strong>Deployment Status
\nIt will take 20-30 minutes to complete the deployment depending on the bandwidth. We can view the deployment status from PowerShell-<\/p>\n![\"Azure](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/AzureDeployment.png?resize=3840%2C2160&ssl=1\")
<\/p>\nWe can also observe the deployment progress in the Azure Portal, by clicking on the Resource Group and choosing Deployments.<\/p>\n
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/AzureDeploymentStatus.png?resize=3840%2C2160&ssl=1\")
<\/p>\nPost-Deployment Steps<\/h4>\n
Once the deployment is complete, there are a few steps that we should follow.<\/p>\n
- Install the Azure Az PowerShell<\/a> module.
![\"\"](\"https:\/\/i0.wp.com\/lng-consultancy.com\/staging\/5474\/wp-content\/uploads\/2023\/02\/ErrorWithImportAzResources.png?resize=3840%2C2160&ssl=1\")
<\/p>\n