Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Resource limits are enforced through quotas and throttling. Microsoft Entra ID and the individual Microsoft 365 services use both methods. Limits are service-specific and change over time as new capabilities are added. For details on the current limits for the various services, see the following topics:
- Microsoft Entra service limits and restrictions
- Exchange Limits
- SharePoint software boundaries and limits
- File Size Limits in Sway
In addition to these limits, Microsoft Entra ID and Microsoft 365 use several throttling mechanisms. Throttling within the service is especially important because network resources in Microsoft's datacenters are optimized for the broad set of customers that use the services. Throttling mechanisms include:
- Microsoft Entra ID and Microsoft 365 feature user-level throttling, which limit the number of transactions or concurrent calls (by script or code) that a single user can perform.
- A default PowerShell throttling policy that the service assigns to each tenant when it creates the tenant. These settings affect other items, such as the maximum number of simultaneous PowerShell sessions that a single administrator can open.
- Each Exchange Online customer has a default Exchange Web Services (EWS) policy that the service tunes for EWS client operations, and throttling that applies to all Outlook clients.