Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

articles/active-directory-b2c/conditional-access-identity-protection-overview.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: conditional-access
 ms.topic: overview
-ms.date: 05/28/2021
+ms.date: 11/23/2021
 
 ms.author: kengaderdus
 author: kengaderdus
@@ -43,7 +43,7 @@ Identity Protection and Conditional Access in Azure AD B2C generally work the sa
 
 - Identity Protection and Conditional Access aren't supported for ROPC server-to-server flows in Azure AD B2C tenants.
 
-- In Azure AD B2C tenants, Identity Protection risk detections are available for local B2C accounts only, and not for social identities like Google or Facebook.
+- In Azure AD B2C tenants, Identity Protection risk detections are available for both local and social identities, such as Google or Facebook. For social identities, Conditional Access must be activated. Detection is limited because the social account credentials are managed by the external identity provider.
 
 - In Azure AD B2C tenants, a subset of the Identity Protection risk detections is available. See [Investigate risk with Identity Protection](identity-protection-investigate-risk.md), and [Add Conditional Access to user flows](conditional-access-user-flow.md).
 

articles/active-directory-b2c/custom-domain.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 09/15/2021
+ms.date: 11/23/2021
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -28,6 +28,10 @@ This article describes how to enable custom domains in your redirect URLs for Az
 
 You can enable custom domains for Azure AD B2C by using [Azure Front Door](https://azure.microsoft.com/services/frontdoor/). Azure Front Door is a global entry point that uses the Microsoft global edge network to create fast, secure, and widely scalable web applications. You can render Azure AD B2C content behind Azure Front Door, and then configure an option in Azure Front Door to deliver the content via a custom domain in your application's URL.
 
+Watch this video to learn about Azure AD B2C custom domain.
+
+>[!Video https://www.youtube.com/embed/mVNB59VK-DQ]
+
 The following diagram illustrates Azure Front Door integration:
 
 1. From an application, a user selects the sign-in button, which takes them to the Azure AD B2C sign-in page. This page specifies a custom domain name.

articles/active-directory/devices/hybrid-azuread-join-federated-domains.md

@@ -82,7 +82,7 @@ Hybrid Azure AD join requires devices to have access to the following Microsoft
 - `https://autologon.microsoftazuread-sso.com` (If you use or plan to use seamless SSO)
 
 > [!WARNING]
-> If your organization uses proxy servers that intercept SSL traffic for scenarios like data loss prevention or Azure AD tenant restrictions, ensure that traffic to 'https://device.login.microsoftonline.com' is excluded from TLS break-and-inspect. Failure to exclude 'https://device.login.microsoftonline.com' may cause interference with client certificate authentication, causing issues with device registration and device-based Conditional Access.
+> If your organization uses proxy servers that intercept SSL traffic for scenarios like data loss prevention or Azure AD tenant restrictions, ensure that traffic to these URLs are excluded from TLS break-and-inspect. Failure to exclude these URLs may cause interference with client certificate authentication, cause issues with device registration, and device-based Conditional Access.
 
 Beginning with Windows 10 1803, if the instantaneous hybrid Azure AD join for a federated environment by using AD FS fails, we rely on Azure AD Connect to sync the computer object in Azure AD that's subsequently used to complete the device registration for hybrid Azure AD join. Verify that Azure AD Connect has synced the computer objects of the devices you want to be hybrid Azure AD joined to Azure AD. If the computer objects belong to specific organizational units (OUs), you must also configure the OUs to sync in Azure AD Connect. To learn more about how to sync computer objects by using Azure AD Connect, see [Configure filtering by using Azure AD Connect](../hybrid/how-to-connect-sync-configure-filtering.md#organizational-unitbased-filtering).
 

articles/active-directory/saas-apps/cisco-webex-provisioning-tutorial.md

@@ -53,7 +53,7 @@ Before configuring Cisco Webex for automatic user provisioning with Azure AD, yo
 
 4. In the search box, type **Cisco Webex**, select **Cisco Webex** from result panel then click **Add** button to add the application.
 
-    ![Cisco Webex in the results list](common/search-new-app.png)
+    ![Cisco Webex in the results list](media/cisco-webex-provisioning-tutorial/search-cisco-app.png)
 
 ## Assigning users to Cisco Webex
 

articles/active-directory/saas-apps/media/cisco-webex-provisioning-tutorial/search-cisco-app.png

@@ -231,7 +231,7 @@ Authorization: Bearer  <token>
 
 For the complete code, see one of the following code samples:
 
-- [C#](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/IssuerController.cs)
+- [C#](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs)
 - [Node.js](https://github.com/Azure-Samples/active-directory-verifiable-credentials-node/blob/main/1-node-api-idtokenhint/issuer.js)
 
 ## Presentation request example
@@ -317,7 +317,7 @@ try
 }
 ```
 
-For the complete code, see the [issuance](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/IssuerController.cs) and [presentation](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/AspNetCoreVerifiableCredentials/VerifierController.cs) code on the GitHub repo.
+For the complete code, see the [issuance](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs) and [presentation](https://github.com/Azure-Samples/active-directory-verifiable-credentials-dotnet/blob/main/1-asp-net-core-api-idtokenhint/IssuerController.cs) code on the GitHub repo.
 
 # [Node.js](#tab/nodejs)
 

articles/active-directory/verifiable-credentials/get-started-request-api.md

@@ -18,8 +18,16 @@ This article shows you how to create an RDP connection with an AKS node using th
 
 ## Before you begin
 
-This article assumes that you have an existing AKS cluster with a Windows Server node. If you need an AKS cluster, see the article on [creating an AKS cluster with a Windows container using the Azure CLI][aks-windows-cli]. You need the Windows administrator username and password for the Windows Server node you want to troubleshoot. If you don't know them, you can reset them by following [Reset Remote Desktop Services or its administrator password in a Windows VM
-](/troubleshoot/azure/virtual-machines/reset-rdp). You also need an RDP client such as [Microsoft Remote Desktop][rdp-mac].
+This article assumes that you have an existing AKS cluster with a Windows Server node. If you need an AKS cluster, see the article on [creating an AKS cluster with a Windows container using the Azure CLI][aks-windows-cli]. You need the Windows administrator username and password for the Windows Server node you want to troubleshoot. You also need an RDP client such as [Microsoft Remote Desktop][rdp-mac].
+
+If you need to reset the password you can use `az aks update` to change the password.
+
+```azurecli-interactive
+az aks update -g myResourceGroup -n myAKSCluster --windows-admin-password $WINDOWS_ADMIN_PASSWORD
+```
+
+If you need to reset both the username and password, see [Reset Remote Desktop Services or its administrator password in a Windows VM
+](/troubleshoot/azure/virtual-machines/reset-rdp).
 
 You also need the Azure CLI version 2.0.61 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
 

articles/aks/rdp.md

@@ -149,7 +149,7 @@ Here's JavaScript code:
 
 ```javascript
 module.exports = function (context, input) {
-    context.bindings.myQueueItem = input.body;
+    context.bindings.outputMessage = input.body;
     context.done();
 };
 ```

articles/azure-functions/functions-bindings-rabbitmq-output.md

@@ -2,7 +2,7 @@
 title: Bicep functions - scopes
 description: Describes the functions to use in a Bicep file to retrieve values about deployment scopes.
 ms.topic: conceptual
-ms.date: 10/18/2021
+ms.date: 11/23/2021
 ---
 
 # Scope functions for Bicep
@@ -13,14 +13,12 @@ This article describes the Bicep functions for getting scope values.
 
 `managementGroup()`
 
+Returns an object with properties from the management group in the current deployment.
+
 `managementGroup(identifier)`
 
 Returns an object used for setting the scope to a management group.
 
-Or
-
-Returns an object with properties from the management group in the current deployment.
-
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
 ### Remarks
@@ -46,7 +44,7 @@ The following example sets the scope for a module to a management group.
 ```bicep
 param managementGroupIdentifier string
 
-module  'module.bicep' = {
+module  'mgModule.bicep' = {
   name: 'deployToMG'
   scope: managementGroup(managementGroupIdentifier)
 }
@@ -115,15 +113,15 @@ output newManagementGroup string = mgName
 
 `resourceGroup()`
 
-`resourceGroup(resourceGroupName)`
+Returns an object that represents the current resource group.
 
-`resourceGroup(subscriptionId, resourceGroupName)`
+`resourceGroup(resourceGroupName)`
 
-Returns an object used for setting the scope to a resource group.
+And
 
-Or
+`resourceGroup(subscriptionId, resourceGroupName)`
 
-Returns an object that represents the current resource group.
+Return an object used for setting the scope to a resource group.
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
@@ -172,7 +170,7 @@ The following example scopes a module to a resource group.
 ```bicep
 param resourceGroupName string
 
-module exampleModule 'module.bicep' = {
+module exampleModule 'rgModule.bicep' = {
   name: 'exampleModule'
   scope: resourceGroup(resourceGroupName)
 }
@@ -210,14 +208,12 @@ You can also use the resourceGroup function to apply tags from the resource grou
 
 `subscription()`
 
+Returns details about the subscription for the current deployment.
+
 `subscription(subscriptionId)`
 
 Returns an object used for setting the scope to a subscription.
 
-Or
-
-Returns details about the subscription for the current deployment.
-
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
 ### Remarks
@@ -254,7 +250,7 @@ When used for getting details about the subscription, the function returns the f
 The following example scopes a module to the subscription.
 
 ```bicep
-module exampleModule 'module.bicep' = {
+module exampleModule 'subModule.bicep' = {
   name: 'deployToSub'
   scope: subscription()
 }
@@ -291,7 +287,7 @@ An object used for setting the `scope` property on a [module](modules.md#set-mod
 The following example shows a module deployed to the tenant.
 
 ```bicep
-module exampleModule 'module.bicep' = {
+module exampleModule 'tenantModule.bicep' = {
   name: 'deployToTenant'
   scope: tenant()
 }

articles/azure-resource-manager/bicep/bicep-functions-scope.md

@@ -1,5 +1,5 @@
 ---
-title: How to configure RHEL/CentOS 7 - Speech service
+title: How to configure RHEL/CentOS for C++ - Speech service
 titleSuffix: Azure Cognitive Services
 description: Learn how to configure RHEL/CentOS 7 so that the Speech SDK can be used.
 services: cognitive-services
@@ -12,11 +12,11 @@ ms.date: 04/02/2020
 ms.author: pankopon
 ---
 
-# Configure RHEL/CentOS 7 for Speech SDK
+# Configure RHEL/CentOS for C++
 
 To use the Speech SDK for C++ development on Red Hat Enterprise Linux (RHEL) 8 x64 and CentOS 8 x64, update the C++ compiler and the shared C++ runtime library on your system.
 
-### 1. General setup
+## Install dependencies
 
 First install all general dependencies:
 
@@ -30,7 +30,7 @@ sudo yum install -y alsa-lib dotnet-sdk-2.1 java-1.8.0-openjdk-devel openssl
 sudo yum install -y gstreamer1 gstreamer1-plugins-base gstreamer1-plugins-good gstreamer1-plugins-bad-free gstreamer1-plugins-ugly-free
 ```
 
-### 2. C/C++ compiler and runtime libraries
+## C/C++ compiler and runtime libraries
 
 Install the prerequisite packages with this command:
 
@@ -52,7 +52,7 @@ sudo make install-strip
 
 If the updated compiler and libraries need to be deployed on several machines, you can simply copy them from under `/usr/local` to other machines. If only the runtime libraries are needed then the files in `/usr/local/lib64` will be enough.
 
-### 3. Environment settings
+## Environment settings
 
 Run the following commands to complete the configuration:
 
@@ -69,7 +69,6 @@ export LD_LIBRARY_PATH=/usr/local/lib64:$LD_LIBRARY_PATH
 export PATH=/usr/local/bin:$PATH
 hash -r # reset cached paths in the current shell session just in case
 export LD_LIBRARY_PATH=/path/to/extracted/SpeechSDK-Linux-<version>/lib/x64:$LD_LIBRARY_PATH
-
 ```
 
 ## Next steps