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

Author: HeidiSteen

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

@@ -24,6 +24,14 @@ The Azure Active Directory Connect synchronization services (Azure AD Connect sy
 This topic is the home for **Azure AD Connect sync** (also called **sync engine**) and lists links to all other topics related to it. For links to Azure AD Connect, see [Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md).
 
 The sync service consists of two components, the on-premises **Azure AD Connect sync** component and the service side in Azure AD called **Azure AD Connect sync service**.
+>[!IMPORTANT]
+>Azure AD Connect Cloud Sync is a new offering from Microsoft designed to meet and accomplish your hybrid identity goals for synchronization of users, groups, and contacts to Azure AD. It accomplishes this by using the Azure AD Cloud provisioning agent instead of the Azure AD Connect application. Azure AD Cloud Sync is replacing Azure AD Connect sync, which will be retired after Cloud Sync has full functional parity with Connect sync. The remainder of this article is about AADConnect sync, but we encourage customers to review the features and advantages of Cloud Sync before deploying AADConnect sync. 
+>
+>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), or watch this [short video](https://www.microsoft.com/en-us/videoplayer/embed/RWJ8l5).
+>
+
 
 ## Azure AD Connect sync topics
 | Topic | What it covers and when to read |

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