Merge pull request #108221 from stevemunk/how-to-manage-authentication

Grammar improvements and created end-links in web-sdk-best-practices.md

Author: Jak-MS

articles/azure-maps/how-to-manage-authentication.md

@@ -13,14 +13,15 @@ custom.ms: subject-rbac-steps
 
 # Manage authentication in Azure Maps
 
-When you create an Azure Maps account, your client ID is automatically generated along with primary and secondary keys that are required for authentication when using [Azure Active Directory (Azure AD)](../active-directory/fundamentals/active-directory-whatis.md) or [Shared Key authentication](./azure-maps-authentication.md#shared-key-authentication).
+When you create an Azure Maps account, your client ID and shared keys are created automatically. These values are required for authentication when using either [Azure Active Directory (Azure AD)] or [Shared Key authentication].
 
 ## Prerequisites
 
-Sign in to the [Azure portal](https://portal.azure.com). If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/) before you begin.
-- A familiarization with [managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md). Be sure to understand the two [Managed identity types](../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) and how they differ.
-- [An Azure Maps account](quick-demo-map-app.md#create-an-azure-maps-account).
-- A familiarization with [Azure Maps Authentication](./azure-maps-authentication.md).
+Sign in to the [Azure portal]. If you don't have an Azure subscription, create a [free account] before you begin.
+
+- A familiarization with [managed identities for Azure resources]. Be sure to understand the two [Managed identity types] and how they differ.
+- [An Azure Maps account].
+- A familiarization with [Azure Maps Authentication].
 
 ## View authentication details
 
@@ -29,7 +30,7 @@ Sign in to the [Azure portal](https://portal.azure.com). If you don't have an Az
 
 To view your Azure Maps authentication details:
 
-1. Sign in to the [Azure portal](https://portal.azure.com).
+1. Sign in to the [Azure portal].
 
 2. Select **All resources** in the **Azure services** section, then select your Azure Maps account.
 
@@ -41,18 +42,18 @@ To view your Azure Maps authentication details:
 
 ## Choose an authentication category
 
-Depending on your application needs, there are specific pathways to application security. Azure AD defines specific authentication categories to support a wide range of authentication flows. To choose the best category for your application, see [application categories](../active-directory/develop/authentication-flows-app-scenarios.md#application-categories).
+Depending on your application needs, there are specific pathways to application security. Azure AD defines specific authentication categories to support a wide range of authentication flows. To choose the best category for your application, see [application categories].
 
 > [!NOTE]
 > Understanding categories and scenarios will help you secure your Azure Maps application, whether you use Azure Active Directory or shared key authentication.
 
 ## How to add and remove managed identities
 
-To enable [Shared access signature (SAS) token authentication](./azure-maps-authentication.md#shared-access-signature-token-authentication) with the Azure Maps REST API you need to add a user-assigned managed identity to your Azure Maps account.
+To enable [Shared access signature (SAS) token authentication] with the Azure Maps REST API, you need to add a user-assigned managed identity to your Azure Maps account.
 
 ### Create a managed identity
 
-You can create a user-assigned managed identity before or after creating a map account. You can add the managed identity through the portal, Azure management SDKs, or the Azure Resource Manager (ARM) template. To add a user-assigned managed identity through an ARM template, specify the resource identifier of the user-assigned managed identity. See example below:
+You can create a user-assigned managed identity before or after creating a map account. You can add the managed identity through the portal, Azure management SDKs, or the Azure Resource Manager (ARM) template. To add a user-assigned managed identity through an ARM template, specify the resource identifier of the user-assigned managed identity.
 
 ```json
 "identity": {
@@ -67,7 +68,7 @@ You can create a user-assigned managed identity before or after creating a map a
 
 You can remove a system-assigned identity by disabling the feature through the portal or the Azure Resource Manager template in the same way that it was created. User-assigned identities can be removed individually. To remove all identities, set the identity type to `"None"`.
 
-Removing a system-assigned identity in this way will also delete it from Azure AD. System-assigned identities are also automatically removed from Azure AD when the Azure Maps account is deleted.
+Removing a system-assigned identity in this way also deletes it from Azure AD. System-assigned identities are also automatically removed from Azure AD when the Azure Maps account is deleted.
 
 To remove all identities by using the Azure Resource Manager template, update this section:
 
@@ -79,20 +80,20 @@ To remove all identities by using the Azure Resource Manager template, update th
 
 ## Choose an authentication and authorization scenario
 
-This table outlines common authentication and authorization scenarios in Azure Maps. Each scenario describes a type of app which can be used to access Azure Maps REST API. Use the links to learn detailed configuration information for each scenario.
+This table outlines common authentication and authorization scenarios in Azure Maps. Each scenario describes a type of app that can be used to access Azure Maps REST API. Use the links to learn detailed configuration information for each scenario.
 
 > [!IMPORTANT]
 > For production applications, we recommend implementing Azure AD with Azure role-based access control (Azure RBAC).
 
-| Scenario                                                                            | Authentication | Authorization | Development effort | Operational effort |
-| ----------------------------------------------------------------------------------- | -------------- | ------------- | ------------------ | ------------------ |
-| [Trusted daemon app or non-interactive client app](./how-to-secure-daemon-app.md)   | Shared Key     | N/A           | Medium             | High               |
-| [Trusted daemon or non-interactive client app](./how-to-secure-daemon-app.md)       | Azure AD       | High          | Low                | Medium             |
-| [Web single page app with interactive single-sign-on](./how-to-secure-spa-users.md) | Azure AD       | High          | Medium             | Medium             |
-| [Web single page app with non-interactive sign-on](./how-to-secure-spa-app.md)      | Azure AD       | High          | Medium             | Medium             |
-| [Web app, daemon app, or non-interactive sign-on app](./how-to-secure-sas-app.md)   | SAS Token      | High          | Medium             | Low                |
-| [Web application with interactive single-sign-on](./how-to-secure-webapp-users.md)  | Azure AD       | High          | High               | Medium             |
-| [IoT device or an input constrained application](./how-to-secure-device-code.md)    | Azure AD       | High          | Medium             | Medium             |
+| Scenario                                             | Authentication | Authorization | Development effort | Operational effort |
+| -----------------------------------------------------| -------------- | ------------- | ------------------ | ------------------ |
+| [Trusted daemon app or non-interactive client app]   | Shared Key     | N/A           | Medium             | High               |
+| [Trusted daemon or non-interactive client app]       | Azure AD       | High          | Low                | Medium             |
+| [Web single page app with interactive single-sign-on]| Azure AD       | High          | Medium             | Medium             |
+| [Web single page app with non-interactive sign-on]   | Azure AD       | High          | Medium             | Medium             |
+| [Web app, daemon app, or non-interactive sign-on app]| SAS Token      | High          | Medium             | Low                |
+| [Web application with interactive single-sign-on]    | Azure AD       | High          | High               | Medium             |
+| [IoT device or an input constrained application]     | Azure AD       | High          | Medium             | Medium             |
 
 ## View built-in Azure Maps role definitions
 
@@ -131,7 +132,7 @@ Request a token from the Azure AD token endpoint. In your Azure AD request, use
 | Azure public cloud     | `https://login.microsoftonline.com` | `https://atlas.microsoft.com/` |
 | Azure Government cloud | `https://login.microsoftonline.us`  | `https://atlas.microsoft.com/` |
 
-For more information about requesting access tokens from Azure AD for users and service principals, see [Authentication scenarios for Azure AD](../active-directory/develop/authentication-vs-authorization.md). To view specific scenarios, see [the table of scenarios](./how-to-manage-authentication.md#choose-an-authentication-and-authorization-scenario).
+For more information about requesting access tokens from Azure AD for users and service principals, see [Authentication scenarios for Azure AD]. To view specific scenarios, see [the table of scenarios].
 
 ## Manage and rotate shared keys
 
@@ -142,14 +143,14 @@ Your Azure Maps subscription keys are similar to a root password for your Azure
 
 ### Manually rotate subscription keys
 
-To help keep your Azure Maps account secure, we recommend periodically rotating your subscription keys. If possible, use Azure Key Vault to manage your access keys. If you aren't using Key Vault, you'll need to manually rotate your keys.
+To help keep your Azure Maps account secure, we recommend periodically rotating your subscription keys. If possible, use Azure Key Vault to manage your access keys. If you aren't using Key Vault, you need to manually rotate your keys.
 
 Two subscription keys are assigned so that you can rotate your keys. Having two keys ensures that your application maintains access to Azure Maps throughout the process.
 
 To rotate your Azure Maps subscription keys in the Azure portal:
 
 1. Update your application code to reference the secondary key for the Azure Maps account and deploy.
-2. In the [Azure portal](https://portal.azure.com/), navigate to your Azure Maps account.
+2. In the [Azure portal], navigate to your Azure Maps account.
 3. Under **Settings**, select **Authentication**.
 4. To regenerate the primary key for your Azure Maps account, select the **Regenerate** button next to the primary key.
 5. Update your application code to reference the new primary key and deploy.
@@ -163,9 +164,31 @@ To rotate your Azure Maps subscription keys in the Azure portal:
 Find the API usage metrics for your Azure Maps account:
 
 > [!div class="nextstepaction"]
-> [View usage metrics](how-to-view-api-usage.md)
+> [View usage metrics]
 
 Explore samples that show how to integrate Azure AD with Azure Maps:
 
 > [!div class="nextstepaction"]
-> [Azure AD authentication samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples)
+> [Azure AD authentication samples]
+
+[Azure portal]: https://portal.azure.com/
+[Azure AD authentication samples]: https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples
+[View usage metrics]: how-to-view-api-usage.md
+[Authentication scenarios for Azure AD]: ../active-directory/develop/authentication-vs-authorization.md
+[the table of scenarios]: how-to-manage-authentication.md#choose-an-authentication-and-authorization-scenario
+[Trusted daemon app or non-interactive client app]: how-to-secure-daemon-app.md
+[Trusted daemon or non-interactive client app]: how-to-secure-daemon-app.md
+[Web single page app with interactive single-sign-on]: how-to-secure-spa-users.md
+[Web single page app with non-interactive sign-on]: how-to-secure-spa-app.md
+[Web app, daemon app, or non-interactive sign-on app]: how-to-secure-sas-app.md
+[Web application with interactive single-sign-on]: how-to-secure-webapp-users.md
+[IoT device or an input constrained application]: how-to-secure-device-code.md
+[Shared access signature (SAS) token authentication]: azure-maps-authentication.md#shared-access-signature-token-authentication
+[application categories]: ../active-directory/develop/authentication-flows-app-scenarios.md#application-categories
+[Azure Active Directory (Azure AD)]: ../active-directory/fundamentals/active-directory-whatis.md
+[Shared Key authentication]: azure-maps-authentication.md#shared-key-authentication
+[free account]: https://azure.microsoft.com/free/
+[managed identities for Azure resources]: ../active-directory/managed-identities-azure-resources/overview.md
+[Managed identity types]: ../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types
+[An Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
+[Azure Maps Authentication]: azure-maps-authentication.md