various

Author: stevemunk

articles/azure-maps/how-to-request-weather-data.md

@@ -41,15 +41,15 @@ This video provides examples for making REST calls to Azure Maps Weather service
 >
 > In the URL examples in this article you will need to replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
 
-This tutorial uses the [bruno] application, but you can choose a different API development environment.
+This tutorial uses the [Bruno] application, but you can choose a different API development environment.
 
 ## Request real-time weather data
 
 The [Get Current Conditions API] returns detailed weather conditions such as precipitation, temperature, and wind for a given coordinate location. Also, observations from the past 6 or 24 hours for a particular location can be retrieved. The response includes details like observation date and time, description of weather conditions, weather icon, precipitation indicator flags, and temperature. RealFeel™ Temperature and ultraviolet(UV) index are also returned.
 
 In this example, you use the [Get Current Conditions API] to retrieve current weather conditions at coordinates located in Seattle, WA.
 
-1. Open the bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
+1. Open the Bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
 
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
@@ -61,7 +61,7 @@ In this example, you use the [Get Current Conditions API] to retrieve current we
 
 1. Select the run button.
 
-   :::image type="content" source="./media/weather-service/bruno-run.png" alt-text="A screenshot showing the Request real-time weather data URL with the run button highlighted in the bruno app.":::
+   :::image type="content" source="./media/weather-service/bruno-run.png" alt-text="A screenshot showing the Request real-time weather data URL with the run button highlighted in the Bruno app.":::
 
    The response body contains current weather information.
 
@@ -245,7 +245,7 @@ In this example, you use the [Get Severe Weather Alerts API] to retrieve current
 > [!NOTE]
 > This example retrieves severe weather alerts at the time of this writing. It is likely that there are no longer any severe weather alerts at the requested location. To retrieve actual severe alert data when running this example, you'll need to retrieve data at a different coordinate location.
 
-1. In the bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
+1. In the Bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
 
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
@@ -257,7 +257,7 @@ In this example, you use the [Get Severe Weather Alerts API] to retrieve current
 
 1. Select the run button.
 
-   :::image type="content" source="./media/weather-service/bruno-run-request-severe-weather-alerts.png" alt-text="A screenshot showing the Request severe weather alerts URL with the run button highlighted in the bruno app.":::
+   :::image type="content" source="./media/weather-service/bruno-run-request-severe-weather-alerts.png" alt-text="A screenshot showing the Request severe weather alerts URL with the run button highlighted in the Bruno app.":::
 
     If there are no severe weather alerts, the response body contains an empty `results[]` array. If there are severe weather alerts, the response body contains something like the following JSON response:
 
@@ -307,7 +307,7 @@ The [Get Daily Forecast API] returns detailed daily weather forecast such as tem
 
 In this example, you use the [Get Daily Forecast API] to retrieve the five-day weather forecast for coordinates located in Seattle, WA.
 
-1. In the bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
+1. In the Bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
 
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
@@ -319,7 +319,7 @@ In this example, you use the [Get Daily Forecast API] to retrieve the five-day w
 
 1. Select the run button.
 
-   :::image type="content" source="./media/weather-service/bruno-run-request-daily-weather-forecast-data.png" alt-text="A screenshot showing the Request daily weather forecast data URL with the run button highlighted in the bruno app.":::
+   :::image type="content" source="./media/weather-service/bruno-run-request-daily-weather-forecast-data.png" alt-text="A screenshot showing the Request daily weather forecast data URL with the run button highlighted in the Bruno app.":::
 
     The response body contains the five-day weather forecast data. For the sake of brevity, the following JSON response shows the forecast for the first day.
 
@@ -558,7 +558,7 @@ The [Get Hourly Forecast API] returns detailed weather forecast by the hour for
 
 In this example, you use the [Get Hourly Forecast API] to retrieve the hourly weather forecast for the next 12 hours at coordinates located in Seattle, WA.
 
-1. In the bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
+1. In the Bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
 
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
@@ -570,7 +570,7 @@ In this example, you use the [Get Hourly Forecast API] to retrieve the hourly we
 
 1. Select the run button.
 
-   :::image type="content" source="./media/weather-service/bruno-run-request-hourly-weather-forecast-data.png" alt-text="A screenshot showing the Request hourly weather forecast data URL with the run button highlighted in the bruno app.":::
+   :::image type="content" source="./media/weather-service/bruno-run-request-hourly-weather-forecast-data.png" alt-text="A screenshot showing the Request hourly weather forecast data URL with the run button highlighted in the Bruno app.":::
 
     The response body contains weather forecast data for the next 12 hours. The following example JSON response only shows the first hour:
 
@@ -670,7 +670,7 @@ In this example, you use the [Get Hourly Forecast API] to retrieve the hourly we
 
 In this example, you use the [Get Minute Forecast API] to retrieve the minute-by-minute weather forecast at coordinates located in Seattle, WA. The weather forecast is given for the next 120 minutes. Our query requests that the forecast is given at 15-minute intervals, but you can adjust the parameter to be either 1 or 5 minutes.
 
-1. In the bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
+1. In the Bruno app, select **NEW REQUEST** to create the request. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request.
 
 1. Select the **GET** HTTP method in the **URL** drop-down list, then enter the following URL:
 
@@ -682,7 +682,7 @@ In this example, you use the [Get Minute Forecast API] to retrieve the minute-by
 
 1. Select the run button.
 
-   :::image type="content" source="./media/weather-service/bruno-run-request-minute-by-minute-weather-forecast-data.png" alt-text="A screenshot showing the Request minute-by-minute weather forecast data URL with the run button highlighted in the bruno app.":::
+   :::image type="content" source="./media/weather-service/bruno-run-request-minute-by-minute-weather-forecast-data.png" alt-text="A screenshot showing the Request minute-by-minute weather forecast data URL with the run button highlighted in the Bruno app.":::
 
     The response body contains weather forecast data for the next 120 minutes, in 15-minute intervals.
 
@@ -790,7 +790,7 @@ In this example, you use the [Get Minute Forecast API] to retrieve the minute-by
 [Get Minute Forecast API]: /rest/api/maps/weather/getminuteforecast
 [Get Severe Weather Alerts API]: /rest/api/maps/weather/getsevereweatheralerts
 [Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
-[bruno]: https://www.usebruno.com/
+[Bruno]: https://www.usebruno.com/
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [Weather service concepts]: weather-services-concepts.md
 [Weather service]: /rest/api/maps/weather

articles/azure-maps/how-to-search-for-address.md

@@ -394,7 +394,7 @@ This example demonstrates how to search for a cross street based on the coordina
 [point of interest]: /rest/api/maps/search/getsearchpoi?view=rest-maps-1.0&preserve-view=true#searchpoiresponse
 [Post Search Address Batch]: /rest/api/maps/search/postsearchaddressbatch
 [Post Search Address Reverse Batch]: /rest/api/maps/search/postsearchaddressreversebatch?view=rest-maps-1.0&preserve-view=true
-[bruno]: https://www.usebruno.com/
+[Bruno]: https://www.usebruno.com/
 [Reverse Address Search Results]: /rest/api/maps/search/getsearchaddressreverse?view=rest-maps-1.0&preserve-view=true#searchaddressreverseresult
 [Reverse Address Search]: /rest/api/maps/search/getsearchaddressreverse?view=rest-maps-1.0&preserve-view=true
 [Reverse Search Parameters]: /rest/api/maps/search/getsearchaddressreverse?view=rest-maps-1.0&preserve-view=true#uri-parameters

articles/azure-maps/how-to-secure-daemon-app.md

@@ -202,9 +202,9 @@ To acquire the access token:
 
       :::image type="content" border="true" source="./media/how-to-manage-authentication/get-token-params.png" alt-text="Copy token parameters.":::
 
-This article uses the [bruno](https://www.usebruno.com/) application to create the token request, but you can use a different API development environment.
+This article uses the [Bruno](https://www.usebruno.com/) application to create the token request, but you can use a different API development environment.
 
-1. Open the bruno app, select **NEW REQUEST** to create the request.
+1. Open the Bruno app, select **NEW REQUEST** to create the request.
 
 1. In the **NEW REQUEST** window, set **Type** to **HTTP**. Enter a **Name** for the request, such as *POST Token Request*.
 

articles/azure-maps/how-to-secure-sas-app.md

@@ -412,7 +412,7 @@ az rest --method GET --url 'https://us.atlas.microsoft.com/search/address/json?a
 
 ## Real-world example
 
-You can run requests to Azure Maps APIs from most clients, like C#, Java, or JavaScript. API development platforms like [bruno](https://www.usebruno.com) or [Postman](https://learning.postman.com/docs/sending-requests/generate-code-snippets) can convert an API request into a basic client code snippet in almost any programming language or framework you choose. You can use the generated code snippets in your front-end applications.
+You can run requests to Azure Maps APIs from most clients, like C#, Java, or JavaScript. API development platforms like [Bruno](https://www.usebruno.com) or [Postman](https://learning.postman.com/docs/sending-requests/generate-code-snippets) can convert an API request into a basic client code snippet in almost any programming language or framework you choose. You can use the generated code snippets in your front-end applications.
 
 The following small JavaScript code example shows how you could use your SAS token with the JavaScript [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#supplying_request_options) to get and return Azure Maps information. The example uses [Get Search Address](/rest/api/maps/search/get-search-address) API version 1.0. Supply your own value for `<your SAS token>`.
 

articles/azure-maps/how-to-use-best-practices-for-routing.md

@@ -30,7 +30,7 @@ The Route Directions and Route Matrix APIs in Azure Maps [Route service] can be
 
 For more information about the coverage of the Route service, see [Routing Coverage].
 
-You can use any API development environment such as [Postman] or [bruno] to run the HTTP request samples shown in this article or to build REST calls.
+You can use any API development environment such as [Postman] or [Bruno] to run the HTTP request samples shown in this article or to build REST calls.
 
 ## Choose between Route Directions and Matrix Routing
 
@@ -289,7 +289,7 @@ To learn more, please see:
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [Azure Maps npm Package]: https://www.npmjs.com/package/azure-maps-rest
 [Azure Maps Route service]: /rest/api/maps/route
-[bruno]: https://www.usebruno.com/
+[Bruno]: https://www.usebruno.com/
 [How to use the Service module]: how-to-use-services-module.md
 [Point of Interest]: /rest/api/maps/search/getsearchpoi?view=rest-maps-1.0&preserve-view=true
 [Post Route Directions API documentation]: /rest/api/maps/route/postroutedirections#supportingpoints

articles/azure-maps/how-to-use-best-practices-for-search.md

@@ -30,7 +30,7 @@ This article explains how to apply sound practices when you call data from Azure
 * An [Azure Maps account]
 * A [subscription key]
 
-You can use any API development environment such as [bruno] to run the HTTP request samples shown in this article or to build REST calls.
+You can use any API development environment such as [Bruno] to run the HTTP request samples shown in this article or to build REST calls.
 
 ## Best practices to geocode addresses
 
@@ -984,21 +984,21 @@ The Azure Maps [Search service] provides REST APIs for forward geocoding, revers
 * An [Azure Maps account]
 * A [subscription key]
 
-You can use any API development environment such as [bruno] to run the HTTP request samples shown in this article or to build REST calls.
+You can use any API development environment such as [Bruno] to run the HTTP request samples shown in this article or to build REST calls.
 
 ## Core Search concepts
 
 ### Task‑specific operations
 
-Each Search capability is exposed through a dedicated API, such as Get Geocoding, Get Geocode Autocomplete, or Get Reverse Geocoding. This separation improves clarity, performance, and intent alignment.
+Each Search capability is exposed through a dedicated API, such as [Get Geocoding], [Get Geocode Autocomplete], or [Get Reverse Geocoding]. This separation improves clarity, performance, and intent alignment.
 
 ### Geographic relevance signals
 
 Most Search APIs accept geographic biasing inputs such as coordinates, bounding boxes, or country/region filters. These signals strongly influence ranking and result quality.
 
 ### Batch processing
 
-Batch APIs allow multiple queries in a single request for large‑scale or background workloads.
+Batch APIs allow multiple queries in a single request for large‑scale workloads.
 
 ## Best practices for forward geocoding
 
@@ -1007,9 +1007,8 @@ Use [Get Geocoding] when converting an address or place name into geographic coo
 Recommendations:
 
 * Provide the most complete address string available.
-* Use countryRegion to reduce ambiguity.
+* Use `countryRegion` to reduce ambiguity.
 * Limit results with top when only the best match is needed.
-* Cache stable results to reduce repeated requests.
 
 ### Forward geocoding example request
 
@@ -1019,14 +1018,15 @@ GET https://atlas.microsoft.com/geocode
   &query=1%20Microsoft%20Way%2C%20Redmond%20WA
   &countryRegion=US
   &top=1
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 ## Best practices for autocomplete
 
 Use [Get Geocode Autocomplete] for interactive user input scenarios.
 Recommendations:
 
-* Trigger requests only after several characters of input.
+* Trigger autocomplete requests after three or more characters have been entered.
 * Always supply either `coordinates` or `bbox`.
 * Restrict results using `resultTypeGroups` or `resultTypes`.
 
@@ -1037,6 +1037,7 @@ GET https://atlas.microsoft.com/geocode:autocomplete
   ?api-version=2026-01-01
   &query=1%20Micro
   &coordinates=-122.129,47.639
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 ## Best practices for reverse geocoding
@@ -1045,15 +1046,18 @@ Use [Get Reverse Geocoding] to translate coordinates into a human‑readable add
 
 Recommendations:
 
-* Prefer batch reverse geocoding for telemetry or asset tracking.
-* Avoid repeated calls for static coordinates.
+* Prefer batch reverse geocoding for telemetry, tracking, or other high‑volume workloads.
+* Cache results and avoid repeated calls for coordinates that do not change.
+* Validate coordinate order and precision to ensure accurate and consistent results.
+* Expect approximate or partial addresses in some locations and handle these cases gracefully.
 
 ### Reverse geocoding example request
 
 ```rest
 GET https://atlas.microsoft.com/reverseGeocode
   ?api-version=2026-01-01
   &coordinates=-122.129,47.639
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 ## Best practices for batch operations
@@ -1064,12 +1068,14 @@ When to use:
 
 * Importing address lists
 * Background enrichment jobs
-* Large‑scale reverse geocoding
+* Large‑scale data processing
 
 ### Get Geocoding Batch example request
 
 ```rest
-POST https://atlas.microsoft.com/geocode:batch?api-version=2026-01-01&subscription-key={Your-Azure-Maps-Key}
+POST https://atlas.microsoft.com/geocode:batch
+  ?api-version=2026-01-01
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 Include the following in the body of the request:
@@ -1088,7 +1094,9 @@ For more information, see [Get Geocoding Batch].
 ### Get Reverse Geocoding Batch example request
 
 ```rest
-POST https://atlas.microsoft.com/reverseGeocode:batch?api-version=2026-01-01&subscription-key={Your-Azure-Maps-Key}
+POST https://atlas.microsoft.com/reverseGeocode:batch
+  ?api-version=2026-01-01
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 Include the following in the body of the request:
@@ -1112,14 +1120,16 @@ Use [Get Polygon] to retrieve administrative boundary geometry.
 Recommendations:
 
 * Use only when boundary geometry is required.
-* Cache responses aggressively.
+* Choose a geometry resolution that matches your application's needs. Use `resolution=small` to return a more manageable polygon size, and avoid `resolution=huge` unless you explicitly require highly detailed geometry, as it can produce very large responses.
 
 ### Administrative boundaries example request
 
 ```rest
 GET https://atlas.microsoft.com/polygon
   ?api-version=2026-01-01
   &entityId=US-WA
+  &resolution=small
+  &subscription-key={Your-Azure-Maps-Key}
 ```
 
 ## Next steps
@@ -1128,12 +1138,12 @@ GET https://atlas.microsoft.com/polygon
 > [Search service API documentation](/rest/api/maps/search)
 
 > [!div class="nextstepaction"]
-> [Search service API documentation](migrate-search-v1-api.md)
+> [Migrate Azure Maps Search 1.0 APIs](migrate-search-v1-api.md)
 :::zone-end
 
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [Azure Maps supported languages]: supported-languages.md
-[bruno]: https://www.usebruno.com/
+[Bruno]: https://www.usebruno.com/
 <!--------------------------------------------------------------------------------------------------->
 [Geocoding coverage]: geocoding-coverage.md
 [Get Search Address]: /rest/api/maps/search/getsearchaddress?view=rest-maps-1.0&preserve-view=true