Merge pull request #211575 from MicrosoftDocs/main

9/16 AM Publish

Author: huypub

articles/active-directory/authentication/TOC.yml

@@ -164,9 +164,9 @@
       href: howto-password-ban-bad-on-premises-agent-versions.md
   - name: Run a registration campaign
     href: how-to-mfa-registration-campaign.md
-  - name: Use number matching (Preview)
+  - name: Use number matching 
     href: how-to-mfa-number-match.md
-  - name: Use additional context (Preview)
+  - name: Use additional context 
     href: how-to-mfa-additional-context.md
   - name: Use Microsoft managed settings 
     href: how-to-mfa-microsoft-managed.md

articles/active-directory/authentication/concept-certificate-based-authentication-smartcard.md

@@ -37,7 +37,7 @@ Users will get a primary refresh token (PRT) from Azure Active Directory after t
 ## Restrictions and caveats  
 
 - The Windows login only works with the latest preview build of Windows 11. We are working to backport the functionality to Windows 10 and Windows Server.
-- Only Windows machines that are joined to either or a hybrid environment can test SmartCard logon.  
+- Only Windows machines that are joined to either Azure AD or a hybrid environment can test SmartCard logon.  
 - Like in the other Azure AD CBA scenarios, the user must be on a managed domain or using staged rollout and cannot use a federated authentication model.
 
 ## Next steps

articles/active-directory/authentication/how-to-mfa-additional-context.md

@@ -71,7 +71,7 @@ const msal = require('@azure/msal-node');
 
 const pca = new msal.PublicClientApplication({
         auth: {
-            clientId = "YOUR_CLIENT_ID"
+            clientId: "YOUR_CLIENT_ID"
         }
     });
 ```
@@ -86,8 +86,8 @@ const msal = require('@azure/msal-node');
 
 const cca = new msal.ConfidentialClientApplication({
         auth: {
-            clientId = "YOUR_CLIENT_ID",
-            clientSecret = "YOUR_CLIENT_SECRET"
+            clientId: "YOUR_CLIENT_ID",
+            clientSecret: "YOUR_CLIENT_SECRET"
         }
     });
 ```

articles/active-directory/authentication/how-to-mfa-number-match.md

@@ -29,7 +29,7 @@ The sync service consists of two components, the on-premises **Azure AD Connect
 >
 >To find out if you are already eligible for Cloud Sync, please verify your requirements in [this wizard](https://admin.microsoft.com/adminportal/home?Q=setupguidance#/modernonboarding/identitywizard).
 >
->To learn more about Cloud Sync please read [this article](https://docs.microsoft.com/azure/active-directory/cloud-sync/what-is-cloud-sync).
+>To learn more about Cloud Sync please read [this article](https://docs.microsoft.com/azure/active-directory/cloud-sync/what-is-cloud-sync), or watch this [short video](https://www.microsoft.com/en-us/videoplayer/embed/RWJ8l5).
 >
 
 

articles/active-directory/authentication/media/how-to-mfa-additional-context/enable-app-name.png

@@ -15,7 +15,6 @@ With Azure CNI Overlay, the cluster nodes are deployed into an Azure Virtual Net
 
 > [!NOTE]
 > - Azure CNI Overlay is currently only available in US West Central region.
-> - Azure CNI Overlay does not currently support _v5 VM SKUs.
 
 ## Overview of overlay networking