Skip to content

Commit ba3c534

Browse files
authored
Merge pull request #102573 from farah-alyasari/report7
report7
2 parents 8410460 + 3c3cd05 commit ba3c534

File tree

9 files changed

+31
-35
lines changed

9 files changed

+31
-35
lines changed

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

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Authentication methods | Microsoft Azure Maps
3-
description: In this article, you will learn about Azure Active Directory (Azure AD) or Shared Key authentication for using Microsoft Azure Maps services. Learn how to get Azure Maps subscription key.
3+
description: In this article, you'll learn about Azure Active Directory (Azure AD) and Shared Key authentication. Both are used for Microsoft Azure Maps services. Learn how to get Azure Maps subscription key.
44
author: walsehgal
55
ms.author: v-musehg
6-
ms.date: 12/30/2019
6+
ms.date: 01/28/2020
77
ms.topic: conceptual
88
ms.service: azure-maps
99
services: azure-maps
@@ -13,32 +13,31 @@ ms.custom: mvc
1313

1414
# Authentication with Azure Maps
1515

16-
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.
16+
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.
1717

1818
## Shared Key authentication
1919

20-
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.
20+
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.
2121

2222
For information about viewing your keys in the Azure portal, see [Manage authentication](https://aka.ms/amauthdetails).
2323

2424
> [!Tip]
25-
> 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 the account to use the new keys.
25+
> 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.
2626
2727

2828

2929
## Authentication with Azure Active Directory (Preview)
3030

31-
Azure Maps now offers [Azure Active Directory (Azure AD)](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) integration for the authentication of requests for Azure Maps services. Azure AD provides identity-based authentication, including [role-based access control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/overview), to grant user-level, group-level and 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.
32-
31+
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.
3332
## Authentication with OAuth access tokens
3433

3534
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:
3635

37-
* Azure AD users.
38-
* Partner applications that use permissions delegated by users.
39-
* Managed identities for Azure resources.
36+
* Azure AD users
37+
* Partner applications that use permissions delegated by users
38+
* Managed identities for Azure resources
4039

41-
Azure Maps generates a *unique identifier (client ID)* for each Azure Maps account. When you combine this client ID with additional parameters, you can request tokens from Azure AD by specifying the values in the following table depending upon your Azure Environment.
40+
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.
4241

4342
| Azure Environment | Azure AD token endpoint |
4443
| --------------------|-------------------------|
@@ -52,7 +51,7 @@ For general information about requesting tokens from Azure AD, see [What is auth
5251

5352
## Request Azure Map resources with OAuth tokens
5453

55-
After a token is received from Azure AD, a request can be sent to Azure Maps with the following two required request headers set:
54+
After a token is received from Azure AD, a request is sent to Azure Maps with the following set of required request headers:
5655

5756
| Request header | Value |
5857
|:------------------|:------------|
@@ -75,17 +74,15 @@ For information about viewing your client ID, see [View authentication details](
7574

7675
## Control access with RBAC
7776

78-
Azure AD lets you control access to secured resources by using RBAC. After you create your Azure Maps account and register your Azure Maps Azure AD application within your Azure AD tenant, you can set up RBAC for a user, group, application, or Azure resource on the Azure Maps account portal page.
79-
80-
Azure Maps supports read access control for individual Azure AD users, groups, applications, and Azure services via managed identities for Azure resources.
77+
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.
8178

8279
![Azure Maps Data Reader (Preview)](./media/azure-maps-authentication/concept.png)
8380

8481
For information about viewing your RBAC settings, see [How to configure RBAC for Azure Maps](https://aka.ms/amrbac).
8582

8683
## Managed identities for Azure resources and Azure Maps
8784

88-
[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. 
85+
[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.
8986

9087
## Next steps
9188

articles/azure-maps/how-to-manage-account-keys.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
2-
title: Manage your Azure Maps account in the Azure Portal | Microsoft Azure Maps
2+
title: Manage your Azure Maps account in the Azure portal | Microsoft Azure Maps
33
description: In this article, you will learn how to use the Azure portal to manage your Microsoft Azure Maps account.
44
author: walsehgal
55
ms.author: v-musehg
6-
ms.date: 02/14/2019
6+
ms.date: 01/27/2020
77
ms.topic: conceptual
88
ms.service: azure-maps
99
services: azure-maps
@@ -26,13 +26,13 @@ If you don't have an Azure subscription, create a [free account](https://azure.m
2626

2727
4. Enter the information for your new account.
2828

29-
![Enter Azure Maps account information in the Azure portal](./media/how-to-manage-account-keys/new-account-portal.png)
29+
[![Enter Azure Maps account information in the Azure portal](./media/how-to-manage-account-keys/new-account-portal.png)](./media/how-to-manage-account-keys/new-account-portal.png#lightbox)
3030

3131
## Delete an account
3232

3333
You can delete an account from the Azure portal. Navigate to the account overview page and select **Delete**.
3434

35-
![Delete your Azure Maps account in the Azure portal](./media/how-to-manage-account-keys/account-delete-portal.png)
35+
[![Delete your Azure Maps account in the Azure portal](./media/how-to-manage-account-keys/account-delete-portal.png)](./media/how-to-manage-account-keys/account-delete-portal.png#lightbox)
3636

3737
You then see a confirmation page. You can confirm the deletion of your account by typing its name.
3838

articles/azure-maps/how-to-manage-pricing-tier.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage your Azure Maps account's pricing tier | Microsoft Azure Maps
33
description: You can use the Azure portal to manage your Microsoft Azure Maps account and its pricing tier.
44
author: walsehgal
55
ms.author: v-musehg
6-
ms.date: 02/12/2019
6+
ms.date: 01/27/2020
77
ms.topic: conceptual
88
ms.service: azure-maps
99
services: azure-maps
@@ -12,21 +12,21 @@ manager: timlt
1212

1313
# Manage the pricing tier of your Azure Maps account
1414

15-
You can manage the pricing tier of your Azure Maps account through the Azure portal. After you create an [account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F), you can view or change your account's pricing tier.
15+
You can manage the pricing tier of your Azure Maps account through the Azure portal. You can also view or change your account's pricing tier after you create an [account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
1616

1717
Get more information about [choosing the right pricing tier in Azure Maps](https://docs.microsoft.com/azure/azure-maps/choose-pricing-tier).
1818

1919
## View your pricing tier
2020

2121
To view your chosen pricing tier, navigate to the **Pricing Tier** option in the settings menu.
2222

23-
![View chosen pricing tier](./media/how-to-manage-pricing-tier/view-pricing-tier.png)
23+
[ ![View chosen pricing tier](./media/how-to-manage-pricing-tier/view-pricing-tier.png) ](./media/how-to-manage-pricing-tier/view-pricing-tier.png#lightbox)
2424

2525
## Change a pricing tier
2626

2727
After you create your Azure Maps account, you can upgrade or downgrade the pricing tier for your Azure Maps account. To upgrade or downgrade, navigate to the **Pricing Tier** option in the settings menu. Select the pricing tier that isn't highlighted. Select the **Save** button to save your chosen pricing tier option.
2828

29-
![Change a pricing tier](./media/how-to-manage-pricing-tier/change-pricing-tier.png)
29+
[ ![Change a pricing tier](./media/how-to-manage-pricing-tier/change-pricing-tier.png) ](./media/how-to-manage-pricing-tier/change-pricing-tier.png#lightbox)
3030

3131
> [!NOTE]
3232
> You don't have to generate new subscription keys or client ID (for Azure AD authentication) if you upgrade or downgrade the pricing tier for your Azure Maps account.
6.73 KB
Loading
12.6 KB
Loading
8.73 KB
Loading
8.99 KB
Loading

articles/azure-maps/render-coverage.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Render coverage | Microsoft Azure Maps
3-
description: In this article, you will learn about regions with Microsoft Azure Maps render coverage along with their level of rendered details.
3+
description: In this article, learn about regions with Microsoft Azure Maps render coverage along with their level of rendered details.
44
author: jingjing-z
55
ms.author: jinzh
66
ms.date: 03/22/2019
@@ -13,9 +13,9 @@ manager:
1313

1414
# Azure Maps render coverage
1515

16-
Azure Maps uses both raster tiles and vector tiles to create maps. At its lowest resolution, the entire world fits on a single tile. At its highest resolution, a single tile represents 38 square meters. As you zoom in on a map, therefore, you can see increasingly more details about continents, regions, cities, and individual streets. For more information, see [Zoom levels and tile grid](zoom-levels-and-tile-grid.md).
16+
Azure Maps uses both raster tiles and vector tiles to create maps. At the lowest resolution, the entire world fits in a single tile. At the highest resolution, a single tile represents 38 square meters. As you zoom in, you'll see more details about continents, regions, cities, and individual streets. For more information about tiles, see [Zoom levels and tile grid](zoom-levels-and-tile-grid.md).
1717

18-
However, Maps does not have the same level of information and accuracy for all regions. The following tables provide information about what level of rendered detail you can expect from each region.
18+
However, Maps does not have the same level of information and accuracy for all regions. The following tables detail the level of information you can render for each region.
1919

2020
## Legend
2121

@@ -298,4 +298,4 @@ However, Maps does not have the same level of information and accuracy for all r
298298

299299
For more information about Azure Maps rendering, see [Zoom levels and tile grid](zoom-levels-and-tile-grid.md).
300300

301-
Learn about the [coverage areas for the Maps routing service](routing-coverage.md).
301+
Learn about the [coverage areas for the Maps routing service](routing-coverage.md).

articles/azure-maps/supported-languages.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -96,13 +96,15 @@ Azure Maps have been localized in a variety of languages across the services. Th
9696
## Azure Maps supported views
9797

9898
> [!Note]
99-
> Azure Maps was released in the following countries/regions on August 1, 2019:
99+
> On August 1, 2019, Azure Maps was released in the following countries/regions:
100100
> * Argentina
101101
> * India
102102
> * Morocco
103103
> * Pakistan
104104
>
105-
> After August 1, 2019, **View** parameter setting will define the returned map content for the new regions/countries listed above. We encourage you to ensure that you have set up the View parameter as required for the REST APIs and SDKs that your services are using.
105+
> After August 1, 2019, the **View** parameter will define the returned map content for the new regions/countries listed above. Azure Maps **View** parameter (also referred to as “user region parameter”) is a two letter ISO-3166 Country Code that will show the correct maps for that country/region specifying which set of geopolitically disputed content is returned via Azure Maps services, including borders and labels displayed on the map.
106+
107+
Ensure that you have set up the **View** parameter as required for the REST APIs and SDKs that your services are using.
106108
>
107109
>
108110
> **Rest APIs:**
@@ -130,15 +132,12 @@ Azure Maps have been localized in a variety of languages across the services. Th
130132
>
131133
> **SDKs:**
132134
>
133-
> Ensure that you have set up the View parameter as required, and you have the latest version of Web SDK and Android SDK. Affected SDKs:
135+
> Ensure that you have set up the **View** parameter as required, and you have the latest version of Web SDK and Android SDK. Affected SDKs:
134136
>
135137
> * Azure Maps Web SDK
136138
> * Azure Maps Android SDK
137139
138-
139-
Azure Maps **View** parameter (also referred to as “user region parameter”) is a two letter ISO-3166 Country Code that will show the correct maps for that country/region specifying which set of geopolitically disputed content is returned via Azure Maps services, including borders and labels displayed on the map.
140-
141-
By default View parameter is set to **Unified**, even if you haven’t defined it in the request. It is your responsibility to determine the location of your users, and then set the View parameter correctly for that location. Alternatively, you have the option to set ‘View=Auto’, which will return the map data based on the IP address of the request. The View parameter in Azure Maps must be used in compliance with applicable laws, including those regarding mapping of the country where maps, images, and other data and third-party content that you are authorized to access via Azure Maps is made available.
140+
By default the View parameter is set to **Unified**, even if you haven’t defined it in the request. Determine the location of your users, and then set the **View** parameter correctly for that location. Alternatively, you can set ‘View=Auto’, which will return the map data based on the IP address of the request. The **View** parameter in Azure Maps must be used in compliance with applicable laws, including those laws about mapping of the country where maps, images, and other data and third-party content that you're authorized to access via Azure Maps is made available.
142141

143142

144143
The following table provides supported views.

0 commit comments

Comments
 (0)