Azure Blueprint for Sitecore FAQ

Azure Blueprint

  • Azure Blueprint can currently deploy to Azure datacenters in the Global Azure Cloud, Azure Germany and Azure China (Mooncake). While this enables coverage in more than 40 regions, Copenhagen Mist do recommend a few “favorite” and well-tested locations. Contact us for more information.

  • You don’t. All infrastructure is fully managed by Copenhagen Mist. No need to worry about sizing, access and upgrades and so on. All you need to focus on is the application development, and we’ll ensure it is delivered and available to end users globally.

  • The updating capability is the most important feature of Azure Blueprint.

    In a traditional infrastructure setting, a solution is deployed into a predefined infrastructure environment. Then it basically remains untouched for the remainder of the solution’s lifetime. With Azure PaaS, the fundamental conditions are different, and this opens new opportunities. The services the infrastructure is based on, are constantly expanded and improved. These ranges from new dashboards and monitoring points, to introduction of new VM types, which supersede older ones with better performance at the same price, to security features and much, much more.

    As a Blueprint customer the end result is that you are always running on the best available services, making the most of the cloud without even having to intervene.

  • While the architecture and deployment Blueprint generates is by its very nature transparently available, Azure Blueprint is based on a wide range of proprietary technologies and practices developed by Copenhagen Mist.


  • Azure Blueprint for Sitecore currently supports Sitecore 8.2 and newer versions including 9.x, 10.x in XM, XP and Sitecore Commerce configurations. In addition XM Cloud is supported though the modular services included in Blueprint.

  • As Blueprint supports deploying Azure VMs into the topology, all Sitecore modules can be supported.

Business Critical configuration

  • Azure Blueprint for Sitecore Business Critical is architected and resourced for the high availability required for transactional websites where downtime can have a significant business impact.

    The specific differences are evolving along with the Blueprint, but overall all resources are deployed in redundant configurations, and where possible also across “Availability Zones“. An Availability Zone is a physical separate datacenter, and this redundant design enables the entire datacenter to be down without impacting the overall availability of the solution.

    Specifically webapps, redis and search are force deployed in redundant pairs. The database service is set up as zone redundant, all networking is made zone redundant, Solr and storage is made zone redundant.

  • At this point Business is available in the following regions with more coming:

    • Central US
    • East US
    • East US 2
    • France Central
    • North Europe
    • Southeast Asia
    • West Europe
    • West US 2

    A Business Critical configuration can be extended with Standard Production nodes in other datacenters, e.g. In Mainland China.

  • 24/7 support is available as an add-on to the other Blueprint configuration types. Please contact us for details.

  • While Azure Blueprint for Sitecore in its Business Critical configuration can be downgraded to regular office hour support, the likely best fit for your deployment would be the Production Standard configuration. Please contact us for an in-depth qualifying discussion of what best meets your needs.

General Questions

  • Azure Blueprint is available packaged with the Azure subscriptions provided by Copenhagen Mist, but can also be made available for customers with Azure Enterprise Agreements under special terms and an adjusted pricing model.

    Each customer is deployed onto a dedicated, and fully isolated Azure AD tenant, so from a security and segregation perspective it is fully on par on both types of deployments. The tenant is effective owned by the customer, and the customer have full control to migrate the tenant to other providers.

  • Unfortunately no. For this you need inhouse development or a Sitecore solution partner. Copenhagen Mist are Sitecore Partners, but we do only deal with the Azure Infrastructure associated with a successful Sitecore Cloud deployment.


  • Based on our benchmarks of Sitecore projects running on various Appservice instance types, we calculate the number of instances required to deliver the traffic from the datacenters chosen. In production environments we ensure high availability using the built-in features of Azure appservice, and this will be even higher if a CD is placed in a secondary location.

    We also size xDB storage and network component such as a Web Application Firewall (WAF) based on the input provided. Management cost is defined by the the number of servers running and traffic distribution costs are calculated based on the number of pageviews the site is delivering.

  • You dont:) The calculator implicitly deals with the ressource allocation required for both SC8, SC9 and SC10. For SC8 you need to drop in a Sitecore xDB. For Sitecore 9+ please remember to add in a Solr cluster per location.

  • Of course, that’s what we do. Contact us, and we’ll provide guidance.

  • Some of your module choices might impact the network cost disproportionally. In particular “Network Isolation for PaaS”, in the shape of an Appservice Environment/ASE has a cost impact of about 1000 EUR pr month pr datacenter, even in nonprod configs.

  • The deployment model we use takes care of all scaling. What we need to know is where you want your CDs, and we will ensure the correct sizing and scaling depending on your environment type and traffic load.

  • A Sitecore CM failover is intended to be deployed as a passive node in a secondary location for business continuity. Should the primary CM location fail the Failover CM kicks in.

    Behind the scenes, all the data from the primary CM is continuously replicated to the secondary location and the failover happens automatically and seamlessly in less than 30 seconds.

  • All datacenters in Global Azure, Azure Germany and Azure China are fully supported.

    We have purposefully limited the datacenter list in the calculator to keep it approachable, while still providing a resonable accurate estimate. If you need an estimate involving datacenters not on the list, contact our team and we’ll assist.

Deployment & Integration

  • Azure Blueprint comes with a full set of enriching deploy pipelines for the relevant rols. All you need to do is connect in your build output, pass the artifacts, and we’ll take care of the rest.

    The enrichment at deploytime includes hotfixes, entensions and enhancement developed by Copenhagen Mist.

  • Absolutely. The architecture of Azure blueprint is designed to be extended with e.g. Additional VMs and other roles. These are automatically integrated into Blueprint’s network and security architecture.

    Contact out team for details and solutions matching your specific needs.

    Privacy Preferences

    When you visit our website, it may store information through your browser from specific services, usually in the form of cookies. Here you can change your Privacy preferences. It is worth noting that blocking some types of cookies may impact your experience on our website and the services we are able to offer.

    Click to enable/disable Google Analytics tracking code.
    Click to enable/disable Google Fonts.
    Click to enable/disable Google Maps.
    Click to enable/disable video embeds.
    Our website uses cookies, mainly from 3rd party services. Define your Privacy Preferences and/or agree to our use of cookies.