Skip to content

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

rpakala-ms
Copy link
Contributor

Add Japan go-local b2c quota limits

Add Japan go-local b2c quota limits
Copy link
Contributor

@rpakala-ms : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit f4cf7e1:

✅ Validation status: passed

File Status Preview URL Details
articles/active-directory-b2c/service-limits.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@kengaderdus

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Aug 14, 2025
@@ -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) |
Copy link
Contributor

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)|
Copy link
Contributor

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)

@v-dirichards
Copy link
Contributor

@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 #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants