Merge branch 'main' of github.com:MicrosoftDocs/azure-docs-pr into remove-opt-in

Author: Blackmist

.openpublishing.publish.config.json

@@ -413,7 +413,7 @@
     {
       "path_to_root": "azureml-examples-vj",
       "url": "https://github.com/azure/azureml-examples",
-      "branch": "vijetajo-patch-2",
+      "branch": "main",
       "branch_mapping": {}
     },
     {

.openpublishing.redirection.active-directory.json

@@ -4575,6 +4575,11 @@
       "redirect_url": "/azure/active-directory/reports-monitoring/howto-access-activity-logs",
       "redirect_document_id": true
     },
+    {
+      "source_path_from_root": "/articles/active-directory/reports-monitoring/overview-sign-in-diagnostics.md",
+      "redirect_url": "/azure/active-directory/reports-monitoring/howto-use-sign-in-diagnostics",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/active-directory/reports-monitoring/troubleshoot-missing-data-download.md",
       "redirect_url": "/azure/active-directory/reports-monitoring/reports-faq",

.openpublishing.redirection.json

@@ -22203,6 +22203,16 @@
             "redirect_url": "/azure/active-directory/develop/zero-trust-for-developers",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/active-directory/develop/active-directory-v2-protocols.md",
+            "redirect_url": "/azure/active-directory/develop/v2-protocols",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/active-directory/develop/msal-net-aad-b2c-considerations.md",
+            "redirect_url": "/azure/active-directory/develop/msal-net-b2c-considerations",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/active-directory/develop/active-directory-how-applications-are-added.md",
             "redirect_url": "/azure/active-directory/develop/how-applications-are-added",

.openpublishing.redirection.virtual-desktop.json

@@ -189,6 +189,11 @@
             "source_path_from_root": "/articles/virtual-desktop/fslogix-office-app-rule-editor.md",
             "redirect_url": "/azure/virtual-desktop/install-office-on-wvd-master-image",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/virtual-desktop/app-attach-glossary.md",
+            "redirect_url": "/azure/virtual-desktop/what-is-app-attach",
+            "redirect_document_id": false
         }
     ]
 }

articles/active-directory-domain-services/join-rhel-linux-vm.md

@@ -311,21 +311,21 @@ To verify that the VM has been successfully joined to the managed domain, start
 1. Create a new SSH connection from your console. Use a domain account that belongs to the managed domain using the `ssh -l` command, such as `[email protected]` and then enter the address of your VM, such as *rhel.aaddscontoso.com*. If you use the Azure Cloud Shell, use the public IP address of the VM rather than the internal DNS name.
 
     ```bash
-    sudo ssh -l [email protected] rhel.aaddscontoso.com
+    ssh -l [email protected] rhel.aaddscontoso.com
     ```
 
 1. When you've successfully connected to the VM, verify that the home directory was initialized correctly:
 
     ```bash
-    sudo pwd
+    pwd
     ```
 
     You should be in the */home* directory with your own directory that matches the user account.
 
 1. Now check that the group memberships are being resolved correctly:
 
     ```bash
-    sudo id
+    id
     ```
 
     You should see your group memberships from the managed domain.

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

@@ -106,7 +106,7 @@ For a full list of endpoints needed to use Microsoft online products, see [Offic
 To check if the Windows 10 client device has the right domain join type, use the following command:
 
 ```console
-Dsregcmd/status
+Dsregcmd /status
 ```
 
 The following sample output shows that the device is Azure AD joined as *AzureADJoined* is set to *YES*:

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

@@ -87,14 +87,17 @@ Users can register for passwordless phone sign-in directly within the Microsoft
 6. Once signed-in, continue following the additional steps to set up phone sign-in. 
 
 ### Guided registration with My Sign-ins 
+> [!NOTE]
+> Users will only be able to register Microsoft Authenticator via combined registration if the Microsoft Authenticator authentication mode is to  Any or Push. 
+
 To register the Microsoft Authenticator app, follow these steps:
 
 1. Browse to [https://aka.ms/mysecurityinfo](https://aka.ms/mysecurityinfo).
 1. Sign in, then select **Add method** > **Authenticator app** > **Add** to add Microsoft Authenticator.
 1. Follow the instructions to install and configure the Microsoft Authenticator app on your device.
 1. Select **Done** to complete Microsoft Authenticator configuration.
 
-### Enable phone sign-in
+#### Enable phone sign-in
 
 After users registered themselves for the Microsoft Authenticator app, they need to enable phone sign-in: 
 

articles/active-directory/authentication/media/how-to-mfa-server-migration-utility/settings.png

@@ -126,7 +126,7 @@
     - name: Add app roles in your application
       href: ../develop/howto-add-app-roles-in-azure-ad-apps.md?toc=/azure/active-directory/azuread-dev/toc.json&bc=/azure/active-directory/azuread-dev/breadcrumb/toc.json
     - name: Branding guidelines
-      href: ../develop/howto-add-branding-in-azure-ad-apps.md?toc=/azure/active-directory/azuread-dev/toc.json&bc=/azure/active-directory/azuread-dev/breadcrumb/toc.json
+      href: /azure/active-directory/develop/howto-add-branding-in-apps
     - name: Terms of Service and Privacy Statement
       href: ../develop/howto-add-terms-of-service-privacy-statement.md?toc=/azure/active-directory/azuread-dev/toc.json&bc=/azure/active-directory/azuread-dev/breadcrumb/toc.json
   - name: Bring an app to market

articles/active-directory/azuread-dev/TOC.yml

@@ -27,16 +27,13 @@
         href: onboard-enable-controller-after-onboarding.md
       - name: Add an account/ subscription/ project after onboarding is complete
         href: onboard-add-account-after-onboarding.md
-    - name: View risk metrics in your authorization system
+    - name: View information about your Authorization Systems
       expanded: false
       items:
       - name: View key statistics and data about your authorization system
         href: ui-dashboard.md
       - name: View data about the activity in your authorization system
         href: product-dashboard.md  
-    - name: View information about your Authorization Systems
-      expanded: false
-      items:
       - name: View and configure settings for data collection
         href: product-data-sources.md
       - name: View current billable resources in your authorization system