Merge pull request #94872 from mmacy/b2c-appreg-cap-fix

megvanhuygen · web-flow · commit f4f9cc6850a3 · 2019-11-05T14:31:21.000-08:00
[b2c] app reg capitalization fix to match UI
diff --git a/articles/active-directory-b2c/active-directory-b2c-custom-setup-msa-idp.md b/articles/active-directory-b2c/active-directory-b2c-custom-setup-msa-idp.md
@@ -40,7 +40,7 @@ To enable sign-in for users with a Microsoft account, you need to register an ap
 1. Select **Certificates & secrets**
 1. Click **New client secret**
 1. Enter a **Description** for the secret, for example *MSA Application Client Secret*, and then click **Add**.
-1. Record the application password shown in the **VALUE** column. You use this value in the next section.
+1. Record the application password shown in the **Value** column. You use this value in the next section.
 
 ## Create a policy key
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-faqs.md b/articles/active-directory-b2c/active-directory-b2c-faqs.md
@@ -128,7 +128,7 @@ Not currently. This feature is on our roadmap. Verifying your domain in the **Do
 
 Follow these steps to delete your Azure AD B2C tenant.
 
-You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-get-started-custom.md b/articles/active-directory-b2c/active-directory-b2c-get-started-custom.md
@@ -69,7 +69,7 @@ You need to register these two applications in your Azure AD B2C tenant only onc
 
 ### Register the IdentityExperienceFramework application
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -147,7 +147,7 @@ Now, grant permissions to the API scope you exposed earlier in the *IdentityExpe
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for both scopes. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for both scopes. It might take a few minutes for the permissions to propagate.
 
 * * *
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md b/articles/active-directory-b2c/active-directory-b2c-reference-audit-logs.md
@@ -119,7 +119,7 @@ Follow these steps register an application, grant it the required Microsoft Grap
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in account if it's been assigned the *Global Administrator* role, or sign in with an account in your Azure AD B2C tenant that's been assigned the *Global Administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for the *AuditLog.Read.All* permission. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for the *AuditLog.Read.All* permission. It might take a few minutes for the permissions to propagate.
 
 * * *
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-setup-aad-custom.md b/articles/active-directory-b2c/active-directory-b2c-setup-aad-custom.md
@@ -43,7 +43,7 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
 
 1. Select **Register**. Record the **Application (client) ID** for use in a later step.
 1. Select **Certificates & secrets**, and then select **New client secret**.
-1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **VALUE** of the secret for use in a later step.
+1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
 
 ## Create a policy key
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-setup-commonaad-custom.md b/articles/active-directory-b2c/active-directory-b2c-setup-commonaad-custom.md
@@ -43,7 +43,7 @@ To enable sign-in for users from a specific Azure AD organization, you need to r
 
 1. Select **Register**. Record the **Application (client) ID** for use in a later step.
 1. Select **Certificates & secrets**, and then select **New client secret**.
-1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **VALUE** of the secret for use in a later step.
+1. Enter a **Description** for the secret, select an expiration, and then select **Add**. Record the **Value** of the secret for use in a later step.
 
 ## Create a policy key
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-setup-msa-app.md b/articles/active-directory-b2c/active-directory-b2c-setup-msa-app.md
@@ -33,7 +33,7 @@ To use a Microsoft account as an [identity provider](active-directory-b2c-refere
 1. Select **Certificates & secrets**
 1. Click **New client secret**
 1. Enter a **Description** for the secret, for example *Application password 1*, and then click **Add**.
-1. Record the application password shown in the **VALUE** column. You need this when you configure the identity provider in the next section.
+1. Record the application password shown in the **Value** column. You need this when you configure the identity provider in the next section.
 
 ## Configure a Microsoft account as an identity provider
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app-webapi.md b/articles/active-directory-b2c/active-directory-b2c-tutorials-desktop-app-webapi.md
@@ -62,12 +62,12 @@ In the prerequisite tutorial, you registered a native client application named *
 1. Under **Configured permissions**, select **Add a permission**.
 1. Select the **My APIs** tab.
 1. Select the API to which the native client application should be granted access. For example, *webapi1*.
-1. Under **PERMISSION**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
+1. Under **Permission**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
 1. Select **Add permissions**. As directed, wait a few minutes before proceeding to the next step.
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for both scopes. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for both scopes. It might take a few minutes for the permissions to propagate.
 
 * * *
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-tutorials-spa.md b/articles/active-directory-b2c/active-directory-b2c-tutorials-spa.md
@@ -44,7 +44,7 @@ Additionally, you need the following in your local development environment:
 
 In the second tutorial that you completed as part of the prerequisites, you registered a web application in Azure AD B2C. To enable communication with the sample in the tutorial, you need to add a redirect URI to the application in Azure AD B2C.
 
-You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to update the application. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to update the application. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-tutorials-web-api.md b/articles/active-directory-b2c/active-directory-b2c-tutorials-web-api.md
@@ -35,7 +35,7 @@ Complete the steps and prerequisites in [Tutorial: Enable authenticate in a web
 
 Web API resources need to be registered in your tenant before they can accept and respond to protected resource requests by client applications that present an access token.
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/articles/active-directory-b2c/active-directory-b2c-tutorials-web-app.md b/articles/active-directory-b2c/active-directory-b2c-tutorials-web-app.md
@@ -37,7 +37,7 @@ In the tutorial that you completed as part of the prerequisites, you registered
 
 ### Add a redirect URI (reply URL)
 
-You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to update the application. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to update the application. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/articles/active-directory-b2c/add-web-application.md b/articles/active-directory-b2c/add-web-application.md
@@ -17,7 +17,7 @@ ms.subservice: B2C
 
  Register web API resources in your tenant so that they can accept and respond to requests by client applications that present an access token. This article shows you how to register a web API in Azure Active Directory B2C (Azure AD B2C).
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -47,7 +47,7 @@ If you have an application that implements the implicit grant flow, for example
 
 1. Under **Manage**, select **Authentication**.
 1. Select **Try out the new experience** (if shown).
-1. Under **IMPLICIT GRANT**, select both the **Access tokens** and **ID tokens** check boxes.
+1. Under **Implicit grant**, select both the **Access tokens** and **ID tokens** check boxes.
 1. Select **Save**.
 
 * * *
diff --git a/articles/active-directory-b2c/secure-api-management.md b/articles/active-directory-b2c/secure-api-management.md
@@ -31,7 +31,7 @@ You need the following resources in place before continuing with the steps in th
 
 When you secure an API in Azure API Management with Azure AD B2C, you need several values for the [inbound policy](../api-management/api-management-howto-policies.md) that you create in APIM. First, record the application ID of an application you've previously created in your Azure AD B2C tenant. If you're using the application you created in the prerequisites, use the application ID for *webbapp1*.
 
-You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to get the application ID. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+You can use the current **Applications** experience or our new unified **App registrations (Preview)** experience to get the application ID. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -47,7 +47,7 @@ You can use the current **Applications** experience or our new unified **App reg
 1. Select the **Directory + subscription** filter in the top menu, and then select the directory that contains your Azure AD B2C tenant.
 1. In the left menu, select **Azure AD B2C**. Or, select **All services** and search for and select **Azure AD B2C**.
 1. Select **App registrations (Preview)**, then select the **Owned applications** tab.
-1. Record the value in the **APPLICATION (CLIENT) ID** column for *webapp1* or another application you've previously created.
+1. Record the value in the **Application (client) ID** column for *webapp1* or another application you've previously created.
 
 * * *
 
diff --git a/articles/active-directory-b2c/tutorial-register-applications.md b/articles/active-directory-b2c/tutorial-register-applications.md
@@ -31,7 +31,7 @@ If you haven't already created your own [Azure AD B2C Tenant](tutorial-create-te
 
 ## Register a web application
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -75,7 +75,7 @@ Once the application registration is complete, enable the implicit grant flow:
 
 1. Under **Manage**, select **Authentication**.
 1. Select **Try out the new experience** (if shown).
-1. Under **IMPLICIT GRANT**, select both the **Access tokens** and **ID tokens** check boxes.
+1. Under **Implicit grant**, select both the **Access tokens** and **ID tokens** check boxes.
 1. Select **Save**.
 
 * * *
@@ -97,7 +97,7 @@ If your application exchanges a code for a token, you need to create an applicat
 1. Select **New client secret**.
 1. Enter a description for the client secret in the **Description** box. For example, *clientsecret1*.
 1. Under **Expires**, select a duration for which the secret is valid, and then select **Add**.
-1. Record the secret's **VALUE**. You use this value as the application secret in your application's code.
+1. Record the secret's **Value**. You use this value as the application secret in your application's code.
 
 * * *
 
diff --git a/includes/active-directory-b2c-appreg-idp.md b/includes/active-directory-b2c-appreg-idp.md
@@ -7,7 +7,7 @@ ms.date: 10/16/2019
 ms.author: marsma
 # Used by the identity provider (IdP) setup articles under "Custom policy"
 ---
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -36,5 +36,5 @@ Once the application registration is complete, enable the implicit grant flow:
 
 1. Under **Manage**, select **Authentication**.
 1. Select **Try out the new experience** (if shown).
-1. Under **IMPLICIT GRANT**, select both the **Access tokens** and **ID tokens** check boxes.
+1. Under **Implicit grant**, select both the **Access tokens** and **ID tokens** check boxes.
 1. Select **Save**.
diff --git a/includes/active-directory-b2c-appreg-mgmt.md b/includes/active-directory-b2c-appreg-mgmt.md
@@ -8,7 +8,7 @@ ms.author: marsma
 # Used by user and audit log management articles. Application is used for
 # interacting with Graph API (AD Graph or MS Graph, depending on article).
 ---
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/includes/active-directory-b2c-appreg-native.md b/includes/active-directory-b2c-appreg-native.md
@@ -7,7 +7,7 @@ ms.date: 10/16/2019
 ms.author: marsma
 # Used by articles that register native client applications in the B2C tenant.
 ---
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/includes/active-directory-b2c-appreg-ropc.md b/includes/active-directory-b2c-appreg-ropc.md
@@ -7,7 +7,7 @@ ms.date: 10/16/2019
 ms.author: marsma
 # Used by the ROPC configuration articles for both user flows and custom policies
 ---
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
diff --git a/includes/active-directory-b2c-appreg-webapi.md b/includes/active-directory-b2c-appreg-webapi.md
@@ -9,7 +9,7 @@ ms.author: marsma
 ---
 Web API resources need to be registered in your tenant before they can accept and respond to protected resource requests by client applications that present an access token.
 
-To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the preview experience](https://aka.ms/b2cappregintro).
+To register an application in your Azure AD B2C tenant, you can use the current **Applications** experience, or our new unified **App registrations (Preview)** experience. [Learn more about the new experience](https://aka.ms/b2cappregintro).
 
 #### [Applications](#tab/applications/)
 
@@ -40,5 +40,5 @@ Next, enable the implicit grant flow:
 
 1. Under **Manage**, select **Authentication**.
 1. Select **Try out the new experience** (if shown).
-1. Under **IMPLICIT GRANT**, select both the **Access tokens** and **ID tokens** check boxes.
+1. Under **Implicit grant**, select both the **Access tokens** and **ID tokens** check boxes.
 1. Select **Save**.
diff --git a/includes/active-directory-b2c-client-secret.md b/includes/active-directory-b2c-client-secret.md
@@ -21,4 +21,4 @@ ms.author: marsma
 1. Select **New client secret**.
 1. Enter a description for the client secret in the **Description** box. For example, *clientsecret1*.
 1. Under **Expires**, select a duration for which the secret is valid, and then select **Add**.
-1. Record the secret's **VALUE**. You use this value for configuration in a later step.
+1. Record the secret's **Value**. You use this value for configuration in a later step.
diff --git a/includes/active-directory-b2c-permissions-api.md b/includes/active-directory-b2c-permissions-api.md
@@ -23,9 +23,9 @@ ms.author: marsma
 1. Under **Configured permissions**, select **Add a permission**.
 1. Select the **My APIs** tab.
 1. Select the API to which the web application should be granted access. For example, *webapi1*.
-1. Under **PERMISSION**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
+1. Under **Permission**, expand **demo**, and then select the scopes that you defined earlier. For example, *demo.read* and *demo.write*.
 1. Select **Add permissions**. As directed, wait a few minutes before proceeding to the next step.
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the *Cloud application administrator* role.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS** for both scopes. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status** for both scopes. It might take a few minutes for the permissions to propagate.
diff --git a/includes/active-directory-b2c-permissions-directory.md b/includes/active-directory-b2c-permissions-directory.md
@@ -29,4 +29,4 @@ ms.author: marsma
 1. Select **Grant admin consent for (your tenant name)**.
 1. Select a tenant administrator account.
 1. Select **Accept**.
-1. Select **Refresh**, and then verify that "Granted for ..." appears under **STATUS**. It might take a few minutes for the permissions to propagate.
+1. Select **Refresh**, and then verify that "Granted for ..." appears under **Status**. It might take a few minutes for the permissions to propagate.
