Merge pull request #183511 from MicrosoftDocs/master

12/22 AM Publishing

Author: v-alje

.openpublishing.redirection.json

@@ -44508,6 +44508,11 @@
       "redirect_url": "/azure/communication-services/concepts/telephony/port-phone-number",
       "redirect_document_id": false
     },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/voice-video-calling/pstn-call.md",
+        "redirect_url": "/azure/communication-services/quickstarts/telephony/pstn-call",
+        "redirect_document_id": false
+      },
     {
       "source_path_from_root": "/articles/communication-services/concepts/telephony-sms/concepts.md",
       "redirect_url": "/azure/communication-services/concepts/sms/concepts",

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

@@ -9,7 +9,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 12/09/2021
+ms.date: 12/21/2021
 ms.author: mimart
 ms.subservice: B2C
 zone_pivot_groups: b2c-policy-type
@@ -38,13 +38,13 @@ The frequency of requests made to Azure AD B2C endpoints determine the overall t
 
 |Endpoint                 |Endpoint type     |Requests consumed |
 |-----------------------------|---------|------------------|
-|/oauth2/v2.0/authorize       |Dynamic  |Varies<sup>1</sup>|
+|/oauth2/v2.0/authorize       |Dynamic  |Varies <sup>1</sup>|
 |/oauth2/v2.0/token           |Static   |1                 |
 |/openid/v2.0/userinfo        |Static   |1                 |
 |/.well-known/openid-config   |Static   |1                 |
 |/discovery/v2.0/keys         |Static   |1                 |
 |/oauth2/v2.0/logout          |Static   |1                 |
-|/samlp/sso/login             |Dynamic  |Varies<sup>1</sup>|
+|/samlp/sso/login             |Dynamic  |Varies <sup>1</sup>|
 |/samlp/sso/logout            |Static   |1                 |
 
 ::: zone pivot="b2c-user-flow"
@@ -97,11 +97,13 @@ The token issuance rate of a Custom Policy is dependent on the number of request
 |Starter Pack |Scenario |User journey ID |Requests consumed|
 |---------|---------|---------|---------|
 |LocalAccounts| Sign-in| SignUpOrSignIn |2|
+|LocalAccounts SocialAndLocalAccounts | Sign-up| SignUpOrSignIn |6|
 |LocalAccounts|Profile edit| ProfileEdit |2|
-|LocalAccounts SocialAndLocalAccounts| PasswordReset| Password reset| 6|
+|LocalAccounts SocialAndLocalAccounts SocialAndLocalAccountsWithMfa| Password reset| PasswordReset| 6|
 |SocialAndLocalAccounts| Federated account sign-in|SignUpOrSignIn| 4|
 |SocialAndLocalAccounts| Federated account sign-up|SignUpOrSignIn| 6|
 |SocialAndLocalAccountsWithMfa| Local account sign-in with MFA|SignUpOrSignIn |6|
+|SocialAndLocalAccountsWithMfa| Local account sign-up with MFA|SignUpOrSignIn |10|
 |SocialAndLocalAccountsWithMfa| Federated account sign-in with MFA|SignUpOrSignIn| 8|
 |SocialAndLocalAccountsWithMfa| Federated account sign-up with MFA|SignUpOrSignIn |10|
 
@@ -115,9 +117,9 @@ To obtain the token issuance rate per second for a particular user journey:
 Tokens/sec = 200/requests-consumed
 ```
 
-## Calculate the token issuance capability of your Custom Policy
+## Calculate the token issuance rate of your Custom Policy
 
-When you create your own Custom Policy, the number of requests consumed at the dynamic endpoint depends on which features a user traverses through. The below table shows how many requests are consumed for each feature in your Custom Policy.
+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.
 
 |Feature                                          |Requests consumed|
 |-------------------------------------------------|-----------------|

articles/active-directory/hybrid/reference-connect-version-history.md

@@ -58,13 +58,6 @@ Required permissions | For permissions required to apply an update, see [account
 >
 > Please follow this link to read more about [auto upgrade](how-to-connect-install-automatic-upgrade.md).
 
-## 2.0.89.0
-
-### Release status
-12/21/2021: Released for download only, not available for auto upgrade.
-
-### Bug fixes
-- We fixed a bug in version 2.0.88.0 where, under certain conditions, linked mailboxes of disabled users were getting deleted.
 
 ## 2.0.88.0
 > [!NOTE] 

articles/api-management/api-management-log-to-eventhub-sample.md

@@ -12,7 +12,7 @@ ms.assetid: c528cf6f-5f16-4a06-beea-fa1207541a47
 ms.service: api-management
 ms.workload: mobile
 ms.tgt_pltfrm: na
-ms.devlang: dotnet
+ms.devlang: csharp
 ms.custom: devx-track-csharp
 ms.topic: article
 ms.date: 01/23/2018

articles/api-management/api-management-sample-cache-by-key.md

@@ -9,8 +9,6 @@ editor: ''
 
 ms.assetid: 772bc8dd-5cda-41c4-95bf-b9f6f052bc85
 ms.service: api-management
-ms.devlang: dotnet
-ms.custom: devx-track-csharp
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na

articles/api-management/api-management-sample-flexible-throttling.md

@@ -9,8 +9,6 @@ editor: ''
 
 ms.assetid: fc813a65-7793-4c17-8bb9-e387838193ae
 ms.service: api-management
-ms.devlang: dotnet
-ms.custom: devx-track-csharp
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na

articles/api-management/api-management-sample-send-request.md

@@ -9,8 +9,6 @@ editor: ''
 
 ms.assetid: 4539c0fa-21ef-4b1c-a1d4-d89a38c242fa
 ms.service: api-management
-ms.devlang: dotnet
-ms.custom: devx-track-csharp
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na

articles/app-service/configure-authentication-customize-sign-in-out.md

@@ -125,13 +125,22 @@ az webapp config appsettings set --name <app_name> --resource-group <group_name>
 
 Both Microsoft Account and Azure Active Directory lets you sign in from multiple domains. For example, Microsoft Account allows _outlook.com_, _live.com_, and _hotmail.com_ accounts. Azure AD allows any number of custom domains for the sign-in accounts. However, you may want to accelerate your users straight to your own branded Azure AD sign-in page (such as `contoso.com`). To suggest the domain name of the sign-in accounts, follow these steps.
 
-In [https://resources.azure.com](https://resources.azure.com), navigate to **subscriptions** > **_\<subscription\_name_** > **resourceGroups** > **_\<resource\_group\_name>_** > **providers** > **Microsoft.Web** > **sites** > **_\<app\_name>_** > **config** > **authsettings**. 
-
-Click **Edit**, modify the following property, and then click **Put**. Be sure to replace _\<domain\_name>_ with the domain you want.
+1. In [https://resources.azure.com](https://resources.azure.com), At the top of the page, select **Read/Write**.
+2. In the left browser, navigate to **subscriptions** > **_\<subscription-name_** > **resourceGroups** > **_\<resource-group-name>_** > **providers** > **Microsoft.Web** > **sites** > **_\<app-name>_** > **config** > **authsettingsV2**.
+3. Click **Edit**.
+4. Add a `loginParameters` array with a `domain_hint` item.
+
+    ```json
+    "identityProviders": {
+        "azureActiveDirectory": {
+            "login": {
+                "loginParameters": ["domain_hint=<domain-name>"],
+            }
+        }
+    }
+    ```
 
-```json
-"additionalLoginParams": ["domain_hint=<domain_name>"]
-```
+5. Click **Put**.
 
 This setting appends the `domain_hint` query string parameter to the login redirect URL. 
 

articles/app-service/deploy-zip.md

@@ -174,19 +174,19 @@ The CLI command uses the [Kudu publish API](#kudu-publish-api-reference) to depl
 ### Deploy a startup script
 
 ```bash
-az webapp deploy --resource group <group-name> --name <app-name> --src-path scripts/startup.sh --type=startup
+az webapp deploy --resource-group <group-name> --name <app-name> --src-path scripts/startup.sh --type=startup
 ```
 
 ### Deploy a library file
 
 ```bash
-az webapp deploy --resource group <group-name> --name <app-name> --src-path driver.jar --type=lib
+az webapp deploy --resource-group <group-name> --name <app-name> --src-path driver.jar --type=lib
 ```
 
 ### Deploy a static file
 
 ```bash
-az webapp deploy --resource group <group-name> --name <app-name> --src-path config.json --type=static
+az webapp deploy --resource-group <group-name> --name <app-name> --src-path config.json --type=static
 ```
 
 # [Azure PowerShell](#tab/powershell)

articles/app-service/resources-kudu.md

@@ -12,7 +12,8 @@ Kudu is the engine behind a number of features in [Azure App Service](overview.m
 Anytime you create an app, App Service creates a companion app for it that's secured by HTTPS. This Kudu app is accessible at:
 
 - App not in Isolated tier: `https://<app-name>.scm.azurewebsites.net`
-- App in Isolated tier (App Service Environment): `https://<app-name>.scm.<ase-name>.p.azurewebsites.net`
+- Internet-facing app in Isolated tier (App Service Environment): `https://<app-name>.scm.<ase-name>.p.azurewebsites.net`
+- Internal app in Isolated tier (ILB App Service Environment): `https://<app-name>.scm.<ase-name>.appserviceenvironment.net`
 
 For more information, see [Accessing the kudu service](https://github.com/projectkudu/kudu/wiki/Accessing-the-kudu-service).