Azure service limits and known issues

Every Azure service has a set of physical limitations by design. When planning and designing Microsoft Azure-based solutions, these Azure service physical limits should always be taken into account. This article items to consider around Azure service limits and known issues.

More specifically, Azure has a number of subscription and service limits as well as default quotas and constraints. The following Microsoft article describes all these limitations organized by service: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits.

Each Azure service has its own limits and known issues, as described below.

When designing any Azure infrastructure, you must take into account the following notes:

Some services have adjustable limits. When a service doesn't have adjustable limits, the following tables use the header Limit. In those cases, the default and the maximum limits are the same. When the limit can be adjusted, the tables include Default limit and Maximum limit headers. The limit can be raised above the default limit but not above the maximum limit. If you want to raise the limit or quota above the default limit, open an online customer support request at no charge. The terms soft limit and hard limit often are used informally to describe the current, adjustable limit (soft limit) and the maximum limit (hard limit). If a limit isn't adjustable, there won't be a soft limit, only a hard limit. Free Trial subscriptions aren't eligible for limit or quota increases. If you have a Free Trial subscription, you can upgrade to a Pay-As-You-Go subscription. Also bear in mind that some limits are managed at a regional level.
You can always request quota increases for a specific Azure service, component, in a specific region. The following article provides guidance on how to request quota increases in Azure: https://azure.microsoft.com/en-us/blog/azure-limits-quotas-increase-requests/.
On top of the above limitations, there are known Azure Resource Manager throttling limits at tenant and subscription level, as described in the following article: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/request-limits-and-throttling.
There are also a number of Azure resource naming limits per each Azure resource provider, as described in the following article: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules.
Take into account not only the resource limits but also potential deprecation notice of any Azure services. Refer to the following article for more details on identifying Azure discontinued services: https://stefanos.cloud/list-of-discontinued-services-in-microsoft-azure/.
On top of the above articles, it is important to always perform the following Web search for getting any more up-to-date Azure resource limits you might have omitted to take into account.

"[Azure service] resource limits" site:learn.microsoft.com
#[Azure services] is the service you are planning and designing, e.g. Azure Virtual Machines

Another very important Web search is the following. This should always be run as part of an Azure architecture design and should be part of your Azure design considerations, for example when designing an Azure App Service infrastructure. By running the following Web search, you can be rest assured that you have taken into account all possible known issues and limitations of any Azure service used in your architecture.

#[service name is the Azure service whose potential limitations and known issues you wish to research]
"limitations and known issues" OR "known issues and limitations"[service name] site:learn.microsoft.com

As a conclusion, taking into account the above Azure service and component limits as well as potential known issues and limitations at an early stage is critical when planning or designing Azure solutions.

For Microsoft 365 service resource limits, refer to the following article: https://stefanos.cloud/microsoft-365-service-resource-limits/.