Description

The following tables describe the Azure resource types and sizes that are provisioned with each of the Sitecore ARM templates found in the Sitecore Azure Quickstart Templates repository on GitHub. The single topologies are not supported for production sites – they are purely for development and test purposes.

The Performance rating sizes were determined by performance testing a simple marketing site and finding the smallest resource sizes required to hit the associated visits per month. The simple marketing site was mainly read-only, with no login activity and few xDB interactions. Dependent requests were not tested (for example, images, JS, CSS) and it is assumed these assets will be served by a CDN.

The following sizes and instance counts serve as a starting point for you when trying to figure out the Azure requirements for your site. You might need to adjust some or all of the sizes or instance counts when you have performance tested your application.

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
Identity Server   Azure Web App [2]	1 x S3	1 x S1 (1 x i2)	1 x S1 (1 x i2)	1 x S1 (1 x i2)	1 x S2 (1 x i2)	1 x S2 (1 x i2)
Content Management server   Azure Web App [2]		1 x S3 (1 x i2)	1 x S3 (1 x i2)	1 x S3 (1xi2)	1 x S3 (1xi2)	1 x S3 (1xi2)
Content Delivery server   Azure Web App [2]		1 x S2 (1 x i1)	2 x S2 (1 x 2i)	3 x S2 (2 x i2)	4 x S3 (2 x i3)	8 x S3 (4 x i3)
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]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	3 x S1 (1 RS x 3 P)
Monitoring – Azure App Insights	3 x Basic	3 x Basic	3 x Basic	3 x Basic	4 x Enterprise	4 x Enterprise
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
Identity Server Azure Web App [2]	1 x S3	1 x S1 (1 x i1)	1 x S1 (1 x i1)	1 x S1 (1 x i1)	1 x S2 (1 x i2)	1 x S2 (1 x i2)
Content Management server Azure Web App [2]		1 x S3 (1 x i2)	1 x S3 (1 x i2)	1 x S3 (1 x i2)	1 x S3 (1 x i2)	1 x S3 (1 x i2)
Content Delivery server Azure Web App [2]		1 x S2 (1 x i1)	2 x S2 (1 x i1)	3 x S2 (2 x i2)	4 x S3 (2 x i3)	8 x S3 (2 x i3)
xDB Processing service Azure Web App [2]		1 x S1 (1 X i1)	1 x S1 ( 1 x i1)	1 x S1 (1 x i1)	1 x S2 (1 x i2)	1 x S2 (1 x i2)
xDB Reporting service Azure Web App [2]		1 x S1 (1 x i1)	1 x S1 (1 x i1)	1 x S2 (1 x i1)	1 x S2 (1 x i2)	1 x S2 (1 x i2)
Cortex Reporting Service Azure Web App[2]	1 x S1	1 x S1 (1 x i1)	1 x S1 (1 x i1)	1 x S2 (1 x i1)	1 x S3 (2 x i2)	2 x S3 (2 x i2)
Marketing Operations Azure Web App[2]
Marketing Automation reporting Azure Web App [2]
xConnect Collection search Azure Web App [2]
Cortex Processing service  Azure Web App[2]		1 x S1 (1 x i1)	1 x S1 (1 x i1)	1 x S3 (2 x i2)	2 x S3 (2 x i2)	4 x S3 (2 x i3)
xConnect Collection Azure Web App[2]
xConnect Reference data Azure Web App [2]
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
Cortex processing engine Tasks database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Cortex processing engine Storage database - SQL Azure	1 x S0	1 x S0	1 x S1	1 x S2	1 x S3	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
EXM 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
Messaging database - SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Search – Azure Search [1]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	3 x S1 (1 RS x 3 P)
Monitoring – Azure App Insights	3 x Basic	3 x Basic	3 x Basic	3 x Basic	4 x Enterprise	4 x Enterprise
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
xDB Processing service Azure Web App [2]	1 x S1	1 x S1	1 x S1	1 x S1	1 x S2	1 x S2
xDB Reporting service Azure Web App [2]		1 x S1	1 x S1	1 x S2	1 x S2	1 x S2
Cortex Reporting Service Azure Web App [2]	1 x S1	1 x S1	1 x S1	1 x S2	1 x S3	2 x S3
Marketing Operations Azure Web App[2]
Marketing Automation Reporting Azure Web App [2]
xConnect Collection search Azure Web App [2]
Cortex Processing service Azure Web App [2]		1 x S1	1 x S1	1 x S3	2 x S3	4 x S3
xConnect Collection Azure Web App[2]
xConnect Reference data Azure Web App [2]
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
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
Messaging database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Cortex processing engine Tasks database – SQL Azure	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0	1 x S0
Cortex processing engine Storage database – SQL Azure	1 x S0	1 x S0	1 x S1	1 x S1	1 x S3	1 x S3
Search – Azure Search [1]	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	1 x S1 (1 RS x 1 P)	2 x S1 (1 RS x 2 P)	3 x S1 (1 RS x 3 P)	3 x S1 (1 RS x 3 P)
Monitoring – Azure App Insights	3 x Basic	3 x Basic	3 x Basic	3 x Basic	4 x Enterprise	4 x Enterprise

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.
  As a cost saving measure the ARM Templates are initially set up with only 1 partition, and you can then add new partitions 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.
• [2] Items in parentheses beginning with i1, i2 and i3 are the isolated sizes in ASE V2.