Skip to content

Commit 8ead8d5

Browse files
committed
support caps
1 parent add763b commit 8ead8d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/active-directory-service-limits-include.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Here are the usage constraints and other service limits for the Azure Active Dir
1515
| --- | --- |
1616
| Directories | A single user can belong to a maximum of 500 Azure AD directories as a member or a guest.<br/>A single user can create a maximum of 20 directories. |
1717
| Domains | You can add no more than 900 managed domain names. If you set up all of your domains for federation with on-premises Active Directory, you can add no more than 450 domain names in each directory. |
18-
|Resources |<ul><li>A maximum of 50,000 Azure AD resources can be created in a single directory by users of the Free edition of Azure Active Directory by default. If you have at least one verified domain, the default Azure AD service quota for your organization is extended to 300,000 Azure AD resources. This service limit is unrelated to the pricing tier limit of 500,000 resources on the Azure AD pricing page. To go beyond the default quota, you must contact support.</li><li>A non-admin user can create no more than 250 Azure AD resources. Both active resources and deleted resources that are available to restore count toward this quota. Only deleted Azure AD resources that were deleted fewer than 30 days ago are available to restore. Deleted Azure AD resources that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. If you have developers who are likely to repeatedly exceed this quota in the course of their regular duties, you can [create and assign a custom role](../articles/active-directory/users-groups-roles/roles-quickstart-app-registration-limits.md) with permission to create a limitless number of app registrations.</li></ul> |
18+
|Resources |<ul><li>A maximum of 50,000 Azure AD resources can be created in a single directory by users of the Free edition of Azure Active Directory by default. If you have at least one verified domain, the default Azure AD service quota for your organization is extended to 300,000 Azure AD resources. This service limit is unrelated to the pricing tier limit of 500,000 resources on the Azure AD pricing page. To go beyond the default quota, you must contact Microsoft Support.</li><li>A non-admin user can create no more than 250 Azure AD resources. Both active resources and deleted resources that are available to restore count toward this quota. Only deleted Azure AD resources that were deleted fewer than 30 days ago are available to restore. Deleted Azure AD resources that are no longer available to restore count toward this quota at a value of one-quarter for 30 days. If you have developers who are likely to repeatedly exceed this quota in the course of their regular duties, you can [create and assign a custom role](../articles/active-directory/users-groups-roles/roles-quickstart-app-registration-limits.md) with permission to create a limitless number of app registrations.</li></ul> |
1919
| Schema extensions |<ul><li>String-type extensions can have a maximum of 256 characters. </li><li>Binary-type extensions are limited to 256 bytes.</li><li>Only 100 extension values, across *all* types and *all* applications, can be written to any single Azure AD resource.</li><li>Only User, Group, TenantDetail, Device, Application, and ServicePrincipal entities can be extended with string-type or binary-type single-valued attributes.</li><li>Schema extensions are available only in the Graph API version 1.21 preview. The application must be granted write access to register an extension.</li></ul> |
2020
| Applications |A maximum of 100 users can be owners of a single application. |
2121
|Application Manifest |A maximum of 1200 entries can be added in the Application Manifest. |

0 commit comments

Comments
 (0)