Merge pull request #79040 from mmacy/refresh-tut-2

[b2c] refresh tutorial 2 - register app

Author: Ja-Dunn

articles/active-directory-b2c/tutorial-register-applications.md

@@ -1,5 +1,5 @@
 ---
-title: Tutorial - Register an application - Azure Active Directory B2C | Microsoft Docs
+title: Tutorial - Register an application - Azure Active Directory B2C
 description: Learn how to register a web application in Azure Active Directory B2C using the Azure portal.
 services: active-directory-b2c
 author: mmacy
@@ -8,7 +8,7 @@ manager: celestedg
 ms.service: active-directory
 ms.workload: identity
 ms.topic: article
-ms.date: 02/05/2019
+ms.date: 06/07/2019
 ms.author: marsma
 ms.subservice: B2C
 ---
@@ -36,7 +36,9 @@ If you haven't already created your own [Azure AD B2C Tenant](tutorial-create-te
 3. Select **Applications**, and then select **Add**.
 4. Enter a name for the application. For example, *webapp1*.
 5. For **Include web app/ web API** and **Allow implicit flow**, select **Yes**.
-6. For **Reply URL**, enter an endpoint where Azure AD B2C should return any tokens that your application requests. For example, you can set it to listen locally at `https://localhost:44316` If you don't yet know the port number, you can enter a placeholder value and change it later. For testing purposes you could set it to `https://jwt.ms`, which displays the contents of a token for inspection. For this tutorial, set it to `https://jwt.ms`. 
+6. For **Reply URL**, enter an endpoint where Azure AD B2C should return any tokens that your application requests. For example, you could set it to listen locally at `https://localhost:44316`. If you don't yet know the port number, you can enter a placeholder value and change it later.
+
+    For testing purposes like this tutorial you can set it to `https://jwt.ms` which displays the contents of a token for inspection. For this tutorial, set the **Reply URL** to `https://jwt.ms`.
 
     The reply URL must begin with the scheme `https`, and all reply URL values must share a single DNS domain. For example, if the application has a reply URL of `https://login.contoso.com`, you can add to it like this URL `https://login.contoso.com/new`. Or, you can refer to a DNS subdomain of `login.contoso.com`, such as `https://new.login.contoso.com`. If you want to have an application with `login-east.contoso.com` and `login-west.contoso.com` as reply URLs, you must add those reply URLs in this order: `https://contoso.com`, `https://login-east.contoso.com`, `https://login-west.contoso.com`. You can add the latter two because they're subdomains of the first reply URL, `contoso.com`.
 
@@ -46,9 +48,9 @@ If you haven't already created your own [Azure AD B2C Tenant](tutorial-create-te
 
 If your application exchanges a code for a token, you need to create an application secret.
 
-1. Navigate back to the newly created app after following above tutorial. 
-2. Select **Keys** and then click **Generate key**.
-3. Select **Save** to view the key. Make note of the **App key** value. You use the value as the application secret in your application's code.
+1. In the **Azure AD B2C - Applications** page, select the application you created, for example *webapp1*.
+2. Select **Keys** and then select **Generate key**.
+3. Select **Save** to view the key. Make note of the **App key** value. You use this value as the application secret in your application's code.
 
 ## Next steps
 
@@ -58,5 +60,7 @@ In this article, you learned how to:
 > * Register a web application
 > * Create a client secret
 
+Next, learn how to create user flows to enable your users to sign up, sign in, and manage their profiles.
+
 > [!div class="nextstepaction"]
-> [Create user flows in Azure Active Directory B2C](tutorial-create-user-flows.md)
+> [Create user flows in Azure Active Directory B2C >](tutorial-create-user-flows.md)