title: Resources without 800 count limit description: Lists the Azure resource types that can have more than 800 instances in a resource group. ms.topic: article ms.date: 09/15/2025
By default, you can deploy up to 800 instances of a resource type in each resource group. However, some resource types are exempt from the 800 instance limit. This article lists the Azure resource types that can have more than 800 instances in a resource group. All other resources types are limited to 800 instances.
For some resource types, you need to contact support to have the 800 instance limit removed. Those resource types are noted in this article.
Some resources have a limit on the number instances per region. This limit is different than the 800 instances per resource group. To check your instances per region, use the Azure portal. Select your subscription and Usage + quotas in the left pane. For more information, see Check resource usage against limits.
- automationAccounts
- SqlServerInstances
- generateDeploymentLicense
- linkedSubscriptions
- registrations
- registrations/customerSubscriptions
- registrations/products
- botServices - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Resources/ARMDisableResourcesPerRGLimit
- profiles - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Resources/ARMDisableResourcesPerRGLimit
- profiles/networkpolicies - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Resources/ARMDisableResourcesPerRGLimit
- diskEncryptionSets
- disks
- galleries
- galleries/images
- galleries/images/versions
- galleries/serviceArtifacts
- images
- snapshots
- virtualMachines
- virtualMachines/extensions
- virtualMachineScaleSets - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Resources/ARMDisableResourcesPerRGLimit
- containerGroupProfiles
- containerGroups
- containerScaleSets
- registries/buildTasks
- registries/buildTasks/steps
- registries/eventGridFilters
- registries/replications
- registries/tasks
- registries/webhooks
- instances
- servers
- flexibleServers
- servers
- flexibleServers
- serverGroupsv2
- servers
- schedules
- bootstrapConfigurations
- orderItems
- orders
- clusters
- namespaces
- capacities - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Fabric/UnlimitedResourceGroupQuota
- guestConfigurationAssignments
- machines
- machines/extensions
- machines/runcommands
- integrationAccounts
- workflows
- mediaservices/liveEvents
- netAppAccounts
- netAppAccounts/capacityPools
- netAppAccounts/capacityPools/volumes
- netAppAccounts/capacityPools/volumes/mountTargets
- netAppAccounts/capacityPools/volumes/snapshots
- netAppAccounts/capacityPools/volumes/subvolumes
- netAppAccounts/capacityPools/volumes/volumeQuotaRules
- netAppAccounts/snapshotPolicies
- netAppAccounts/volumeGroups
- applicationSecurityGroups
- customIpPrefixes
- ddosProtectionPlans
- loadBalancers - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.Resources/ARMDisableResourcesPerRGLimit
- networkIntentPolicies
- networkInterfaces
- networkSecurityGroups
- privateEndpointRedirectMaps
- privateEndpoints
- privateLinkServices
- publicIPAddresses
- serviceEndpointPolicies
- virtualNetworkTaps
- volumes
- vpnBranches - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.NetworkFunction/AllowNaasVpnAccess
- namespaces - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.NotificationHubs/ARMDisableResourcesPerRGLimit
- namespaces/notificationHubs - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.NotificationHubs/ARMDisableResourcesPerRGLimit
- workspaceCollections - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.PowerBI/UnlimitedQuota
- autoScaleVCores - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.PowerBIDedicated/UnlimitedResourceGroupQuota
- capacities - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.PowerBIDedicated/UnlimitedResourceGroupQuota
- namespaces
- assignments
- securityConnectors
- securityConnectors/devops
- namespaces
- accounts
- accounts/accountQuotaPolicies
- accounts/groupPolicies
- accounts/jobs
- accounts/models
- accounts/networks
- accounts/secrets
- accounts/storageContainers
- instancePools
- managedInstances
- managedInstances/databases
- managedInstances/metricDefinitions
- managedInstances/metrics
- managedInstances/sqlAgent
- servers
- servers/databases
- servers/databases/databaseState
- servers/elasticpools
- servers/jobAccounts
- servers/jobAgents
- virtualClusters
- sqlVirtualMachines
- storageAccounts
- streamingjobs - By default, limited to 800 instances. That limit can be increased by registering the following features - Microsoft.StreamAnalytics/ASADisableARMResourcesPerRGLimit
- apiManagementAccounts/apis
- sites
For a complete list of quotas and limits, see Azure subscription and service limits, quotas, and constraints.