Description

The following table describes the differences between various Sitecore XP environments for the Sitecore Managed Cloud service, as well as related Azure components.

Customers can purchase these configurations under both Production and Non-Production SLAs.

Note:

1. Tiers and topologies are subject to availability. Check the Sitecore Managed Cloud Standard – compatibility tables for the currently supported tiers for provisioning new Sitecore Managed Cloud Standard sets, as well as for the Microsoft Azure data center compatibility information. The environment tiers are designed in accordance with Sitecore XP ARM templates with additional changes and clarifications required to deliver Managed Cloud specific service level agreements. Sitecore might update the recommended sizes from time to time to ensure the most efficient performance level. For details about the specific topology and size applied in a contract, customers can contact their Sitecore sales representatives.
2. We do not recommend using the Basic App Service plan because it is designed for a test environment and has a number of limitations.
   These limitations include: no possibility to use backups at all, no autoscaling your instances, a storage capacity of only 10Gb, no opportunity to use Traffic manager for load balancing, and no using Staging slots for development.

Experience Management (XM)

	Performance rating
Component	Single	Extra small	Small	Medium	Large	Extra large
Approximate visits per month range	-	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000-10,000,000
Page views per month	-	500,000	1,000,000	5,000,000	10,000,000	50,000,000
Content Management server – Azure Web App	1 x B3 *	1 x B3	1 x B3	1 x B3	1 x B3	1 x B3
Content Delivery server – Azure Web App		1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
Core database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Forms database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S1	1 x S2
Search – Azure Search [1][2]	1 x S1 (1 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	4 x S1 (2 RS x 2 P)	6 x S1 (2 RS x 3 P)	6 x S1 (2 RS x 3 P)
Search – Solr on SearchStax (Azure)[3]	1 x XS	2 x XS	2 x S	2 x M	2 x L	2 x XL
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Basic	1xEnterprise	1xEnterprise
Session state – RedisCache	-	1 x C1	1 x C1	1 x C1	1 x C1	1 x C2

Experience Platform (XP)

	Performance rating
Component	Single	Extra small	Small	Medium	Large	Extra large
Approximate visits per month range	-	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000-10,000,000
Page views per month	-	500,000	1,000,000	5,000,000	10,000,000	50,000,000
Content Management server – Azure Web App	1 x B3 *	1 x B3	1 x B3	1 x B3	1 x B3	1 x B3
Content Delivery server – Azure Web App		1 x B2	2 x B2	3 x B2	4 x S3	8 x S3
xDB Processing service – Azure Web App		1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting service – Azure Web App		1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Marketing Operations – Azure Web App	1 x S1 *	1 x B1 *	1 x B1 *	1 x B2 *	1 x B3 *	2 x S3 *
Marketing Automation reporting – Azure Web App
xConnect Collection search – Azure Web App
xConnect Collection – Azure Web App		1 x B1 *	1 x B1 *	1 x B3 *	2 x S3 *	4 x S3 *
xConnect Reference data – Azure Web App
Core database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Reporting database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S2	1 x S2	1 x S3
Pools database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S1	1 x S1	1 x S2
Tasks database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S1
Forms database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S1	1 x S2
Marketing Automation database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S1	1 x S1	1 x S1
Reference data database – SQL Azure	1 x S0	1 x S0	1 x S1	1 x S2	1 x S3	1 x S3
Shard map management – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Shard 0/1 databases – SQL Azure	2 x S0	2 x S0	2 x S1	2 x S2	2 x P1	2 x P2
Search – Azure Search [1][2]	1 x S1 (1 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	4 x S1 (2 RS x 2 P)	6 x S1 (2 RS x 3 P)	6 x S1 (2 RS x 3 P)
Search – Solr on SearchStax (Azure)[3]	1 x XS	2 x XS	2 x S	2 x M	2 x L	2 x XL
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Basic	1xEnterprise	1xEnterprise
Session state – RedisCache	-	1 x C1	1 x C1	1 x C1	1 x C1	1 x C2

Experience Database (XDB)

	Performance Rating
Component	Single	Extra small	Small	Medium	Large	Extra large
Approximate visits per month range	-	0 - 100,000	100,000 - 200,000	200,000 - 1,000,000	1,000,000 - 5,000,000	5,000,000-10,000,000
Page views per month	-	500,000	1,000,000	5,000,000	10,000,000	50,000,000
xDB Processing service – Azure Web App	1 x S1 *	1 x B1	1 x B1	1 x B1	1 x B2	1 x B2
xDB Reporting service – Azure Web App		1 x B1	1 x B1	1 x B2	1 x B2	1 x B2
Marketing Operations – Azure Web App	1 x S1 *	1 x B1 *	1 x B1 *	1 x B2 *	1 x B3 *	2 x S3 *
Marketing Automation Reporting – Azure Web App
xConnect Collection search – Azure Web App
xConnect Collection – Azure Web App		1 x B1 *	1 x B1 *	1 x B3 *	2 x S3 *	4 x S3 *
xConnect Reference data – Azure Web App
Core database – SQL Azure	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Master database – SQL Azure	1 x S0	1 x S1	1 x S1	1 x S1	1 x S1	1 x S1
Web database – SQL Azure	1 x S0	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3
Reporting database – SQL Azure	1 x S0	1 x S1	1 x S1	1 x S2	1 x S2	1 x S3
Pools database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S1	1 x S1	1 x S2
Tasks database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S1
Marketing Automation database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S1	1 x S1	1 x S1
Reference Data database – SQL Azure	1 x S0	1 x S0	1 x S1	1 x S2	1 x S3	1 x S3
Shard map management – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Shard 0/1 databases – SQL Azure	2 x S0	2 x S0	2 x S1	2 x S2	2 x P1	2 x P2
Search – Azure Search [1][2]	1 x S1 (1 RS x 1 P)	2 x S1 (2 RS x 1 P)	2 x S1 (2 RS x 1 P)	4 x S1 (2 RS x 2 P)	6 x S1 (2 RS x 3 P)	6 x S1 (2 RS x 3 P)
Search – Solr on SearchStax (Azure)[3]	1 x XS	2 x XS	2 x S	2 x M	2 x L	2 x XL
Monitoring – Azure App Insights	1 x Basic	1 x Basic	1 x Basic	1 x Basic	1xEnterprise	1xEnterprise

* - All services from the left must be deployed on separate web apps

Notes

• [1] Azure Search size refers to Search Unit (SU), which is the product of replica and partitions used by the Azure Search service (RS X P = SU). At a minimum, every service starts with 1 SU (one replica multiplied by one partition). See search units and SU combinations for more information.
• [2] The size of Azure Search Units for Managed Cloud topologies is double the size of what is defined in the ARM template article. This is due to Microsoft SLA for Azure Search, which requires a minimum of two replicas to guarantee 99.9% availability.
  As a cost saving measure all customers are initially set up with only 1 partition and then new partitions are added as required. However, from a budgeting point of view, you can expect to increase to the number of partitions listed by the end of the first year.
  The Single sizing is not designed for production usage so it is only set up with 1 Replica Set by default, because no SLA should be required.
• [3] The size of Solr instances on SearchStax:
  

  Tier	Specification	Production and Non-Production – Max Requests / Month*
  XS	32 GB storage	1 Million
  S	32 GB storage	2 Million
  M	50 GB storage	10 Million
  L	75 GB storage	20 Million
  XL	75 GB storage	100 Million
  2XL	128 GB storage	100 Million
  3XL	256 GB storage	100 Million

  *- Customers exceeding the monthly entitlement will accrue overages against your contract.