Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us410660-remove-old-articles

Author: asudbring

articles/app-service/app-service-asp-net-migration.md

@@ -111,4 +111,4 @@ The [app containerization tool](https://azure.microsoft.com/blog/accelerate-appl
 
 ## Next steps
 
-[Migrate an on-premises web application to Azure App Service](/training/modules/migrate-app-service-migration-assistant/)
+[Migrate an on-premises web application to Azure App Service](/training/modules/migrate-app-service-migration-assistant/)

articles/app-service/configure-authentication-customize-sign-in-out.md

@@ -1,63 +1,64 @@
 ---
-title: Configure an OpenID Connect provider
+title: Configure an OpenID Connect Provider
 description: Learn how to configure an OpenID Connect provider as an identity provider for your App Service or Azure Functions app.
-ms.topic: article
+ms.topic: how-to
 ms.date: 10/20/2021
 ms.reviewer: mahender
 ms.custom: AppServiceIdentity
 author: cephalin
 ms.author: cephalin
 ---
 
-# Configure your App Service or Azure Functions app to sign in using an OpenID Connect provider
+# Configure your App Service or Azure Functions app to sign in by using an OpenID Connect provider
 
 [!INCLUDE [app-service-mobile-selector-authentication](../../includes/app-service-mobile-selector-authentication.md)]
 
-This article shows you how to configure Azure App Service or Azure Functions to use a custom authentication provider that adheres to the [OpenID Connect specification](https://openid.net/connect/). OpenID Connect (OIDC) is an industry standard used by many identity providers (IDPs). You don't need to understand the details of the specification in order to configure your app to use an adherent IDP.
+This article shows you how to configure Azure App Service or Azure Functions to use a custom authentication provider that adheres to the [OpenID Connect (OIDC) specification](https://openid.net/connect/). OIDC is an industry standard that many identity providers (IDPs) use. You don't need to understand the details of the specification in order to configure your app to use an adherent IDP.
 
-You can configure your app to use one or more OIDC providers. Each must be given a unique alphanumeric name in the configuration, and only one can serve as the default redirect target.
+You can configure your app to use one or more OIDC providers. Each must have a unique alphanumeric name in the configuration, and only one can serve as the default redirect target.
 
 ## <a name="register"> </a>Register your application with the identity provider
 
-Your provider will require you to register the details of your application with it. One of these steps involves specifying a redirect URI. This redirect URI will be of the form `<app-url>/.auth/login/<provider-name>/callback`. Each identity provider should provide more instructions on how to complete these steps. `<provider-name>` will refer to the friendly name you give to the OpenID provider name in Azure.
+Your provider requires you to register the details of your application with it. One of these steps involves specifying a redirect URI that has the form `<app-url>/.auth/login/<provider-name>/callback`. Each identity provider should provide more instructions on how to complete the steps. The `<provider-name>` value refers to the friendly name that you give to the OpenID provider name in Azure.
 
 > [!NOTE]
-> Some providers may require additional steps for their configuration and how to use the values they provide. For example, Apple provides a private key which is not itself used as the OIDC client secret, and you instead must use it to craft a JWT which is treated as the secret you provide in your app config (see the "Creating the Client Secret" section of the [Sign in with Apple documentation](https://developer.apple.com/documentation/sign_in_with_apple/generate_and_validate_tokens))
->
-
-You'll need to collect a **client ID** and **client secret** for your application.
+> Some providers might require additional steps for their configuration and for using the values that they provide. For example, Apple provides a private key that isn't itself used as the OIDC client secret. You instead must use it to craft a JSON Web Token (JWT) that's treated as the secret that you provide in your app configuration. For more information, see [Creating a client secret](https://developer.apple.com/documentation/sign_in_with_apple/generate_and_validate_tokens) in the Apple developer documentation.
 
-> [!IMPORTANT]
-> The client secret is an important security credential. Don't share this secret with anyone or distribute it within a client application.
->
+You need to collect a *client ID* and a *client secret* for your application. The client secret is an important security credential. Don't share this secret with anyone or distribute it within a client application.
 
-Additionally, you'll need the OpenID Connect metadata for the provider. This is often exposed via a [configuration metadata document](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig), which is the provider's Issuer URL suffixed with `/.well-known/openid-configuration`. Gather this configuration URL.
+Additionally, you need the OIDC metadata for the provider. This metadata is often exposed in a [configuration metadata document](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig), which is the provider's issuer URL suffixed with `/.well-known/openid-configuration`. Gather this configuration URL.
 
-If you're unable to use a configuration metadata document, you'll need to gather the following values separately:
+If you can't use a configuration metadata document, gather the following values separately:
 
 - The issuer URL (sometimes shown as `issuer`)
-- The [OAuth 2.0 Authorization endpoint](https://tools.ietf.org/html/rfc6749#section-3.1) (sometimes shown as `authorization_endpoint`)
-- The [OAuth 2.0 Token endpoint](https://tools.ietf.org/html/rfc6749#section-3.2) (sometimes shown as `token_endpoint`)
-- The URL of the [OAuth 2.0 JSON Web Key Set](https://tools.ietf.org/html/rfc8414#section-2) document (sometimes shown as `jwks_uri`)
+- The [OAuth 2.0 authorization endpoint](https://tools.ietf.org/html/rfc6749#section-3.1) (sometimes shown as `authorization_endpoint`)
+- The [OAuth 2.0 token endpoint](https://tools.ietf.org/html/rfc6749#section-3.2) (sometimes shown as `token_endpoint`)
+- The URL of the [OAuth 2.0 JSON Web Key set](https://tools.ietf.org/html/rfc8414#section-2) document (sometimes shown as `jwks_uri`)
 
 ## <a name="configure"> </a>Add provider information to your application
 
-1. Sign in to the [Azure portal] and navigate to your app.
-1. Select **Authentication** in the menu on the left. Select **Add identity provider**.
-1. Select **OpenID Connect** in the identity provider dropdown.
-1. Provide the unique alphanumeric name selected earlier for **OpenID provider name**.
-1. If you have the URL for the **metadata document** from the identity provider, provide that value for **Metadata URL**. Otherwise, select the **Provide endpoints separately** option and put each URL gathered from the identity provider in the appropriate field.
-1. Provide the earlier collected **Client ID** and **Client Secret** in the appropriate fields.
-1. Specify an application setting name for your client secret. Your client secret will be stored as an app setting to ensure secrets are stored in a secure fashion. You can update that setting later to use [Key Vault references](./app-service-key-vault-references.md) if you wish to manage the secret in Azure Key Vault.
-1. Press the **Add** button to finish setting up the identity provider. 
+1. Sign in to the [Azure portal] and go to your app.
 
-> [!NOTE]
-> The OpenID provider name can't contain symbols like "-" because an appsetting will be created based on this and it doesn't support it. Use "_" instead.  
+1. On the left menu, select **Authentication**. Then select **Add identity provider**.
+
+1. In the dropdown list for identity providers, select **OpenID Connect**.
+
+1. For **OpenID provider name**, provide the unique alphanumeric name that you selected earlier.
+
+1. If you have the URL for the metadata document from the identity provider, provide that value for **Metadata URL**. Otherwise, select the **Provide endpoints separately** option and put each URL gathered from the identity provider in the appropriate field.
+
+1. Provide the values that you collected earlier for **Client ID** and **Client Secret**.
+
+1. Specify an application setting name for your client secret. Your client secret is stored as an app setting to ensure that secrets are stored in a secure fashion. You can update that setting later to use [Azure Key Vault references](./app-service-key-vault-references.md) if you want to manage the secret in Key Vault.
+
+1. Select **Add** to finish setting up the identity provider.
 
 > [!NOTE]
-> Azure requires "openid," "profile," and "email" scopes. Make sure you've configured your App Registration in your ID Provider with at least these scopes.  
+> The OpenID provider name can't contain a hyphen (-) because an app setting is created based on this name, and the app setting doesn't support hyphens. Use an underscore (_) instead.  
+>
+> Azure requires `openid`, `profile`, and `email` scopes. Make sure that you configured your app registration in your ID provider with at least these scopes.  
 
-## <a name="related-content"> </a>Next steps
+## <a name="related-content"> </a>Related content
 
 [!INCLUDE [app-service-mobile-related-content-get-started-users](../../includes/app-service-mobile-related-content-get-started-users.md)]