Gen1 deprecation PR #4 of 4.

Author: stevemunk

articles/azure-maps/how-to-render-custom-data.md

@@ -35,8 +35,10 @@ Use the Azure Maps [Data service] to store and render overlays.
 ## Render pushpins with labels and a custom image
 
 > [!NOTE]
-> The procedure in this section requires an Azure Maps account in the Gen 1 or Gen 2 pricing tier.
-The Azure Maps account Gen 1 Standard S0 tier supports only a single instance of the `pins` parameter. It allows you to render up to five pushpins, specified in the URL request, with a custom image.
+> The procedure in this section requires an Azure Maps account in the Gen1 or Gen2 pricing tier.
+The Azure Maps account Gen1 Standard S0 tier supports only a single instance of the `pins` parameter. It allows you to render up to five pushpins, specified in the URL request, with a custom image.
+>
+> Gen1 pricing tier is now deprecated and will be retired on 9/15/26. If your Azure Maps account has Gen1 pricing tier selected, you can switch to Gen2 before it’s retired, otherwise it will automatically be updated. For more information, see [Manage the pricing tier of your Azure Maps account].
 
 ### Get static image with custom pins and labels
 
@@ -65,7 +67,7 @@ To get a static image with custom pins and labels:
 ## Upload pins and path data
 
 > [!NOTE]
-> The procedure in this section requires an Azure Maps account Gen 1 (S1) or Gen 2 pricing tier.
+> The procedure in this section requires an Azure Maps account Gen1 (S1) or Gen2 pricing tier.
 
 In this section, you upload path and pin data to Azure Map data storage.
 
@@ -215,7 +217,7 @@ To render the uploaded pins and path data on the map:
 ## Render a polygon with color and opacity
 
 > [!NOTE]
-> The procedure in this section requires an Azure Maps account Gen 1 (S1) or Gen 2 pricing tier.
+> The procedure in this section requires an Azure Maps account Gen1 (S1) or Gen2 pricing tier.
 
 You can modify the appearance of a polygon by using style modifiers with the [path parameter].
 
@@ -243,7 +245,7 @@ To render a polygon with color and opacity:
 ## Render a circle and pushpins with custom labels
 
 > [!NOTE]
-> The procedure in this section requires an Azure Maps account Gen 1 (S1) or Gen 2 pricing tier.
+> The procedure in this section requires an Azure Maps account Gen1 (S1) or Gen2 pricing tier.
 
 You can modify the appearance of the pins by adding style modifiers. For example, to make pushpins and their labels larger or smaller, use the `sc` "scale style" modifier. This modifier takes a value that's greater than zero. A value of 1 is the standard scale. Values larger than 1 makes the pins larger, and values smaller than 1 makes them smaller. For more information about style modifiers, see [static image service path parameters].
 
@@ -291,11 +293,11 @@ Similarly, you can change, add, and remove other style modifiers.
 > [!div class="nextstepaction"]
 > [Data service]
 
-
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [Render - Get Map Image]: /rest/api/maps/render/getmapimage
 [Data service]: /rest/api/maps/data
 [Data Upload]: /rest/api/maps/data-v2/upload
+[Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
 [path parameter]: /rest/api/maps/render/getmapimage#uri-parameters
 [Postman]: https://www.postman.com/
 [Render service]: /rest/api/maps/render/get-map-image

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

@@ -30,13 +30,15 @@ This video provides examples for making REST calls to Azure Maps Weather service
 
 >[!VIDEO https://learn.microsoft.com/Shows/Internet-of-Things-Show/Azure-Maps-Weather-services-for-developers/player?format=ny]
 
+</br>
+
 ## Prerequisites
 
 * An [Azure Maps account]
 * A [subscription key]
 
     >[!IMPORTANT]
-    >The [Get Minute Forecast API] requires a Gen 1 (S1) or Gen 2 pricing tier.  All other APIs require an S0 pricing tier key.
+    >The [Get Minute Forecast API] requires a Gen1 (S1) or Gen2 pricing tier.
 
 This tutorial uses the [Postman] application, but you may choose a different API development environment.
 
@@ -284,7 +286,9 @@ In this example, you use the [Get Severe Weather Alerts API] to retrieve current
 The [Get Daily Forecast API] returns detailed daily weather forecast such as temperature and wind. The request can specify how many days to return: 1, 5, 10, 15, 25, or 45 days for a given coordinate location. The response includes details such as temperature, wind, precipitation, air quality, and UV index.  In this example, we request for five days by setting `duration=5`.
 
 >[!IMPORTANT]
->In the S0 pricing tier, you can request daily forecast for the next 1, 5, 10, and 15 days. In either Gen 1 (S1) or Gen 2 pricing tier, you can request daily forecast for the next 25 days, and 45 days.
+>In the S0 pricing tier, you can request daily forecast for the next 1, 5, 10, and 15 days. In either Gen1 (S1) or Gen2 pricing tier, you can request daily forecast for the next 25 days, and 45 days.
+>
+> Gen1 pricing tier is now deprecated and will be retired on 9/15/26. If your Azure Maps account has Gen1 pricing tier selected, you can switch to Gen2 before it’s retired, otherwise it will automatically be updated. For more information, see [Manage the pricing tier of your Azure Maps account].
 
 In this example, you use the [Get Daily Forecast API] to retrieve the five-day weather forecast for coordinates located in Seattle, WA.
 
@@ -533,7 +537,7 @@ In this example, you use the [Get Daily Forecast API] to retrieve the five-day w
 The [Get Hourly Forecast API] returns detailed weather forecast by the hour for the next 1, 12, 24 (1 day), 72 (3 days), 120 (5 days), and 240 hours (10 days) for the given coordinate location. The API returns details such as temperature, humidity, wind, precipitation, and UV index.
 
 >[!IMPORTANT]
->In the S0 pricing tier, you can request hourly forecast for the next 1, 12, 24 hours (1 day), and 72 hours (3 days). In either Gen 1 (S1) or Gen 2 pricing tier, you can request hourly forecast for the next 120 (5 days) and 240 hours (10 days).
+>In the Gen1 (S0) pricing tier, you can request hourly forecast for the next 1, 12, 24 hours (1 day), and 72 hours (3 days). In either Gen1 (S1) or Gen2 pricing tier, you can request hourly forecast for the next 120 (5 days) and 240 hours (10 days).
 
 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.
 
@@ -758,6 +762,7 @@ In this example, you use the [Get Minute Forecast API] to retrieve the minute-by
 [Get Hourly Forecast API]: /rest/api/maps/weather/gethourlyforecast
 [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
 [Postman]: https://www.postman.com/
 [subscription key]: quick-demo-map-app.md#get-the-subscription-key-for-your-account
 [Weather service concepts]: weather-services-concepts.md

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

@@ -172,6 +172,12 @@ The following steps describe how to create and configure an Azure Maps account w
 
 1. Create a template file *azuredeploy.json* to provision the Azure Maps account, role assignment, and SAS token.
 
+    > [!NOTE]
+    >
+    > **Azure Maps Gen1 Price Tier Retirement**
+    >
+    > Gen1 pricing tier is now deprecated and will be retired on 9/15/26. Gen2 pricing tier replaces Gen1 (both S0 and S1) pricing tier. If your Azure Maps account has Gen1 pricing tier selected, you can switch to Gen2 pricing before it’s retired, otherwise it will automatically be updated. For more information, see [Manage the pricing tier of your Azure Maps account].
+
     ```json
     {
         "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
@@ -457,3 +463,5 @@ Find the API usage metrics for your Azure Maps account:
 Explore samples that show how to integrate Azure AD with Azure Maps:
 > [!div class="nextstepaction"]
 > [Azure Maps samples](https://github.com/Azure-Samples/Azure-Maps-AzureAD-Samples)
+
+[Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md

articles/azure-maps/migrate-from-bing-maps-web-services.md

@@ -611,9 +611,13 @@ Batch geocoding is the process of taking a large number of addresses or places,
 
 Bing Maps allows up to 200,000 addresses to be passed in a single batch geocode request. This request goes into a queue and usually processes over a period of time, anywhere from a few minutes to a few hours depending on the size of the data set and the load on the service. Each address in the request generated a transaction.
 
-Azure Maps has a batch geocoding service, however it allows up to 10,000 addresses to be passed in a single request and is processed over seconds to a few minutes depending on the size of the data set and the load on the service. Each address in the request generated a transaction. In Azure Maps, the batch geocoding service is only available the Gen 2 or S1 pricing tier. For more information on pricing tiers, see [Choose the right pricing tier in Azure Maps].
+Azure Maps has a batch geocoding service, however it allows up to 10,000 addresses to be passed in a single request and is processed over seconds to a few minutes depending on the size of the data set and the load on the service. Each address in the request generated a transaction.
 
-Another option for geocoding a large number addresses with Azure Maps is to make parallel requests to the standard search APIs. These services only accept a single address per request but can be used with the S0 tier that also provides free usage limits. The S0 tier allows up to 50 requests per second to the Azure Maps platform from a single account. So if you process limit these to stay within that limit, it's possible to geocode upwards of 180,000 address an hour. The Gen 2 or S1 pricing tier doesn’t have a documented limit on the number of queries per second that can be made from an account, so a lot more data can be processed faster when using that pricing tier, however using the batch geocoding service helps reduce the total amount of data transferred, reducing network traffic.
+Another option for geocoding a large number addresses with Azure Maps is to make parallel requests to the standard search APIs. These services only accept a single address per request but can be used with the S0 tier that also provides free usage limits. The S0 tier allows up to 50 requests per second to the Azure Maps platform from a single account. So if you process limit these to stay within that limit, it's possible to geocode upwards of 180,000 address an hour. The Gen2 or Gen1 (S1) pricing tier doesn’t have a documented limit on the number of queries per second that can be made from an account, so a lot more data can be processed faster when using that pricing tier, however using the batch geocoding service helps reduce the total amount of data transferred, reducing network traffic.
+
+> [!NOTE]
+> Gen1 pricing tier is now deprecated and will be retired on 9/15/26. Gen2 pricing tier replaces Gen1 (both S0 and S1). If your Azure Maps account has Gen1 selected, you can switch to Gen2 before it’s retired, otherwise it will automatically be updated.
+For more information on the Gen1 pricing tier retirement, see [Manage the pricing tier of your Azure Maps account].
 
 * [Free-form address geocoding]: Specify a single address string (like `"1 Microsoft way, Redmond, WA"`) and process the request immediately. This service is recommended if you need to geocode individual addresses quickly.
 * [Structured address geocoding]: Specify the parts of a single address, such as the street name, city, country/region, and postal code and process the request immediately. This service is recommended if you need to geocode individual addresses quickly and the data is already parsed into its individual address parts.
@@ -690,7 +694,6 @@ Learn more about the Azure Maps REST services.
 [Best practices for Azure Maps Route service]: how-to-use-best-practices-for-routing.md
 [Best practices for Azure Maps Search service]: how-to-use-best-practices-for-search.md
 [Calculate route]: /rest/api/maps/route/getroutedirections
-[Choose the right pricing tier in Azure Maps]: choose-pricing-tier.md
 [Cross street reverse geocoder]: /rest/api/maps/search/getsearchaddressreversecrossstreet
 [free account]: https://azure.microsoft.com/free/
 [Free-form address geocoding]: /rest/api/maps/search/getsearchaddress
@@ -699,6 +702,7 @@ Learn more about the Azure Maps REST services.
 [Geolocation API]: /rest/api/maps/geolocation/get-ip-to-location
 [Localization support in Azure Maps]: supported-languages.md
 [manage authentication in Azure Maps]: how-to-manage-authentication.md
+[Manage the pricing tier of your Azure Maps account]: how-to-manage-pricing-tier.md
 [Map image render]: /rest/api/maps/render/getmapimagerytile
 [Map imagery tile]: /rest/api/maps/render/getmapimagerytile
 [Map Tiles]: /rest/api/maps/render/getmaptile

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -63,6 +63,7 @@ The following limits apply when you use Azure Resource Manager and Azure resourc
 
 [!INCLUDE [api-center-service-limits](../../api-center/includes/api-center-service-limits.md)]
 
+
 ## API Management limits
 
 [!INCLUDE [api-management-service-limits](../../../includes/api-management-service-limits.md)]
@@ -127,8 +128,6 @@ Azure Communications Gateway also has limits on the SIP signaling.
 
 For Azure Container Apps limits, see [Quotas in Azure Container Apps](../../container-apps/quotas.md).
 
-[!INCLUDE [container-apps-limits](../../../includes/container-apps/container-apps-limits.md)]
-
 ## Azure Cosmos DB limits
 
 For Azure Cosmos DB limits, see [Limits in Azure Cosmos DB](../../cosmos-db/concepts-limits.md).