Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into release-ignite-sentinel-honeytokens-solution

Author: batamig

.openpublishing.redirection.json

@@ -403,6 +403,11 @@
       "redirect_url": "/articles/load-balancer/concepts",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/frontdoor/standard-premium/resource-manager-template-samples.md",
+      "redirect_url": "/articles/frontdoor/front-door-quickstart-template-samples",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/azure-sql/database/doc-changes-updates-release-notes.md",
       "redirect_url": "/azure/azure-sql/database/doc-changes-updates-release-notes-whats-new",

articles/active-directory/app-provisioning/on-premises-ecma-troubleshoot.md

@@ -1,25 +1,25 @@
 ---
-title: 'Troubleshooting issues with the ECMA Connector Host and Azure AD'
+title: 'Troubleshooting issues with provisioning to on-premises applications'
 description: Describes how to troubleshoot various issues you might encounter when you install and use the ECMA Connector Host.
 services: active-directory
 author: billmath
 manager: karenh444
 ms.service: active-directory
 ms.workload: identity
 ms.topic: overview
-ms.date: 08/24/2021
+ms.date: 10/21/2021
 ms.subservice: hybrid
 ms.author: billmath
 ms.collection: M365-identity-device-management
 ---
 
-# Troubleshoot ECMA Connector Host issues
+# Troubleshoot on-premises application provisioning
 
 >[!IMPORTANT]
 > The on-premises provisioning preview is currently in an invitation-only preview. To request access to the capability, use the [access request form](https://aka.ms/onpremprovisioningpublicpreviewaccess). We'll open the preview to more customers and connectors over the next few months as we prepare for general availability.
 
 ## Troubleshoot test connection issues
-After you configure the ECMA host and provisioning agent, it's time to test connectivity from the Azure Active Directory (Azure AD) provisioning service to the provisioning agent, the ECMA host, and the application. To perform this end-to-end test, select **Test connection** in the application in the Azure portal. When the test connection fails, try the following troubleshooting steps:
+After you configure the provisioning agent and ECMA host, it's time to test connectivity from the Azure Active Directory (Azure AD) provisioning service to the provisioning agent, the ECMA host, and the application. To perform this end-to-end test, select **Test connection** in the application in the Azure portal. When the test connection fails, try the following troubleshooting steps:
 
  1. Check that the agent and ECMA host are running:
      1. On the server with the agent installed, open **Services** by going to **Start** > **Run** > **Services.msc**.

articles/active-directory/app-provisioning/on-premises-sql-connector-configure.md

@@ -1,6 +1,6 @@
 ---
-title: Azure AD ECMA Connector Host generic SQL connector configuration
-description: This document describes how to configure the Azure AD ECMA Connector Host generic SQL connector.
+title: Provisioning users into SQL based applications using the ECMA Connector host
+description: Provisioning users into SQL based applications using the ECMA Connector host
 services: active-directory
 author: billmath
 manager: karenh444
@@ -13,7 +13,7 @@ ms.author: billmath
 ms.reviewer: arvinh
 ---
 
-# Azure AD ECMA Connector Host generic SQL connector configuration
+# Provisioning users into SQL based applications
 The following documentation provides configuration and tutorial information demonstrating how the generic SQL connector and the ECMA Connector Host can be used with a SQL Server.
 
 

articles/active-directory/app-provisioning/toc.yml

@@ -18,7 +18,7 @@
       href: customize-application-attributes.md
     - name: App specific provisioning tutorials
       href: /azure/active-directory/saas-apps
-    - name: Azure AD ECMA Connector Host Generic SQL Connector
+    - name: Provisioning to SQL based apps
       href: tutorial-ecma-sql-connector.md
   - name: Concepts
     expanded: true
@@ -74,13 +74,13 @@
         href: application-provisioning-config-problem-no-users-provisioned.md
       - name: Missing source attribute
         href: user-provisioning-sync-attributes-for-mapping.md
-      - name: Troubleshooting ECMA Connector Host
+      - name: Troubleshooting on-premises provisioning
         href: on-premises-ecma-troubleshoot.md
       - name: Provisioning logs
         href: ../reports-monitoring/concept-provisioning-logs.md?context=%2fazure%2factive-directory%2fapp-provisioning%2fcontext%2fapp-provisioning-context
     - name: On-premises app provisioning
       items:
-      - name: Generic SQL connector configuration
+      - name: Provisioning to SQL based apps
         href: on-premises-sql-connector-configure.md
       - name: Generic LDAP Connector configuration
         href: on-premises-ldap-connector-configure.md

articles/active-directory/app-provisioning/tutorial-ecma-sql-connector.md

@@ -1,13 +1,13 @@
 ---
-title:  Azure AD ECMA Connector Host generic SQL connector tutorial
-description: This tutorial describes how to use the on-premises application provisioning generic SQL connector.
+title:  Azure AD Provisioning to SQL applications
+description: This tutorial describes how to provision users from Azure AD into a SQL database.
 services: active-directory
 author: billmath
 manager: karenh444
 ms.service: active-directory
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 07/13/2021
+ms.date: 10/21/2021
 ms.subservice: hybrid
 ms.author: billmath
 ms.reviewer: arvinh
@@ -16,7 +16,7 @@ ms.collection: M365-identity-device-management
 
 
 
-# Azure AD ECMA Connector Host generic SQL connector tutorial
+# Configuring Azure AD to provision users into a SQL database
 
 [!INCLUDE [active-directory-app-provisioning-sql.md](../../../includes/active-directory-app-provisioning-sql.md)]
 

articles/active-directory/authentication/concept-authentication-authenticator-app.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 02/22/2021
+ms.date: 10/29/2021
 
 ms.author: justinha
 author: justinha
@@ -29,9 +29,9 @@ To use the Authenticator app at a sign-in prompt rather than a username and pass
 
 ## Passwordless sign-in
 
-Instead of seeing a prompt for a password after entering a username, a user that has enabled phone sign-in from the Microsoft Authenticator app sees a message to tap a number in their app. When the correct number is selected, the sign-in process is complete.
+Instead of seeing a prompt for a password after entering a username, a user that has enabled phone sign-in from the Microsoft Authenticator app sees a message to enter a number in their app. When the correct number is selected, the sign-in process is complete.
 
-![Example of a browser sign-in asking for user to approve the sign-in](./media/howto-authentication-passwordless-phone/phone-sign-in-microsoft-authenticator-app.png)
+![Example of a browser sign-in asking for user to approve the sign-in.](./media/howto-authentication-passwordless-phone/phone-sign-in-microsoft-authenticator-app.png)
 
 This authentication method provides a high level of security, and removes the need for the user to provide a password at sign-in. 
 
@@ -41,7 +41,7 @@ To get started with passwordless sign-in, see [Enable passwordless sign-in with
 
 The Authenticator app can help prevent unauthorized access to accounts and stop fraudulent transactions by pushing a notification to your smartphone or tablet. Users view the notification, and if it's legitimate, select **Verify**. Otherwise, they can select **Deny**.
 
-![Screenshot of example web browser prompt for Authenticator app notification to complete sign-in process](media/tutorial-enable-azure-mfa/azure-multi-factor-authentication-browser-prompt.png)
+![Screenshot of example web browser prompt for Authenticator app notification to complete sign-in process.](media/tutorial-enable-azure-mfa/azure-multi-factor-authentication-browser-prompt.png)
 
 > [!NOTE]
 > If your organization has staff working in or traveling to China, the *Notification through mobile app* method on Android devices doesn't work in that country/region as Google play services(including push notifications) are blocked in the region. However iOS notification do work. For Android devices ,alternate authentication methods should be made available for those users.

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

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: how-to
-ms.date: 10/21/2021
+ms.date: 10/29/2021
 
 ms.author: justinha
 author: justinha
@@ -25,15 +25,15 @@ This authentication technology can be used on any device platform, including mob
 
 People who enabled phone sign-in from the Microsoft Authenticator app see a message that asks them to tap a number in their app. No username or password is asked for. To complete the sign-in process in the app, a user must next take the following actions:
 
-1. Match the number.
-2. Choose **Approve**.
-3. Provide their PIN or biometric.
+1. Type the number they see on the login screen into the Microsoft Authenticator app dialog.
+1. Choose **Approve**.
+1. Provide their PIN or biometric.
 
 ## Prerequisites
 
 To use passwordless phone sign-in with the Microsoft Authenticator app, the following prerequisites must be met:
 
-- Azure AD Multi-Factor Authentication, with push notifications allowed as a verification method. Push notifications to your smartphone or tablet help the Authenticator app to prevent unauthorized access to accounts and stop fraudulent transactions. The Authenticator app automatically generates codes when set up to do push notifications so a user has a backup sign-in method even if their device doesn't have connectivity. 
+- Recommended: Azure AD Multi-Factor Authentication, with push notifications allowed as a verification method. Push notifications to your smartphone or tablet help the Authenticator app to prevent unauthorized access to accounts and stop fraudulent transactions. The Authenticator app automatically generates codes when set up to do push notifications so a user has a backup sign-in method even if their device doesn't have connectivity. 
 - Latest version of Microsoft Authenticator installed on devices running iOS 8.0 or greater, or Android 6.0 or greater.
 - The device on which the Microsoft Authenticator app is installed must be registered within the Azure AD tenant to an individual user. 
 
@@ -65,7 +65,7 @@ To enable the authentication method for passwordless phone sign-in, complete the
 Users register themselves for the passwordless authentication method of Azure AD by using the following steps:
 
 1. Browse to [https://aka.ms/mysecurityinfo](https://aka.ms/mysecurityinfo).
-1. Sign in, then add the Authenticator app by selecting **Add method > Authenticator app**, then **Add**.
+1. Sign in, then click **Add method** > **Authenticator app** > **Add** to add the Authenticator app.
 1. Follow the instructions to install and configure the Microsoft Authenticator app on your device.
 1. Select **Done** to complete Authenticator configuration.
 1. In **Microsoft Authenticator**, choose **Enable phone sign-in** from the drop-down menu for the account registered.
@@ -90,7 +90,7 @@ The first time a user starts the phone sign-in process, the user performs the fo
 3. If necessary, selects **Other ways to sign in**.
 4. Selects **Approve a request on my Microsoft Authenticator app**.
 
-The user is then presented with a number. The app prompts the user to authenticate by selecting the appropriate number, instead of by entering a password.
+The user is then presented with a number. The app prompts the user to authenticate by typing the appropriate number, instead of by entering a password.
 
 After the user has utilized passwordless phone sign-in, the app continues to guide the user through this method. However, the user will see the option to choose another method.
 
@@ -119,7 +119,7 @@ This logic generally prevents a user in a hybrid tenant from being directed to A
 
 ### Azure MFA server
 
-An end user can be enabled for multi-factor authentication (MFA), through an on-premises Azure MFA server. The user can still create and utilize a single passwordless phone sign-in credential.
+An end user can be enabled for multifactor authentication (MFA) through an on-premises Azure MFA server. The user can still create and utilize a single passwordless phone sign-in credential.
 
 If the user attempts to upgrade multiple installations (5+) of the Microsoft Authenticator app with the passwordless phone sign-in credential, this change might result in an error.
 
@@ -138,4 +138,4 @@ To learn about Azure AD authentication and passwordless methods, see the followi
 
 - [Learn how passwordless authentication works](concept-authentication-passwordless.md)
 - [Learn about device registration](../devices/overview.md)
-- [Learn about Azure AD Multi-Factor Authentication](../authentication/howto-mfa-getstarted.md)
+- [Learn about Azure AD Multi-Factor Authentication](../authentication/howto-mfa-getstarted.md)

articles/active-directory/authentication/media/howto-authentication-passwordless-phone/phone-sign-in-microsoft-authenticator-app.png

@@ -6,12 +6,12 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: conditional-access
 ms.topic: conceptual
-ms.date: 06/21/2021
+ms.date: 10/27/2021
 
 ms.author: joflore
 author: MicrosoftGuyJFlo
 manager: karenhoran
-ms.reviewer: calebb, olhuan
+ms.reviewer: calebb, mewal
 
 ms.collection: M365-identity-device-management
 
@@ -78,7 +78,7 @@ If you select **Determine location by IP address (IPv4 only)**, the system will
 > [!NOTE]
 > Sign-ins from IPv6 addresses cannot be mapped to countries or regions, and are considered unknown areas. Only IPv4 addresses can be mapped to countries or regions.
 
-If you select **Determine location by GPS coordinates (Preview)**, the user will need to have the Microsoft Authenticator app installed on their mobile device. Every hour, the system will contact the user’s Microsoft Authenticator app to collect the GPS location of the user’s mobile device.
+If you select **Determine location by GPS coordinates**, the user will need to have the Microsoft Authenticator app installed on their mobile device. Every hour, the system will contact the user’s Microsoft Authenticator app to collect the GPS location of the user’s mobile device.
 
 The first time the user is required to share their location from the Microsoft Authenticator app, the user will receive a notification in the app. The user will need to open the app and grant location permissions.