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 superseed 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 proprierary technologies and practices developed by Copenhagen Mist.

Sitecore

Azure Blueprint for Sitecore currenly supports Sitecore 8.2.x.

Sitecore 9.1 will be supported from its release date.

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

General Questions

At the moment Azure Blueprint is only available packaged with the Azure subscriptions provided by Copenhagen Mist.

Each customer is deployed onto a dedicated, and fully isolated Azure AD tenant, so from a security and segregation perspectiive it is fully on par with a seperate EA deployment. 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

Calculator

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 and SC9. For SC8 you need to drop in a Sitecore xDB

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 currect 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 continiously replicated to the secondary location and the failover happens automatically and seemlessly 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

Once the infrastructure is in place for the relevant environments, there are multiple options for deploying code an data onto it. Our recommendation is to use Octopus Deploy and Webdeploy packages, but will help each customer evaluate which tools are best suited for the existing scenario.

Absolutely. The arcitecure 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.