Merge pull request #73150 from MicrosoftDocs/master

4/15 AM Publish

articles/active-directory/authentication/howto-sspr-reporting.md

@@ -47,15 +47,14 @@ In the Azure portal experience, we have improved the way that you can view passw
 1. Browse to the [Azure portal](https://portal.azure.com).
 2. Select **All services** in the left pane.
 3. Search for **Azure Active Directory** in the list of services and select it.
-4. Select **Users and groups**.
-5. Select **Audit Logs** from the **Users and groups** menu. This shows you all of the audit events that occurred against all the users in your directory. You can filter this view to see all the password-related events.
-6. To filter this view to see only the password-reset-related events, select the **Filter** button at the top of the pane.
-7. From the **Filter** menu, select the **Category** drop-down list, and change it to the **Self-service Password Management** category type.
-8. Optionally, further filter the list by choosing the specific **Activity** you're interested in.
+4. Select **Users** from the Manage section.
+5. Select **Audit Logs** from the **Users** blade. This shows you all of the audit events that occurred against all the users in your directory. You can filter this view to see all the password-related events.
+6. From the **Filter** menu at the top of the pane, select the **Service** drop-down list, and change it to the **Self-service Password Management** service type.
+7. Optionally, further filter the list by choosing the specific **Activity** you're interested in.
 
 ### Converged registration (preview)
 
-If you are participating in the public preview of converged registration, information regarding user activity in the audit logs will be found under the category **Authentication Methods**.
+If you are participating in the public preview of converged registration, information regarding user activity in the audit logs will be found under the service **Authentication Methods**.
 
 ## Description of the report columns in the Azure portal
 

articles/active-directory/develop/quickstart-v2-aspnet-core-webapp.md

@@ -52,9 +52,9 @@ In this quickstart, you'll learn how an ASP.NET Core web app can sign in persona
 > 1. Select **New registration**.
 > 1. When the **Register an application** page appears, enter your application's registration information:
 >    - In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `AspNetCore-Quickstart`.
->    - In **Reply URL**, add `https://localhost:44321/`, and select **Register**.
+>    - In **Redirect URI**, add `https://localhost:44321/`, and select **Register**.
 > 1. Select the **Authentication** menu, and then add the following information:
->    - In **Reply URL**, add `https://localhost:44321/signin-oidc`,  and select **Register**.
+>    - In **Redirect URIs**, add `https://localhost:44321/signin-oidc`,  and select **Save**.
 >    - In the **Advanced settings** section, set **Logout URL** to `https://localhost:44321/signout-oidc`.
 >    - Under **Implicit grant**, check **ID tokens**.
 >    - Select **Save**.
@@ -145,7 +145,7 @@ The line containing `.AddAzureAd` adds the Microsoft identity platform authentic
 
 
 > [!NOTE]
-> Setting `ValidateIssuer = false` is a simplification for this quickstart. In real applications you need to validate the issuer
+> Setting `ValidateIssuer = false` is a simplification for this quickstart. In real applications you need to validate the issuer.
 > See the samples to understand how to do that.
 
 ### Protect a controller or a controller's method

articles/active-directory/develop/quickstart-v2-aspnet-webapp.md

@@ -51,7 +51,7 @@ In this quickstart, you'll learn how an ASP.NET web app can sign in personal acc
 > 1. Select **New registration**.
 > 1. When the **Register an application** page appears, enter your application's registration information:
 >      - In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `ASPNET-Quickstart`.
->      - Add `https://localhost:44368/` in **Reply URL**, and click **Register**.
+>      - Add `https://localhost:44368/` in **Redirect URI**, and click **Register**.
 Select **Authentication** menu, set **ID tokens** under **Implicit Grant**, and then select **Save**.
 
 > [!div class="sxs-lookup" renderon="portal"]
@@ -155,7 +155,7 @@ public void Configuration(IAppBuilder app)
 
 
 > [!NOTE]
-> Setting `ValidateIssuer = false` is a simplification for this quickstart. In real applications you need to validate the issuer
+> Setting `ValidateIssuer = false` is a simplification for this quickstart. In real applications you need to validate the issuer.
 > See the samples to understand how to do that.
 
 ### Initiate an authentication challenge

articles/active-directory/hybrid/whatis-aadc-admin-agent.md

@@ -37,16 +37,18 @@ The Microsoft Support Engineer cannot change any data in your system and cannot
 
 If you do not want the Microsoft service engineer to access your data for a support call you can disable  this by modifying the service config file as described below: 
 
-  1.	Open **C:\Program Files\Microsoft Azure AD Connect Administration Agent\AzureADConnectAdministrationAgentService.exe.config** in notepad.
-  2.	Disable **UserDataEnabled** setting as shown below. If **UserDataEnabled** setting exists and is set to true, then set it to false. If the setting does not exist, then add the setting as shown below.    
-  `
- <appSettings>
-   <add key="TraceFilename" value="ADAdministrationAgent.log" />
-   <add key="UserDataEnabled" value="false" />
-  </appSettings>
-  `
-  3.	Save the config file.
-  4.	Restart Azure AD Connect Administration Agent service as shown below
+1.	Open **C:\Program Files\Microsoft Azure AD Connect Administration Agent\AzureADConnectAdministrationAgentService.exe.config** in notepad.
+2.	Disable **UserDataEnabled** setting as shown below. If **UserDataEnabled** setting exists and is set to true, then set it to false. If the setting does not exist, then add the setting as shown below.    
+
+    ```xml
+    <appSettings>
+      <add key="TraceFilename" value="ADAdministrationAgent.log" />
+      <add key="UserDataEnabled" value="false" />
+    </appSettings>
+    ```
+
+3.	Save the config file.
+4.	Restart Azure AD Connect Administration Agent service as shown below
 
 ![admin agent](media/whatis-aadc-admin-agent/adminagent2.png)
 

articles/active-directory/manage-apps/application-proxy-release-version-history.md

@@ -26,7 +26,7 @@ Here is a list of related resources:
 Resource |  Details
 --------- | --------- |
 How to enable Application Proxy | Pre-requisites for enabling Application Proxy and installing and registering a connector are described in this [tutorial](application-proxy-add-on-premises-application.md).
-Understand Azure AD Application Proxy connectors | Find out more about [connector management](application-proxy-connectors.md) and how connectors auto-upgrade.
+Understand Azure AD Application Proxy connectors | Find out more about [connector management](application-proxy-connectors.md) and how connectors [auto-upgrade](application-proxy-connectors.md#automatic-updates).
 Azure AD Application Proxy Connector Download |  [Download the latest connector](https://download.msappproxy.net/subscription/d3c8b69d-6bf7-42be-a529-3fe9c2e70c90/connector/download).
 
 ## 1.5.612.0
@@ -85,4 +85,4 @@ If you're using an Application Proxy connector version earlier than 1.5.36.0, up
 
 ## Next steps
 - Learn more about [Remote access to on-premises applications through Azure AD Application Proxy](application-proxy.md).
-- To start using Application Proxy, see [Tutorial: Add an on-premises application for remote access through Application Proxy](application-proxy-add-on-premises-application.md).
+- To start using Application Proxy, see [Tutorial: Add an on-premises application for remote access through Application Proxy](application-proxy-add-on-premises-application.md).