Update broken link to Azure region locations API (#2845)

Author: lmolkova

docs/database/cosmosdb.md

@@ -195,7 +195,7 @@ additional values when introducing new operations.
 
 **[2] `azure.cosmosdb.connection.mode`:** if not `gateway` (the default value is assumed to be `gateway`).
 
-**[3] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/subscription/subscriptions/list-locations?view=rest-subscription-2021-10-01&tabs=HTTP#location)
+**[3] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations)
 
 **[4] `db.collection.name`:** It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
 
@@ -400,7 +400,7 @@ Instrumentations SHOULD document how `error.type` is populated.
 
 **[7] `server.port`:** If using a port other than the default port for this DBMS and if `server.address` is set.
 
-**[8] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/subscription/subscriptions/list-locations?view=rest-subscription-2021-10-01&tabs=HTTP#location)
+**[8] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations)
 
 **[9] `server.address`:** When observed from the client side, and when communicating through an intermediary, `server.address` SHOULD represent the server address behind any intermediaries, for example proxies, if it's available.
 

docs/registry/attributes/azure.md

@@ -30,7 +30,7 @@ This section defines attributes for Azure Cosmos DB.
 | <a id="azure-cosmosdb-request-body-size" href="#azure-cosmosdb-request-body-size">`azure.cosmosdb.request.body.size`</a> | int | Request payload size in bytes. |  | ![Development](https://img.shields.io/badge/-development-blue) |
 | <a id="azure-cosmosdb-response-sub-status-code" href="#azure-cosmosdb-response-sub-status-code">`azure.cosmosdb.response.sub_status_code`</a> | int | Cosmos DB sub status code. | `1000`; `1002` | ![Development](https://img.shields.io/badge/-development-blue) |
 
-**[1] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/subscription/subscriptions/list-locations?view=rest-subscription-2021-10-01&tabs=HTTP#location)
+**[1] `azure.cosmosdb.operation.contacted_regions`:** Region name matches the format of `displayName` in [Azure Location API](https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations)
 
 ---
 

model/azure/registry.yaml

@@ -61,7 +61,7 @@ groups:
           it indicates that the operation was performed on multiple regions i.e. cross-regional call.
         note: >
           Region name matches the format of `displayName`
-          in [Azure Location API](https://learn.microsoft.com/rest/api/subscription/subscriptions/list-locations?view=rest-subscription-2021-10-01&tabs=HTTP#location)
+          in [Azure Location API](https://learn.microsoft.com/rest/api/resources/subscriptions/list-locations)
         examples:
           - ["North Central US", "Australia East", "Australia Southeast"]
       - id: azure.cosmosdb.response.sub_status_code