-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Update service-limits.md #127510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Update service-limits.md #127510
Conversation
Add Japan go-local b2c quota limits
@rpakala-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit f4cf7e1: ✅ Validation status: passed
For more details, please refer to the build report. |
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
@@ -169,8 +169,10 @@ The following table lists the administrative configuration limits in the Azure A | |||
|Number of sign-out URLs per application |1 | | |||
|String Limit per Attribute |250 Chars | | |||
|Number of B2C tenants per subscription |20 | | |||
|Total number of objects (user accounts and applications) per tenant (default limit)|1.25 million | | |||
|Total number of objects (user accounts and applications) per tenant (using a verified custom domain). If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|5.25 million | | |||
|Total number of objects per tenant (default limit)|1.25 million (1M user accounts and 250K applications) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we maintain the 1.25 million in the Limit column, then add notes below the table (reference using footnotes). How this work out? We want to keep the Limit column clean. We can then apply all this in the other new row.
|Total number of objects (user accounts and applications) per tenant (using a verified custom domain). If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|5.25 million | | ||
|Total number of objects per tenant (default limit)|1.25 million (1M user accounts and 250K applications) | | ||
|Total number of objects per tenant (using a verified custom domain). If you want to increase this limit, please contact [Microsoft Support](find-help-open-support-ticket.md).|5.25 million (5M user accounts and 250K applications) | | ||
|Japan Go-Local B2C Tenants - Total number of objects per tenant (default limit)|310,000 (60K user accounts and 250K applications)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can rephrase Japan Go-Local B2C Tenants - Total number of objects per tenant (default limit) to Number of objects per tenant for Japan Go-Local Azure AD B2C tenants (default limit)
@rpakala-ms Can you respond to the requested changes or let us know if you would like us to commit them? @kengaderdus - When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Add Japan go-local b2c quota limits