A cloud-based identity and access management service for securing user authentication and resource access
Hi @João Santos
Thank you for reaching out to Microsoft Q&A. I understand your having an issue with the ceiling on the amount of directory objects you can create.
A verified custom domain should already put your tenant on the higher default quota (300,000 objects), not 500. What you're seeing isn't expected behavior for a tenant in your situation. It also looks like a backend provisioning issue rather than anything you can fix from the admin center.
That said, I've seen this exact pattern come up a few times in other threads, and in each case, it turned out the tenant just hadn't been provisioned with the correct quota on the backend. The fix required Microsoft's engineering team to review and raise it manually. I'm sorry to say there's no admin-side setting for this.
A couple of things worth doing before/while you open a ticket:
- Double-check the actual numbers via Microsoft Graph:
GET https://graph.microsoft.com/beta/organization?$select=directorySizeQuota(needsOrganization.Read.All). This gives you the realused/totalvalues to include in your case. - Open a support request through the M365 admin center (Help & support) and mention specifically that you have a verified custom domain, but the quota is showing 500 instead of the standard 300,000. That detail is what gets it routed to engineering quickly.
- If you ever need to go beyond the standard 300,000 for an Education tenant, that's a separate ask handled by the EDU Customer Success Team (not needed for your current issue, just for reference).
Good luck I hope this gets resolved for you expeditiously!
Please 'Upvote' (Thumbs-up) and 'Accept' as answer if the response was helpful. This will be benefitting other community members who face the same issue.
Best regards, Andrew S Taylor