AADSTS565051 - The directory object quota limit for the Tenant has been exceeded.

Question

The following warning is displayed in the Microsoft Entra Admin Center for our tenant:

Tenant object quota: 521 of 500 objects used (~104%)

In addition, we receive the following error message:

AADSTS565051 - The directory object quota limit for the Tenant has been exceeded.

Our primary domain is verified.

Based on our analysis, it appears that the tenant's directory object quota has been reached, or that the tenant is incorrectly limited to only 500 directory objects.

For reference, the tenant currently contains only:

• 40 users
• 22 groups
• 10 devices
• 2 applications

Despite this relatively small number of visible objects, the tenant object quota shows 521 of 500 objects used.

We asked the MS Support to review the tenant's directorySizeQuota configuration and, if necessary, correct or increase the quota. The answer was to contact Azure Support. But there we would need a support plan.

Imho this is an MS Entra Quota issue and not Azure.

How can we solve this issue other than with the suggested Azure support plan?

Answer 1

Hi ADAPT Admin

Based on the information you shared, the 500-object total shown for the tenant appears to require further investigation. According to the current service limits documentation, the default directory quota is normally 50,000 resources, or 300,000 resources when the organization has at least one verified domain. Newly created tenants can temporarily have a lower quota during their first two days, but the currently documented temporary limit is 600 objects, after which the standard quota is restored automatically.

Service limits and restrictions - Microsoft Entra ID | Microsoft Learn

It is also important to note that the directory quota is not necessarily limited to the users, groups, devices, and applications currently visible in the . For example, active resources and deleted resources that are still available for restoration can contribute to directory quota usage. Therefore, the 521 objects reported by the quota may include additional directory objects that are not immediately apparent from those categories.

However, if the tenant is not newly created, has a verified domain, and directorySizeQuota.total is actually reporting only 500, that value does not correspond to the standard directory limits currently documented for

Similar cases involving a directorySizeQuota.total value of 500 have also been discussed in Tenant directory quota limit - Microsoft Q&A. In one such case, the issue could be brought to the engineering team for further review.

Since you already have an open Microsoft support case, I would recommend asking the current support engineer to escalate or transfer the case to the Microsoft Entra ID team for a backend review of the tenant's directorySizeQuota configuration. The reported total quota of 500 does not correspond to the standard Microsoft Entra directory quotas currently documented by Microsoft.

When requesting the escalation, please include the Tenant ID, verified-domain status, the AADSTS565051 error, the directorySizeQuotavalue showing 521/500, and your existing support case number. This should help the appropriate Microsoft Entra engineering/support team investigate the tenant-level quota configuration.

If the backend quota value itself is incorrectly configured, this is generally not something that can be corrected through the by a tenant administrator. Microsoft's documentation also directs organizations to Microsoft Support when the directory service quota needs to be increased. (Error (This company has exceeded the number of objects that can be synchronized) displays in a direc…)

I hope this information helpful.