Managed Cloud Standard best practice suggestions


Sitecore Managed Cloud Standard is a combination of technologies and services on top of the Microsoft Azure platform. There are a wide variety of optimizations available, and Managed Cloud Standard is a fundamentally open product where customers adapt the starting topologies (Sitecore Managed Cloud Standard – topologies and tiers for Sitecore) to suit their implementation patterns. Based on our experience of working with many Managed Cloud Standard projects, Sitecore would like to share some of the best practices other projects have found to be successful. These suggestions are not supported by Sitecore through a formal SLA. The scope of Managed Cloud official support is defined by Sitecore Managed Cloud Standard – service catalog on-demand requests and Sitecore Managed Cloud Standard — monitoring metrics. What is included in this article are suggestions independent of Sitecore official support that can address areas where Microsoft Azure features might be tuned to suit certain Sitecore scenarios.

The suggestions cover 6 specific components:

  1. SQL Database
  2. App Service
  3. App Service Plan
    • Out of the Box topologies are a starting point
    • Microsoft can update without notice
    • Azure App Service Plan consideration – P2V3 vs S3
    • Using the Basic App Service plan is not recommended
  4. Application Insight
    • Application Insight as a logging mechanism
    • Application Insights "Daily Cap" on data storage
  5. Azure Networking
    • Consider IP restrictions for CM, and note Application Insights IP ranges for ping checks
    • Set up a Web Application Firewall (WAF) before go-live               
  6. Resource Group
    • "Tags" can identify Azure resources