Merge pull request #231736 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/authentication/howto-authentication-passwordless-phone.md

@@ -85,7 +85,7 @@ Users can register for passwordless phone sign-in directly within the Microsoft
 1. Acquire a [Temporary Access Pass](../authentication/howto-authentication-temporary-access-pass.md) from your Admin or Organization. 
 2. Download and install the Microsoft Authenticator app on your mobile device. 
 3. Open Microsoft Authenticator and click **Add account** and then choose **Work or school account.**
-4. Choose **Sign in." 
+4. Choose **Sign in**. 
 5. Follow the instructions to sign-in with your account using the Temporary Access Pass provided by your Admin or Organization. 
 6. Once signed-in, continue following the additional steps to set up phone sign-in. 
 

articles/cognitive-services/includes/quickstarts/sku-pricing.md

@@ -51,6 +51,11 @@ See the list of SKUs and pricing information below.
 | Content Moderator | `ContentModerator` |
 | Personalizer      | `Personalizer`     |
 
+#### Azure OpenAI
+
+| Service           | Kind               |
+|-------------------|--------------------|
+| Azure OpenAI      | `OpenAI`           |
 
 #### Pricing tiers and billing
 

articles/cognitive-services/language-service/question-answering/how-to/authoring.md

@@ -479,7 +479,7 @@ curl -X POST -H "Ocp-Apim-Subscription-Key: {API-KEY}" -H "Content-Type: applica
   }' -i 'https://{ENDPOINT}.api.cognitive.microsoft.com/language/query-knowledgebases/projects/{PROJECT-NAME}/:import?api-version=2021-10-01&format=tsv'
 ```
 
-A successful call to deploy a project results in an `Operation-Location` header being returned, which can be used to check the status of the import job. In many of our examples, we haven't needed to look at the response headers and thus haven't been displaying them. To retrieve the response headers our curl command uses `-i`. Without this additional parameter prior to the endpoint address, the response to this command would appear empty as if no response occurred.
+A successful call to import a project results in an `Operation-Location` header being returned, which can be used to check the status of the import job. In many of our examples, we haven't needed to look at the response headers and thus haven't been displaying them. To retrieve the response headers our curl command uses `-i`. Without this additional parameter prior to the endpoint address, the response to this command would appear empty as if no response occurred.
 
 ### Example response
 
@@ -807,4 +807,4 @@ apim-request-id: 92225e03-e83f-4c7f-b35a-223b1b0f29dd
 strict-transport-security: max-age=31536000; includeSubDomains; preload
 x-content-type-options: nosniff
 date: Wed, 24 Nov 2021 04:02:56 GMT
-```
+```

articles/expressroute/expressroute-howto-reset-peering.md

@@ -129,14 +129,22 @@ There are a two scenarios where you may find it helpful to reset your ExpressRou
    AllowClassicOperations           : False
    GatewayManagerEtag               :
    ```
-6. Run the following commands to change the state of the peering.
+6. Run the following commands to change the peering state to disabled.
 
    ```azurepowershell-interactive
    $ckt.Peerings[0].State = "Disabled"
    Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
    ```
-   The peering should be in a state you set. 
+   The peering should be in a disabled state you set. 
 
+7. Run the following commands to change the peering state back to enabled.
+
+   ```azurepowershell-interactive
+   $ckt.Peerings[0].State = "Enabled"
+   Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt
+   ```
+   The peering should be in a enabled state you set.
+   
 ## Next steps
 If you need help with troubleshooting an ExpressRoute problem, see the following articles:
 * [Verifying ExpressRoute connectivity](expressroute-troubleshooting-expressroute-overview.md)

articles/frontdoor/standard-premium/how-to-enable-private-link-internal-load-balancer.md

@@ -60,7 +60,7 @@ In this section, you'll map the Private Link service to a private endpoint creat
     | Resource | If you select **In my directory**, specify the Private Link Service resource for the ILB in your subscription. |
     | ID/alias | If you select **By ID or alias**, specify the resource ID of the Private Link Service resource you want to enable private link to. |
     | Region | Select the region that is the same or closest to your origin. |
-    | Request message | Customize message or choose the default. |
+    | Request message | Custom message to see while approving the Private Endpoint. |
 
 1. Then select **Add** and then **Update** to save the origin group settings.
 

articles/service-bus-messaging/message-sessions.md

@@ -21,7 +21,7 @@ On session-aware queues or subscriptions, sessions come into existence when ther
 Typically, however, an application has a clear notion of where a set of related messages starts and ends. Service Bus doesn't set any specific rules. For example, your application could set the **Label** property for the first message to **start**, for intermediate messages to **content**, and for the last message to **end**. The relative position of the content messages can be computed as the current message *SequenceNumber* delta from the **start** message *SequenceNumber*.
 
 > [!IMPORTANT]
-> When sessions are enabled on a queue or a subscription, the client applications can ***no longer*** send/receive regular messages. All messages must be sent as part of a session (by setting the session id) and received by accepting the session.
+> When sessions are enabled on a queue or a subscription, the client applications can ***no longer*** send/receive regular messages. All messages must be sent as part of a session (by setting the session id) and received by accepting the session. Clients may still peek a queue or subscription that has sessions enabled. See [Message browsing](message-browsing.md).
 
 The APIs for sessions exist on queue and subscription clients. There's an imperative model that controls when sessions and messages are received, and a handler-based model that hides the complexity of managing the receive loop. 
 

articles/virtual-network/what-is-ip-address-168-63-129-16.md

@@ -39,6 +39,9 @@ The public IP address 168.63.129.16 is used in all regions and all national clou
 - When the VM is part of a load balancer backend pool, [health probe](../load-balancer/load-balancer-custom-probe-overview.md) communication should be allowed to originate from 168.63.129.16. The default network security group configuration has a rule that allows this communication. This rule leverages the [AzureLoadBalancer](../virtual-network/service-tags-overview.md#available-service-tags) service tag. If desired this traffic can be blocked by configuring the network security group however this will result in probes that fail.
 
 ## Troubleshoot connectivity
+> [!NOTE]
+> When running the tests below, the action need to be run as Administrator (Windows) and Root (Linux) to ensure accurate results.
+
 ### Windows OS
 You can test communication to 168.63.129.16 by using the following tests with PowerShell.