Skip to content

Commit 1baffea

Browse files
committed
made some of the changes
1 parent b6b2213 commit 1baffea

21 files changed

+181
-133
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ For general information about authenticating with Azure AD, see [Authentication
5151

5252
## Managed identities for Azure resources and Azure Maps
5353

54-
[Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) provide Azure services with an automatically managed application based security principal that can authenticate with Azure AD. With Azure role-based access control (Azure RBAC), the managed identity security principal can be authorized to access Azure Maps services. Some examples of managed identities include: Azure App Service, Azure Functions, and Azure Virtual Machines. For a list of managed identities, see [Services that support managed identities for Azure resources](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md). For more information on managed identities, see [Manage authentication in Azure Maps](./how-to-manage-authentication.md).
54+
[Managed identities for Azure resources](../active-directory/managed-identities-azure-resources/overview.md) provide Azure services with an automatically managed application based security principal that can authenticate with Azure AD. With Azure role-based access control (Azure RBAC), the managed identity security principal can be authorized to access Azure Maps services. Some examples of managed identities include: Azure App Service, Azure Functions, and Azure Virtual Machines. For a list of managed identities, see [Azure services that can use managed identities to access other services](../active-directory/managed-identities-azure-resources/services-support-managed-identities.md). For more information on managed identities, see [Manage authentication in Azure Maps](./how-to-manage-authentication.md).
5555

5656
### Configure application Azure AD authentication
5757

@@ -120,11 +120,11 @@ The following role definition types exist to support application scenarios.
120120
121121
Some Azure Maps services may require elevated privileges to perform write or delete actions on Azure Maps REST APIs. Azure Maps Data Contributor role is required for services, which provide write or delete actions. The following table describes what services Azure Maps Data Contributor is applicable when using write or delete actions. When only read actions are required, the Azure Maps Data Reader role can be used in place of the Azure Maps Data Contributor role.
122122
123-
| Azure Maps Service | Azure Maps Role Definition |
123+
| Azure Maps service | Azure Maps Role Definition |
124124
| :--------------------- | :-------------------------- |
125-
| [Data](/rest/api/maps/data) | Azure Maps Data Contributor |
126-
| [Creator](/rest/api/maps-creator/) | Azure Maps Data Contributor |
127-
| [Spatial](/rest/api/maps/spatial) | Azure Maps Data Contributor |
125+
| [Data](/rest/api/maps/data) | Azure Maps Data Contributor |
126+
| [Creator](/rest/api/maps-creator/) | Azure Maps Data Contributor |
127+
| [Spatial](/rest/api/maps/spatial) | Azure Maps Data Contributor |
128128
| Batch [Search](/rest/api/maps/search) and [Route](/rest/api/maps/route) | Azure Maps Data Contributor |
129129
130130
For information about viewing your Azure RBAC settings, see [How to configure Azure RBAC for Azure Maps](./how-to-manage-authentication.md).
@@ -154,7 +154,7 @@ Assigning a role assignment to a resource group can enable access to multiple Az
154154
155155
## Disable local authentication
156156
157-
Azure Maps accounts support the standard Azure property in the [Azure Maps Management REST API](/rest/api/maps-management/) for `Microsoft.Maps/accounts` called `disableLocalAuth`. When `true`, all authentication to the Azure Maps data-plane REST API is disabled, except [Azure AD authentication](./azure-maps-authentication.md#azure-ad-authentication). This is configured using Azure Policy to control distribution and management of shared keys and SAS tokens. For more information, see [What is Azure Policy?](../governance/policy/overview.md).
157+
Azure Maps accounts support the standard Azure property in the [Management API](/rest/api/maps-management/) for `Microsoft.Maps/accounts` called `disableLocalAuth`. When `true`, all authentication to the Azure Maps data-plane REST API is disabled, except [Azure AD authentication](./azure-maps-authentication.md#azure-ad-authentication). This is configured using Azure Policy to control distribution and management of shared keys and SAS tokens. For more information, see [What is Azure Policy?](../governance/policy/overview.md).
158158
159159
Disabling local authentication doesn't take effect immediately. Allow a few minutes for the service to block future authentication requests. To re-enable local authentication, set the property to `false` and after a few minutes local authentication will resume.
160160

articles/azure-maps/azure-maps-qps-rate-limits.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -16,27 +16,27 @@ Azure Maps does not have any maximum daily limits on the number of requests that
1616

1717
Below are the QPS usage limits for each Azure Maps service by Pricing Tier.
1818

19-
| Azure Maps Service | QPS Limit: Gen 2 Pricing Tier | QPS Limit: Gen 1 S1 Pricing Tier | QPS Limit: Gen 1 S0 Pricing Tier |
19+
| Azure Maps service | QPS Limit: Gen 2 Pricing Tier | QPS Limit: Gen 1 S1 Pricing Tier | QPS Limit: Gen 1 S0 Pricing Tier |
2020
| ----------------- | :--------------------------: | :------------------------------: | :------------------------: |
21-
| Copyright Service | 10 | 10 | 10 |
21+
| Copyright service | 10 | 10 | 10 |
2222
| Creator - Alias, TilesetDetails | 10 | Not Available | Not Available |
2323
| Creator - Conversion, Dataset, Feature State, WFS | 50 | Not Available | Not Available |
24-
| Data Service | 50 | 50 | Not Available |
25-
| Elevation Service | 50 | 50 | Not Available |
26-
| Geolocation Service | 50 | 50 | 50 |
27-
| Render Service - Contour tiles, Digital Elevation Model (DEM) tiles and Customer tiles | 50 | 50 | Not Available |
28-
| Render Service - Traffic tiles and Static maps | 50 | 50 | 50 |
29-
| Render Service - Road tiles | 500 | 500 | 50 |
30-
| Render Service - Satellite tiles | 250 | 250 | Not Available |
31-
| Render Service - Weather tiles | 100 | 100 | 50 |
32-
| Route Service - Batch | 10 | 10 | Not Available |
33-
| Route Service - Non-Batch | 50 | 50 | 50 |
34-
| Search Service - Batch | 10 | 10 | Not Available |
35-
| Search Service - Non-Batch | 500 | 500 | 50 |
36-
| Search Service - Non-Batch Reverse | 250 | 250 | 50 |
37-
| Spatial Service | 50 | 50 | Not Available |
38-
| Timezone Service | 50 | 50 | 50 |
39-
| Traffic Service | 50 | 50 | 50 |
40-
| Weather Service | 50 | 50 | 50 |
24+
| Data service | 50 | 50 | Not Available |
25+
| Elevation service | 50 | 50 | Not Available |
26+
| Geolocation service | 50 | 50 | 50 |
27+
| Render service - Contour tiles, Digital Elevation Model (DEM) tiles and Customer tiles | 50 | 50 | Not Available |
28+
| Render service - Traffic tiles and Static maps | 50 | 50 | 50 |
29+
| Render service - Road tiles | 500 | 500 | 50 |
30+
| Render service - Satellite tiles | 250 | 250 | Not Available |
31+
| Render service - Weather tiles | 100 | 100 | 50 |
32+
| Route service - Batch | 10 | 10 | Not Available |
33+
| Route service - Non-Batch | 50 | 50 | 50 |
34+
| Search service - Batch | 10 | 10 | Not Available |
35+
| Search service - Non-Batch | 500 | 500 | 50 |
36+
| Search service - Non-Batch Reverse | 250 | 250 | 50 |
37+
| Spatial service | 50 | 50 | Not Available |
38+
| Timezone service | 50 | 50 | 50 |
39+
| Traffic service | 50 | 50 | 50 |
40+
| Weather service | 50 | 50 | 50 |
4141

4242
When QPS limits are reached, an HTTP 429 error will be returned. If you are using the Gen 2 or Gen 1 S1 pricing tiers, you can create an Azure Maps *Technical* Support Request in the [Azure portal](https://portal.azure.com/) to increase a specific QPS limit if needed. QPS limits for the Gen 1 S0 pricing tier cannot be increased.

articles/azure-maps/creator-facility-ontology.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,13 @@ Facility ontology defines how Azure Maps Creator internally stores facility data
1919

2020
:::zone pivot="facility-ontology-v1"
2121

22-
The Facility 1.0 contains revisions for the Facility feature class definitions for [Azure Maps Services](https://aka.ms/AzureMaps).
22+
The Facility 1.0 contains revisions for the Facility feature class definitions for [Azure Maps services](https://aka.ms/AzureMaps).
2323

2424
:::zone-end
2525

2626
:::zone pivot="facility-ontology-v2"
2727

28-
The Facility 2.0 contains revisions for the Facility feature class definitions for [Azure Maps Services](https://aka.ms/AzureMaps).
28+
The Facility 2.0 contains revisions for the Facility feature class definitions for [Azure Maps services](https://aka.ms/AzureMaps).
2929

3030
:::zone-end
3131

articles/azure-maps/creator-indoor-maps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -257,9 +257,9 @@ The Azure Maps [Render V2-Get Map Tile API](/rest/api/maps/render-v2/get-map-til
257257

258258
Applications can use the Render V2-Get Map Tile API to request tilesets. The tilesets can then be integrated into a map control or SDK. For an example of a map control that uses the Render V2 service, see [Indoor Maps Module](#indoor-maps-module).
259259

260-
### Web Feature Service API
260+
### Web Feature service API
261261

262-
You can use the [Web Feature Service (WFS) API](/rest/api/maps/v2/wfs) to query datasets. WFS follows the [Open Geospatial Consortium API Features](https://docs.opengeospatial.org/DRAFTS/17-069r4.html). You can use the WFS API to query features within the dataset itself. For example, you can use WFS to find all mid-size meeting rooms of a specific facility and floor level.
262+
You can use the [Web Feature service](/rest/api/maps/v2/wfs) (WFS) to query datasets. WFS follows the [Open Geospatial Consortium API Features](https://docs.opengeospatial.org/DRAFTS/17-069r4.html). You can use the WFS API to query features within the dataset itself. For example, you can use WFS to find all mid-size meeting rooms of a specific facility and floor level.
263263

264264
### Alias API
265265

articles/azure-maps/drawing-tools-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Learn how to use additional features of the drawing tools module:
8686
> [!div class="nextstepaction"]
8787
> [Interaction types and keyboard shortcuts](drawing-tools-interactions-keyboard-shortcuts.md)
8888
89-
Learn more about the Services module:
89+
Learn more about the services module:
9090

9191
> [!div class="nextstepaction"]
9292
> [Services module](how-to-use-services-module.md)

articles/azure-maps/how-to-create-data-registries.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ services: azure-maps
1212

1313
# How to create data registry (preview)
1414

15-
The [data registry] service enables you to register data content in an Azure Storage Account with your Azure Maps account. An example of data might include a collection of Geofences used in the Azure Maps Geofencing Service. Another example is ZIP files containing drawing packages (DWG) or GeoJSON files that Azure Maps Creator uses to create or update indoor maps.
15+
The [data registry] service enables you to register data content in an Azure Storage Account with your Azure Maps account. An example of data might include a collection of Geofences used in the Azure Maps Geofencing service. Another example is ZIP files containing drawing packages (DWG) or GeoJSON files that Azure Maps Creator uses to create or update indoor maps.
1616

1717
## Prerequisites
1818

@@ -22,7 +22,7 @@ The [data registry] service enables you to register data content in an Azure Sto
2222

2323
>[!IMPORTANT]
2424
>
25-
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your account wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator Services](how-to-manage-creator.md#access-to-creator-services).
25+
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your account wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator services](how-to-manage-creator.md#access-to-creator-services).
2626
> - In the URL examples in this article you will need to replace:
2727
> - `{Azure-Maps-Subscription-key}` with your Azure Maps [subscription key].
2828
> - `{udid}` with the user data ID of your data registry. For more information, see [The user data ID](#the-user-data-id).

articles/azure-maps/how-to-creator-wayfinding.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,23 +12,23 @@ services: azure-maps
1212

1313
# Indoor maps wayfinding service (preview)
1414

15-
The Azure Maps Creator [wayfinding service][wayfinding service] allows you to navigate from place to place anywhere within your indoor map. The service utilizes stairs and elevators to navigate between floors and provides guidance to help you navigate around physical obstructions. This article describes how to generate a path from a starting point to a destination point in a sample indoor map.
15+
The Azure Maps Creator [wayfinding service] allows you to navigate from place to place anywhere within your indoor map. The service utilizes stairs and elevators to navigate between floors and provides guidance to help you navigate around physical obstructions. This article describes how to generate a path from a starting point to a destination point in a sample indoor map.
1616

1717
## Prerequisites
1818

1919
- Understanding of [Creator concepts](creator-indoor-maps.md).
20-
- An Azure Maps Creator [dataset][dataset] and [tileset][tileset]. If you have never used Azure Maps Creator to create an indoor map, you might find the [Use Creator to create indoor maps](tutorial-creator-indoor-maps.md) tutorial helpful.
20+
- An Azure Maps Creator [dataset] and [tileset]. If you have never used Azure Maps Creator to create an indoor map, you might find the [Use Creator to create indoor maps](tutorial-creator-indoor-maps.md) tutorial helpful.
2121

2222
>[!IMPORTANT]
2323
>
24-
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator Services][how to manage access to creator services].
24+
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator services].
2525
> - In the URL examples in this article you will need to:
2626
> - Replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
27-
> - Replace `{datasetId`} with your `datasetId`. For more information, see the [Check the dataset creation status][check dataset creation status] section of the *Use Creator to create indoor maps* tutorial.
27+
> - Replace `{datasetId`} with your `datasetId`. For more information, see the [Check the dataset creation status] section of the *Use Creator to create indoor maps* tutorial.
2828
2929
## Create a routeset
3030

31-
A [routeset][routeset] is a collection of indoor map data that is used by the wayfinding service.
31+
A [routeset] is a collection of indoor map data that is used by the wayfinding service.
3232

3333
A routeset is created from a dataset, but is independent from that dataset. This means that if the dataset is deleted, the routeset continues to exist.
3434

@@ -101,7 +101,7 @@ The `facilityId`, a property of the routeset, is a required parameter when searc
101101

102102
## Get a wayfinding path
103103

104-
In this section, you’ll use the [wayfinding API][wayfinding API] to generate a path from the routeset you created in the previous section. The wayfinding API requires a query that contains start and end points in an indoor map, along with floor level ordinal numbers. For more information about Creator wayfinding, see [wayfinding][wayfinding] in the concepts article.
104+
In this section, you’ll use the [wayfinding API] to generate a path from the routeset you created in the previous section. The wayfinding API requires a query that contains start and end points in an indoor map, along with floor level ordinal numbers. For more information about Creator wayfinding, see [wayfinding] in the concepts article.
105105

106106
To create a wayfinding query:
107107

@@ -127,6 +127,6 @@ The wayfinding service calculates the path through specific intervening points.
127127
[routeset]: /rest/api/maps/v20220901preview/routeset
128128
[wayfinding]: creator-indoor-maps.md#wayfinding-preview
129129
[wayfinding API]: /rest/api/maps/v20220901preview/wayfinding
130-
[how to manage access to creator services]: how-to-manage-creator.md#access-to-creator-services
131-
[check dataset creation status]: tutorial-creator-indoor-maps.md#check-the-dataset-creation-status
130+
[Access to Creator services]: how-to-manage-creator.md#access-to-creator-services
131+
[Check the dataset creation status]: tutorial-creator-indoor-maps.md#check-the-dataset-creation-status
132132
[wayfinding service]: creator-indoor-maps.md#wayfinding-preview

articles/azure-maps/how-to-dataset-geojson.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Azure Maps Creator enables users to import their indoor map data in GeoJSON form
2828

2929
>[!IMPORTANT]
3030
>
31-
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator Services](how-to-manage-creator.md#access-to-creator-services).
31+
> - This article uses the `us.atlas.microsoft.com` geographical URL. If your Creator service wasn't created in the United States, you must use a different geographical URL. For more information, see [Access to Creator services](how-to-manage-creator.md#access-to-creator-services).
3232
> - In the URL examples in this article you will need to replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
3333
3434
## Create dataset using the GeoJSON package

articles/azure-maps/how-to-dev-guide-csharp-sdk.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ dotnet add package Azure.Maps.Geolocation --prerelease
5252

5353
#### Azure Maps services
5454

55-
| Service Name  | NuGet package  | Samples  |
55+
| Service name  | NuGet package  | Samples  |
5656
|---------------|-------------------------|--------------|
5757
| [Search][search readme] | [Azure.Maps.Search][search package] | [search samples][search sample] |
5858
| [Routing][routing readme] | [Azure.Maps.Routing][routing package] | [routing samples][routing sample] |

articles/azure-maps/how-to-dev-guide-java-sdk.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ New-Item demo.java
102102
103103
### Azure Maps services
104104

105-
| Service Name  | Maven package  | Samples  |
105+
| Service name  | Maven package  | Samples  |
106106
|---------------|-------------------------|--------------|
107107
| [Search][java search readme] | [azure-maps-search][java search package] | [search samples][java search sample] |
108108
| [Routing][java routing readme] | [azure-maps-routing][java routing package] | [routing samples][java routing sample] |

0 commit comments

Comments
 (0)