Skip to content

Commit 8aa7431

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 3069757 + 5b073ca commit 8aa7431

File tree

127 files changed

+1981
-611
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

127 files changed

+1981
-611
lines changed

articles/active-directory/develop/msal-js-initializing-client-applications.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ Below is the total set of configurable options that are supported currently in t
113113
* `https://login.microsoftonline.com/common`- Used to sign in users with work and school accounts or a Microsoft personal account.
114114
* `https://login.microsoftonline.com/organizations/`- Used to sign in users with work and school accounts.
115115
* `https://login.microsoftonline.com/consumers/` - Used to sign in users with only personal Microsoft account (live).
116-
* In Azure AD B2C, it is of the form `https://<instance>/tfp/<tenant>/<policyName>/`, where instance is the Azure AD B2C domain, tenant is the name of the Azure AD B2C tenant, policyName is the name of the B2C policy to apply.
116+
* In Azure AD B2C, it is of the form `https://<instance>/tfp/<tenant>/<policyName>/`, where instance is the Azure AD B2C domain i.e. {your-tenant-name}.b2clogin.com, tenant is the name of the Azure AD B2C tenant i.e. {your-tenant-name}.onmicrosoft.com, policyName is the name of the B2C policy to apply.
117117

118118

119119
- **validateAuthority**: Optional. Validate the issuer of tokens. Default is `true`. For B2C applications, since the authority value is known and can be different per policy, the authority validation will not work and has to be set to `false`.

articles/active-directory/manage-apps/define-conditional-rules-for-provisioning-user-accounts.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,8 +89,9 @@ Scoping filters are configured as part of the attribute mappings for each Azure
8989
g. **REGEX MATCH**. Clause returns "true" if the evaluated attribute matches a regular expression pattern. For example: ([1-9][0-9]) matches any number between 10 and 99.
9090

9191
h. **NOT REGEX MATCH**. Clause returns "true" if the evaluated attribute doesn't match a regular expression pattern.
92-
93-
8. Select **Add new scoping clause**.
92+
93+
>[!IMPORTANT]
94+
> The Includes and IsMemberOf filters are not supported. They will soon be removed from the UI.
9495
9596
9. Optionally, repeat steps 7-8 to add more scoping clauses.
9697

articles/application-gateway/application-gateway-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The following metrics related to timing of the request and response are availabl
3131

3232
Average time that it takes for a request to be processed and its response to be sent. This is calculated as average of the interval from the time when Application Gateway receives the first byte of an HTTP request to the time when the response send operation finishes. It's important to note that this usually includes the Application Gateway processing time, time that the request and response packets are traveling over the network and the time the backend server took to respond.
3333

34-
If the *Client RTT* is much more than the *Application gateway total time*, then it can be deduced that the latency observed by the client is due to the network connectivity between the client and Application Gateway. If both the latencies are comparable, then the high latency could be due to any of the following: Application Gateway, the network between the Application Gateway and the backend application, or the backend application performance.
34+
After filtering by listener, if the *Client RTT* is much more than the *Application gateway total time*, then it can be deduced that the latency observed by the client is due to the network connectivity between the client and Application Gateway. If both the latencies are comparable, then the high latency could be due to any of the following: Application Gateway, the network between the Application Gateway and the backend application, or the backend application performance.
3535

3636
- **Backend first byte response time**
3737

articles/billing/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@
149149
href: billing-understand-mca-roles.md
150150
- name: Link partner ID
151151
href: billing-partner-admin-link-started.md
152-
- name: Organize costs with invoice sections
152+
- name: Organize costs by customizing your billing account - Microsoft Customer Agreement
153153
href: billing-mca-section-invoice.md
154154
- name: EA tasks in Microsoft Customer Agreement
155155
href: billing-mca-enterprise-operations.md

articles/billing/billing-mca-section-invoice.md

Lines changed: 200 additions & 13 deletions
Large diffs are not rendered by default.
98.5 KB
Loading
163 KB
Loading
17.7 KB
Loading
26 KB
Loading
78.4 KB
Loading

0 commit comments

Comments
 (0)