Skip to content

Commit 6be3cea

Browse files
committed
add note to contact support if customer wished to increase service limit
1 parent e66cb28 commit 6be3cea

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/active-directory-b2c/service-limits.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The number of users able to authenticate through an Azure AD B2C tenant is gated
3636

3737
Azure AD B2C is compliant with [OAuth 2.0](https://datatracker.ietf.org/doc/html/rfc6749), [OpenID Connect (OIDC)](https://openid.net/certification), and [SAML](http://saml.xml.org/saml-specifications) protocols. It provides user authentication and single sign-on (SSO) functionality, with the endpoints listed in the following table.
3838

39-
The frequency of requests made to Azure AD B2C endpoints determine the overall token issuance capability. Azure AD B2C exposes endpoints which consume a different number of requests. Review the [Authentication Protocols](./protocols-overview.md) article for more information on which endpoints are consumed by your application.
39+
The frequency of requests made to Azure AD B2C endpoints determines the overall token issuance capability. Azure AD B2C exposes endpoints, which consume a different number of requests. Review the [Authentication Protocols](./protocols-overview.md) article for more information on which endpoints are consumed by your application.
4040

4141
|Endpoint |Endpoint type |Requests consumed |
4242
|-----------------------------|---------|------------------|
@@ -105,9 +105,9 @@ The token issuance rate of a Custom Policy is dependent on the number of request
105105
|SocialAndLocalAccounts| Federated account sign-in|SignUpOrSignIn| 4|
106106
|SocialAndLocalAccounts| Federated account sign-up|SignUpOrSignIn| 6|
107107
|SocialAndLocalAccountsWithMfa| Local account sign-in with MFA|SignUpOrSignIn |6|
108-
|SocialAndLocalAccountsWithMfa| Local account sign-up with MFA|SignUpOrSignIn |10|
108+
|SocialAndLocalAccountsWithMfa| Local account sign up with MFA|SignUpOrSignIn |10|
109109
|SocialAndLocalAccountsWithMfa| Federated account sign-in with MFA|SignUpOrSignIn| 8|
110-
|SocialAndLocalAccountsWithMfa| Federated account sign-up with MFA|SignUpOrSignIn |10|
110+
|SocialAndLocalAccountsWithMfa| Federated account sign up with MFA|SignUpOrSignIn |10|
111111

112112
To obtain the token issuance rate per second for a particular user journey:
113113

@@ -121,7 +121,7 @@ Tokens/sec = 200/requests-consumed
121121

122122
## Calculate the token issuance rate of your Custom Policy
123123

124-
You can craete your own Custom Policy to provide a unique authentication experience for your application. The number of requests consumed at the dynamic endpoint depends on which features a user traverses through your Custom Policy. The below table shows how many requests are consumed for each feature in a Custom Policy.
124+
You can create your own Custom Policy to provide a unique authentication experience for your application. The number of requests consumed at the dynamic endpoint depends on which features a user traverses through your Custom Policy. The below table shows how many requests are consumed for each feature in a Custom Policy.
125125

126126
|Feature |Requests consumed|
127127
|-------------------------------------------------|-----------------|
@@ -150,7 +150,7 @@ You can optimize the token issuance rate by considering the following configurat
150150
- Increasing access and refresh [token lifetimes](./configure-tokens.md).
151151
- Increasing the Azure AD B2C [web session lifetime](./session-behavior.md).
152152
- Enabling [Keep Me Signed In](./session-behavior.md#enable-keep-me-signed-in-kmsi).
153-
- Caching the [OpenId Connect metadata](./openid-connect.md#validate-the-id-token) documents at your API's.
153+
- Caching the [OpenId Connect metadata](./openid-connect.md#validate-the-id-token) documents at your APIs.
154154
- Enforcing conditional MFA using [Conditional Access](./conditional-access-identity-protection-overview.md).
155155

156156
## Azure AD B2C configuration limits
@@ -162,7 +162,7 @@ The following table lists the administrative configuration limits in the Azure A
162162
|Number of scopes per application  |1000 |
163163
|Number of [custom attributes](user-profile-attributes.md#extension-attributes) per user <sup>1</sup> |100 |
164164
|Number of redirect URLs per application |100 |
165-
|Number of sign out URLs per application  |1 |
165+
|Number of sign-out URLs per application  |1 |
166166
|String Limit per Attribute |250 Chars |
167167
|Number of B2C tenants per subscription |20 |
168168
|Levels of [inheritance](custom-policy-overview.md#inheritance-model) in custom policies |10 |

0 commit comments

Comments
 (0)