Merge pull request #96930 from ShawnJackson/scenario-web-app-sign-user

edit pass: scenario-web-app-sign-user

Author: itechedit

articles/active-directory/develop/scenario-web-app-sign-user-app-configuration.md

@@ -15,114 +15,113 @@ ms.workload: identity
 ms.date: 10/30/2019
 ms.author: jmprieur
 ms.custom: aaddev
-#Customer intent: As an application developer, I want to know how to write a web app that signs-in users using the Microsoft identity platform for developers.
+#Customer intent: As an application developer, I want to know how to write a web app that signs in users by using the Microsoft identity platform for developers.
 ms.collection: M365-identity-device-management
 ---
 
-# Web app that signs in users - app registration
+# Web app that signs in users: App registration
 
-This page explains the app registration specifics for a web app that signs-in users.
+This article explains the app registration specifics for a web app that signs in users.
 
 To register your application, you can use:
 
-- The [web app quickstarts](#register-an-app-using-the-quickstarts) - In addition to being a great first experience with creating an application, quickstarts in the Azure portal contain a button named **Make this change for me**. You can use this button to set the properties you need, even for an existing app. You'll need to adapt the values of these properties to your own case. In particular, the web API URL for your app is probably going to be different from the proposed default, which will also impact the sign-out URI.
-- The Azure portal to [register your application manually](#register-an-app-using-azure-portal)
-- PowerShell and command-line tools
+- The [web app quickstarts](#register-an-app-by-using-the-quickstarts). In addition to being a great first experience with creating an application, quickstarts in the Azure portal contain a button named **Make this change for me**. You can use this button to set the properties you need, even for an existing app. You'll need to adapt the values of these properties to your own case. In particular, the web API URL for your app is probably going to be different from the proposed default, which will also affect the sign-out URI.
+- The Azure portal to [register your application manually](#register-an-app-by-using-the-azure-portal).
+- PowerShell and command-line tools.
 
-## Register an app using the QuickStarts
+## Register an app by using the quickstarts
 
-If you navigate to this link, you can create bootstrap the creation of your web application:
+You can use these links to bootstrap the creation of your web application:
 
 - [ASP.NET Core](https://aka.ms/aspnetcore2-1-aad-quickstart-v2)
 - [ASP.NET](https://ms.portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/applicationsListBlade/quickStartType/AspNetWebAppQuickstartPage/sourceType/docs)
 
-## Register an app using Azure portal
+## Register an app by using the Azure portal
 
 > [!NOTE]
-> the portal to use is different depending on if your application runs in the Microsoft Azure public cloud or in a national or sovereign cloud. For more information, see [National Clouds](./authentication-national-cloud.md#app-registration-endpoints)
+> The portal to use is different depending on whether your application runs in the Microsoft Azure public cloud or in a national or sovereign cloud. For more information, see [National clouds](./authentication-national-cloud.md#app-registration-endpoints).
 
 
-1. Sign in to the [Azure portal](https://portal.azure.com) using either a work or school account, or a personal Microsoft account. Alternatively, sign in to the national cloud Azure portal of choice.
-1. If your account gives you access to more than one tenant, select your account in the top-right corner, and set your portal session to the desired Azure AD tenant.
-1. In the left-hand navigation pane, select the **Azure Active Directory** service, and then select **App registrations** > **New registration**.
+1. Sign in to the [Azure portal](https://portal.azure.com) by using either a work or school account, or a personal Microsoft account. Alternatively, sign in to the Azure portal of choice for the national cloud.
+1. If your account gives you access to more than one tenant, select your account in the upper-right corner. Then, set your portal session to the desired Azure Active Directory (Azure AD) tenant.
+1. In the left pane, select the **Azure Active Directory** service, and then select **App registrations** > **New registration**.
 
 # [ASP.NET Core](#tab/aspnetcore)
 
-4. When the **Register an application** page appears, enter your application's registration information:
-   1. choose the supported account types for your application (See [Supported Account types](./v2-supported-account-types.md))
-   1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `AspNetCore-WebApp`.
-   1. In **Redirect URI**, add the type of application and the URI destination that will accept returned token responses after successfully authenticating. For example, `https://localhost:44321/`.  Select **Register**.
+1. When the **Register an application** page appears, enter your application's registration information:
+   1. Choose the supported account types for your application. (See [Supported account types](./v2-supported-account-types.md).)
+   1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app. For example, enter **AspNetCore-WebApp**.
+   1. For **Redirect URI**, add the type of application and the URI destination that will accept returned token responses after successful authentication. For example, enter **https://localhost:44321**. Then, select **Register**.
 1. Select the **Authentication** menu, and then add the following information:
-   1. In **Reply URL**, add `https://localhost:44321/signin-oidc` of type "Web".
-   1. In the **Advanced settings** section, set **Logout URL** to `https://localhost:44321/signout-oidc`.
-   1. Under **Implicit grant**, check **ID tokens**.
+   1. For **Reply URL**, add **https://localhost:44321/signin-oidc** of type **Web**.
+   1. In the **Advanced settings** section, set **Logout URL** to **https://localhost:44321/signout-oidc**.
+   1. Under **Implicit grant**, select **ID tokens**.
    1. Select **Save**.
 
 # [ASP.NET](#tab/aspnet)
 
-4. When the **Register an application page** appears, enter your application's registration information:
-   1. choose the supported account types for your application (See [Supported Account types](./v2-supported-account-types.md))
-   - In the **Name** section, enter a meaningful application name that will be displayed to users of the app, for example `MailApp-openidconnect-v2`.
-   - In the Redirect URI (optional) section, select **Web** in the combo-box and enter the following redirect URIs: `https://localhost:44326/`.
+1. When the **Register an application page** appears, enter your application's registration information:
+   1. Choose the supported account types for your application. (See [Supported account types](./v2-supported-account-types.md).)
+   1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app. For example, enter **MailApp-openidconnect-v2**.
+   1. In the **Redirect URI (optional)** section, select **Web** in the combo box and enter the following redirect URI: **https://localhost:44326/**.
 1. Select **Register** to create the application.
-1. Select the **Authentication** menu, and then add the following information:
-   - In the **Advanced settings** | **Implicit grant** section, check **ID tokens** as this sample requires
-     the [Implicit grant flow](v2-oauth2-implicit-grant-flow.md) to be enabled to sign in the user.
+1. Select the **Authentication** menu. 
+1. In the **Advanced settings** | **Implicit grant** section, select **ID tokens**. This sample requires the [implicit grant flow](v2-oauth2-implicit-grant-flow.md) to be enabled to sign in the user.
 1. Select **Save**.
 
 # [Java](#tab/java)
 
-4. When the **Register an application page** appears, enter a friendly name for the application, for example 'java-webapp', select "Accounts in any organizational directory
-and personal Microsoft Accounts (e.g. Skype, Xbox, Outlook.com)"
-   and select 'Web app / API' as the *Application Type*.
-1. Click **Register** to register the application.
-1. On the left-hand menu, click on **Authentication**, and under *Redirect URIs*, select "Web". You will need to enter
- two different redirect URIs: one for the signIn page, and one for the graph page. For both, you should use the same host and port number, then followed by "/msal4jsample/secure/aad" for the sign-in page and "msal4jsample/graph/me" for the user info page.
- By default, the sample uses:
+1. When the **Register an application page** appears, enter a display name for the application. For example, enter **java-webapp**. 
+1. Select **Accounts in any organizational directory
+and personal Microsoft Accounts (e.g. Skype, Xbox, Outlook.com)**,
+   and then select **Web app / API** for **Application Type**.
+1. Select **Register** to register the application.
+1. On the left menu, select **Authentication**. Under **Redirect URIs**, select **Web**. 
 
-    - `http://localhost:8080/msal4jsample/secure/aad`.
-    - `http://localhost:8080/msal4jsample/graph/me`
+1. Enter two redirect URIs: one for the sign-in page, and one for the graph page. For both, use the same host and port number, followed by **/msal4jsample/secure/aad** for the sign-in page and **msal4jsample/graph/me** for the user information page.
+ 
+   By default, the sample uses:
 
-    In the **Advanced settings** section, set **Logout URL** to `http://localhost:8080/msal4jsample/sign_out`.
+   - **http://localhost:8080/msal4jsample/secure/aad**
+   - **http://localhost:8080/msal4jsample/graph/me**
 
-     Click on **save**.
+1. In the **Advanced settings** section, set **Logout URL** to **http://localhost:8080/msal4jsample/sign_out**. Then, select **Save**.
 
-1. Select the **Certificates & secrets** from the menu and in the **Client secrets** section, click on **New client secret**:
+1. Select **Certificates & secrets** from the menu. 
+1. In the **Client secrets** section, select **New client secret**, and then:
 
-    - Type a key description
-    - Select a key duration **In 1 year**.
-    - The key value will display when you select **Add**.
-    - Copy the value of the key for later. This key value will not be displayed again, nor retrievable by any other means, so record it as soon as it is visible from the Azure portal.
+   1. Enter a key description.
+   1. Select the key duration **In 1 year**.
+   1. Select **Add**.
+   1. When the key value appears, copy it for later. This value will not be displayed again or be retrievable by any other means.
 
 # [Python](#tab/python)
 
-4. 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 `python-webapp`.
-   - Change **Supported account types** to **Accounts in any organizational directory and personal Microsoft accounts (e.g. Skype, Xbox, Outlook.com)**.
-   - In the Redirect URI (optional) section, select **Web** in the combo-box and enter the following redirect URIs: `http://localhost:5000/getAToken`.
+1. When the **Register an application page** appears, enter your application's registration information:
+   1. In the **Name** section, enter a meaningful application name that will be displayed to users of the app. For example, enter **python-webapp**.
+   1. Change **Supported account types** to **Accounts in any organizational directory and personal Microsoft accounts (e.g. Skype, Xbox, Outlook.com)**.
+   1. In the **Redirect URI (optional)** section, select **Web** in the combo  box and enter the following redirect URI: **http://localhost:5000/getAToken**.
 1. Select **Register** to create the application.
-1. On the app **Overview** page, find the **Application (client) ID** value and record it for later. You'll need it to configure the Visual Studio configuration file for this project.
-1. From the app's Overview page, select the **Authentication** section.
-   - In the **Advanced settings** section set **Logout URL** to `http://localhost:5000/logout`
-
-  Select **Save**.
-1. On the left hand menu, choose **Certificates & secrets** and click on **New client secret** in the **Client Secrets** section:
-
-      - Type a key description
-      - Select a key duration of **In 1 year**.
-      - When you click on **Add**, the key value will be displayed.
-      - Copy the value of the key. You will need it later.
+1. On the app's **Overview** page, find the **Application (client) ID** value and record it for later. You'll need it to configure the Visual Studio configuration file for this project.
+1. Select the **Authentication** section. In **Advanced settings**, set **Logout URL** to **http://localhost:5000/logout**. Then, select **Save**.
+1. On the left menu, select **Certificates & secrets**.
+1. In the **Client Secrets** section, select **New client secret**, and then:
+
+   1. Enter a key description.
+   1. Select a key duration of **In 1 year**.
+   1. Select **Add**.
+   1. When the key value appears, copy it. You'll need it later.
 ---
 
-## Register an app using PowerShell
+## Register an app by using PowerShell
 
 > [!NOTE]
-> Currently Azure AD PowerShell only creates applications with the following supported account types:
+> Currently, Azure AD PowerShell creates applications with only the following supported account types:
 >
-> - MyOrg (Accounts in this organizational directory only)
-> - AnyOrg (Accounts in any organizational directory).
+> - MyOrg (accounts in this organizational directory only)
+> - AnyOrg (accounts in any organizational directory)
 >
-> If you want to create an application that signs-in users with their personal Microsoft Accounts (e.g. Skype, XBox, Outlook.com), you can first create a multi-tenant application (Supported account types = Accounts in any organizational directory), and then change the `signInAudience` property in the application manifest from the Azure portal. This is explained in details in the step [1.3](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/1-WebApp-OIDC/1-3-AnyOrgOrPersonal#step-1-register-the-sample-with-your-azure-ad-tenant) of the ASP.NET Core tutorial (and can be generalized to web apps in any language).
+> You can create an application that signs in users with their personal Microsoft accounts (for example, Skype, Xbox, or Outlook.com). First, create a multitenant application. Supported account types are accounts in any organizational directory. Then, change the `signInAudience` property in the application manifest from the Azure portal. For more information, see [step 1.3](https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/1-WebApp-OIDC/1-3-AnyOrgOrPersonal#step-1-register-the-sample-with-your-azure-ad-tenant) in the ASP.NET Core tutorial. You can generalize this step to web apps in any language.
 
 ## Next steps