Merge pull request #221898 from markwahl-msft/mwahl-ecma-ga2sql

ECMA host SQL provisioning: update with GA strings

Author: prmerger-automator[bot]

includes/active-directory-app-provisioning-sql.md

@@ -155,20 +155,20 @@ If you have already downloaded the provisioning agent and configured it for anot
 
  1. Open the provisioning agent installer, agree to the terms of service, and select **next**.
  1. Open the provisioning agent wizard.
- 1. In the **Select Extension** step, select **On-premises provisioning** and then select **Next**.
+ 1. In the **Select Extension** step, select **On-premises application provisioning** and then select **Next**.
 
     ![Screenshot that shows how to select on premises provisioning.](./media/active-directory-app-provisioning-sql/azure-ad-sync-agent-select-on-premises.png)
 
  1. The provisioning agent will use the operating system's web browser to display a popup window for you to authenticate to Azure AD, and potentially also your organization's identity provider.  If you are using Internet Explorer as the browser on Windows Server, then you may need to add Microsoft web sites to your browser's trusted site list to allow JavaScript to run correctly.
- 1. Provide credentials for an Azure AD administrator when you're prompted to authorize. The Hybrid Identity Administrator or Global Administrator role is required.
- 1. Select **Confirm** to confirm the installation was successful.
+ 1. Provide credentials for an Azure AD administrator when you're prompted to authorize. The user is required to have the Hybrid Identity Administrator or Global Administrator role.
+ 1. Select **Confirm** to confirm the setting. Once installation is successful, you can select **Exit**, and also close the Provisioning Agent Package installer.
 
 ## 4. Configure the On-premises ECMA app
 
 1. Sign in to the Azure portal.
-1. Go to **Enterprise applications** > **Add a new application**.
-1. Search for the **On-premises ECMA app** application, and add it to your tenant.
-1. From the menu, select **Provisioning**.
+1. Go to **Enterprise applications** and select **New application**.
+1. Search for the **On-premises ECMA app** application, give the app a name, and select **Create** to add it to your tenant.
+1. From the menu, navigate to the **Provisioning** page of your application.
 1. Select **Get started**.
 1. On the **Provisioning** page, change the mode to **Automatic**.
 
@@ -185,7 +185,7 @@ If you have already downloaded the provisioning agent and configured it for anot
 
  1. On the Windows Server where the provisioning agent is installed, right click the **Microsoft ECMA2Host Configuration Wizard** from the start menu, and run as administrator.  Running as a Windows administrator is necessary for the wizard to create the necessary Windows event logs.
 
- 1. After the ECMA Connector Host Configuration starts, if it's the first time you have run the wizard, it will ask you to create a certificate. Leave the default port **8585** and select **Generate** to generate a certificate. The autogenerated certificate will be self-signed as part of the trusted root. The certificate SAN matches the host name.
+ 1. After the ECMA Connector Host Configuration starts, if it's the first time you have run the wizard, it will ask you to create a certificate. Leave the default port **8585** and select **Generate certificate** to generate a certificate. The autogenerated certificate will be self-signed as part of the trusted root. The certificate SAN matches the host name.
 
      [![Screenshot that shows configuring your settings.](.\media\active-directory-app-provisioning-sql\configure-1.png)](.\media\active-directory-app-provisioning-sql\configure-1.png#lightbox)