Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into subnet-prefixes

Author: asudbring

.openpublishing.redirection.json

@@ -4000,11 +4000,6 @@
             "redirect_url":"/azure/reliability/reliability-containers",
             "redirect_document_id":false 
         },
-		{
-			"source_path_from_root":"/articles/service-connector/quickstart-cli-aks-connection.md",
-			"redirect_url":"/azure/service-connector/quickstart-portal-aks-connection",
-			"redirect_document_id":false
-		},
         {
             "source_path_from_root":"/articles/aks/generation-2-vm-windows.md",
             "redirect_url":"/azure/aks/generation-2-vm",

.openpublishing.redirection.virtual-desktop.json

@@ -409,6 +409,16 @@
             "source_path_from_root": "/articles/virtual-desktop/autoscale-scaling-plan.md",
             "redirect_url": "/azure/virtual-desktop/autoscale-create-assign-scaling-plan",
             "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/getting-started-feature.md",
+            "redirect_url": "/azure/virtual-desktop/quickstart",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/troubleshoot-getting-started.md",
+            "redirect_url": "/azure/virtual-desktop/troubleshoot-quickstart",
+            "redirect_document_id": true
         }
     ]
 }

articles/active-directory-b2c/configure-authentication-sample-web-app.md

@@ -78,7 +78,7 @@ To create the web app registration, use the following steps:
 1. Under **Name**, enter a name for the application (for example, *webapp1*).
 1. Under **Supported account types**, select **Accounts in any identity provider or organizational directory (for authenticating users with user flows)**. 
 1. Under **Redirect URI**, select **Web** and then, in the URL box, enter `https://localhost:44316/signin-oidc`.
-1. Under  **Authentication**, go to **Implicit grant and hybrid flows**, select the **ID tokens (used for implicit and hybrid flows)** checkbox.
+1. Under **Manage**, select the **Authentication**, go to **Implicit grant and hybrid flows**, select the **ID tokens (used for implicit and hybrid flows)** checkbox.
 1. Under **Permissions**, select the **Grant admin consent to openid and offline access permissions** checkbox.
 1. Select **Register**.
 1. Select **Overview**.

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

@@ -185,7 +185,7 @@ To create a CNAME record for your custom domain:
     1.  Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name Server Management**.
 
     1. Create a new TXT DNS record and complete the fields as shown below:
-        1. Name: `_dnsauth.contoso.com`, but you need to enter just `_dnsauth`.
+        1. Name: `_dnsauth.login.contoso.com`, but you need to enter just `_dnsauth`.
         1. Type: `TXT`
         1. Value: Something like `75abc123t48y2qrtsz2bvk......`.
 

articles/active-directory-b2c/custom-policies-series-store-user.md

@@ -10,7 +10,7 @@ ms.service: active-directory
 
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 01/11/2024
+ms.date: 05/11/2024
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: B2C
@@ -206,7 +206,7 @@ We use the `ClaimGenerator` technical profile to execute three claims transforma
                         </Precondition>
                     </Preconditions>
                 </ValidationTechnicalProfile>                        
-                <ValidationTechnicalProfile ReferenceId="DisplayNameClaimGenerator"/>
+                <ValidationTechnicalProfile ReferenceId="UserInputDisplayNameGenerator"/>
                 <ValidationTechnicalProfile ReferenceId="AAD-UserWrite"/>
             </ValidationTechnicalProfiles>
         <!--</TechnicalProfile>-->
@@ -407,15 +407,14 @@ To configure a display control, use the following steps:
 
 1. Use the procedure in [step 6](#step-6---upload-policy) and [step 7](#step-7---test-policy) to upload your policy file, and test it. This time, you must verify your email address before a user account is created.  
 
-<a name='update-user-account-by-using-azure-ad-technical-profile'></a>
 
 ## Update user account by using Microsoft Entra ID technical profile
 
-You can configure a Microsoft Entra ID technical profile to update a user account instead of attempting to create a new one. To do so, set the Microsoft Entra ID technical profile to throw an error if the specified user account doesn't already exist in the `Metadata` collection by using the following code. The *Operation* needs to be set to *Write*:
+You can configure a Microsoft Entra ID technical profile to update a user account instead of attempting to create a new one. To do so, set the Microsoft Entra ID technical profile to throw an error if the specified user account doesn't already exist in the metadata collection by using the following code. Also, remove the `Key="UserMessageIfClaimsPrincipalAlreadyExists` metadata entry. The *Operation* needs to be set to *Write*:
 
 ```xml
     <Item Key="Operation">Write</Item>
-    <Item Key="RaiseErrorIfClaimsPrincipalDoesNotExist">true</Item>
+    <Item Key="RaiseErrorIfClaimsPrincipalDoesNotExist">false</Item>
 ``` 
 
 ## Use custom attributes