edits

Author: Farah Alyasari

articles/azure-maps/azure-maps-authentication.md

@@ -13,32 +13,31 @@ ms.custom: mvc
 
 # Authentication with Azure Maps
 
-Azure Maps supports two ways to authenticate requests: Shared Key and Azure Active Directory (Azure AD). This article explains these authentication methods to help guide your implementation.
+Azure Maps supports two ways to authenticate requests: Shared Key authentication and Azure Active Directory authentication. This article explains these authentication methods to help guide your implementation.
 
 ## Shared Key authentication
 
-Shared Key authentication passes keys generated by an Azure Maps account with each request to Azure Maps. For each request to Azure Maps services, the *subscription key* needs to be added as a parameter to the URL. Primary and secondary keys are generated after the Azure Maps account is created. We recommend that you use the primary key as the subscription key when you call Azure Maps by using shared key authentication. The secondary key can be used in scenarios like rolling key changes.  
+Shared Key authentication passes keys generated by an Azure Maps account with each request to Azure Maps. For each request to Azure Maps services, the *subscription key* needs to be added as a parameter to the URL. Primary and secondary keys are generated after the Azure Maps account is created. We recommend you use the primary key as the subscription key when you call Azure Maps by using shared key authentication. The secondary key can be used in scenarios like rolling key changes.  
 
 For information about viewing your keys in the Azure portal, see [Manage authentication](https://aka.ms/amauthdetails).
 
 > [!Tip]
-> We recommend regenerating your keys regularly. You're provided with two keys so that you can maintain connections with one key while regenerating the other. When you regenerate your keys, you need to update any applications that access your account with the new keys.
+> We recommend regenerating your keys regularly. You're provided with two keys, so that you can maintain connections with one key while regenerating the other. When you regenerate your keys, you need to update any applications that access your account with the new keys.
 
 
 
 ## Authentication with Azure Active Directory (Preview)
 
-Azure Maps now offers authentication of requests for Azure Maps services using [Azure Active Directory (Azure AD)](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis). Azure AD provides identity-based authentication, including [role-based access control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/overview). RBAC is used to grant user-level, group-level, or application-level access to Azure Maps resources. The sections that follow can help you understand the concepts and components of Azure Maps integration with Azure AD.
-
+Azure Maps now offers requests authentication for Azure Maps services using [Azure Active Directory (Azure AD)](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis). Azure AD provides identity-based authentication, including [role-based access control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/overview). RBAC is used to grant user-level, group-level, or application-level access to Azure Maps resources. The next sections can help you understand concepts and components of Azure Maps integration with Azure AD.
 ## Authentication with OAuth access tokens
 
 Azure Maps accepts **OAuth 2.0** access tokens for Azure AD tenants associated with an Azure subscription that contains an Azure Maps account. Azure Maps accepts tokens for:
 
-* Azure AD users. 
-* Partner applications that use permissions delegated by users.
-* Managed identities for Azure resources.
+* Azure AD users
+* Partner applications that use permissions delegated by users
+* Managed identities for Azure resources
 
-Azure Maps generates a *unique identifier (client ID)* for each Azure Maps account. When you combine this client ID with an additional parameters, you can request tokens from Azure AD. To request a token, you need to specify the values in the following table based on your Azure Environment.
+Azure Maps generates a *unique identifier (client ID)* for each Azure Maps account. You can request tokens from Azure AD when you combine this client ID with additional parameters. To request a token, you need to specify the values in the following table based on your Azure Environment.
 
 | Azure Environment   | Azure AD token endpoint |
 | --------------------|-------------------------|
@@ -52,7 +51,7 @@ For general information about requesting tokens from Azure AD, see [What is auth
 
 ## Request Azure Map resources with OAuth tokens
 
-After a token is received from Azure AD, a request can be sent to Azure Maps with the following two required request headers set:
+After a token is received from Azure AD, a request is sent to Azure Maps with the following set of required request headers:
 
 | Request header    |    Value    |
 |:------------------|:------------|
@@ -75,17 +74,15 @@ For information about viewing your client ID, see [View authentication details](
 
 ## Control access with RBAC
 
-Azure AD lets you control access to secured resources by using RBAC. Set up your Azure Maps account and register your Azure Maps Azure AD TENANT. Then, you can set up RBAC for a user, group, application, or Azure resource on the Azure Maps account portal page.
-
-Azure Maps supports read access control for individual Azure AD users, groups, applications, and Azure services via managed identities for Azure resources.
+In Azure AD, use RBAC to control access to secured resources. Set up your Azure Maps account and register your Azure Maps Azure AD TENANT. Azure Maps supports read access control for individual Azure AD users, groups, applications, Azure resources, and Azure services via managed identities for Azure resources. On the Azure Maps portal page, you can set up RBAC for your desired roles.
 
 ![Azure Maps Data Reader (Preview)](./media/azure-maps-authentication/concept.png)
 
 For information about viewing your RBAC settings, see [How to configure RBAC for Azure Maps](https://aka.ms/amrbac).
 
 ## Managed identities for Azure resources and Azure Maps
 
-[Managed identities for Azure resources](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) provide Azure services (Azure App Service, Azure Functions, Azure Virtual Machines, and so on) with an automatically managed identity that can be authorized for access to Azure Maps services.  
+[Managed identities for Azure resources](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) provide Azure services with an automatically managed identity, which can be authorized to access Azure Maps services. Some examples of managed identities, include: Azure App Service, Azure Functions, and Azure Virtual Machines.
 
 ## Next steps