Merge branch 'main' into wi366674-2-customer-intents-azure

Author: sbreingold-ms

.openpublishing.redirection.json

@@ -6065,9 +6065,9 @@
       "redirect_document_id": false
     },
     {
-      "source_path_from_root": "/articles/reliability/reliability-postgre-flexible.md",
-      "redirect_url": "/azure/reliability/reliability-postgresql-flexible-server",
-      "redirect_document_id": false
+      "source_path_from_root": "/articles/reliability/reliability-postgresql-flexible-server.md",
+      "redirect_url": "/azure/reliability/reliability-azure-database-postgresql",
+      "redirect_document_id": true
     },
     {
       "source_path_from_root": "/articles/remote-rendering/tutorials/unity/changing-environment-and-materials.md",

articles/api-center/includes/api-center-portal-user-sign-in.md

@@ -16,7 +16,7 @@ To enable sign-in to the API Center portal to access APIs, assign the **Azure AP
 > [!IMPORTANT]
 > By default, you and other administrators of the API center must sign-in to access APIs in the API Center portal. Be sure to assign the **Azure API Center Data Reader** role to yourself and other administrators.  
 
-For detailed prerequisites and steps to assign a role to users and groups, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml). Brief steps follow:
+For detailed prerequisites and steps to assign a role to users and groups, see [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal). Brief steps follow:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
 1. In the left menu, select **Access control (IAM)** > **+ Add role assignment**.

articles/azure-functions/functions-add-output-binding-cosmos-db-vs-code.md

@@ -199,7 +199,7 @@ app = func.FunctionApp()
 @app.function_name(name="HttpTrigger1")
 @app.route(route="hello", auth_level=func.AuthLevel.ANONYMOUS)
 @app.queue_output(arg_name="msg", queue_name="outqueue", connection="AzureWebJobsStorage")
-@app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", container_name="my-container", connection="CosmosDbConnectionSetting")
+@app.cosmos_db_output(arg_name="outputDocument", database_name="my-database", container_name="my-container", connection="CosmosDbConnectionString")
 def test_function(req: func.HttpRequest, msg: func.Out[func.QueueMessage],
     outputDocument: func.Out[func.Document]) -> func.HttpResponse:
      logging.info('Python HTTP trigger function processed a request.')

articles/azure-functions/functions-bindings-mcp.md

@@ -93,7 +93,7 @@ To connect to the MCP server exposed by your function app, you need to provide a
 
 <sup>1</sup> Newer protocol versions deprecated the Server-Sent Events transport. Unless your client specifically requires it, you should use the Streamable HTTP transport instead.
 
-When hosted in Azure, the endpoints exposed by the extension also require the [system key](./function-keys-how-to.md) named `mcp_extension`. If it isn't provided in the `x-functions-key` HTTP header, your client receives a `401 Unauthorized` response. You can retrieve the key using any of the methods described in [Get your function access keys](./function-keys-how-to.md#get-your-function-access-keys). The following example shows how to get the key with the Azure CLI:
+When hosted in Azure, the endpoints exposed by the extension also require the [system key](./function-keys-how-to.md) named `mcp_extension`. If it isn't provided in the `x-functions-key` HTTP header or in the `code` query string parameter, your client receives a `401 Unauthorized` response. You can retrieve the key using any of the methods described in [Get your function access keys](./function-keys-how-to.md#get-your-function-access-keys). The following example shows how to get the key with the Azure CLI:
 
 ```azurecli
 az functionapp keys list --resource-group <RESOURCE_GROUP> --name <APP_NAME> --query systemKeys.mcp_extension --output tsv

articles/azure-maps/about-azure-maps.md

@@ -180,7 +180,7 @@ Azure Maps uses a key-based authentication scheme. When you create your account,
 Azure Maps services are currently available except in the following countries/regions:
 
 * China
-* South Korea
+* Korea
 
 Verify that the location of your current IP address is in a supported country/region.
 

articles/azure-maps/autocomplete-coverage.md

@@ -132,6 +132,7 @@ The following table shows which countries/regions support Azure Maps search auto
 | Kazakhstan                                         | ✓        | ✓      |
 | Kenya                                              |          | ✓      |
 | Kiribati                                           |          | ✓      |
+| Korea                                              |          | ✓      |
 | Kuwait                                             | ✓        | ✓      |
 | Kyrgyzstan                                         |          | ✓      |
 | Laos                                               |          | ✓      |
@@ -221,7 +222,6 @@ The following table shows which countries/regions support Azure Maps search auto
 | Somalia                                            |          | ✓      |
 | South Africa                                       | ✓        | ✓      |
 | South Georgia and the South Sandwich Islands       |          | ✓      |
-| South Korea                                        |          | ✓      |
 | South Sudan                                        |          | ✓      |
 | Spain                                              | ✓        | ✓      |
 | Sri Lanka                                          | ✓        | ✓      |
@@ -381,6 +381,7 @@ The following table shows which countries/regions support Azure Maps search auto
 | Kazakhstan                                        | 103,642       | 877,700     | 981,342     |
 | Kenya                                             | 0             | 17,054      | 17,054      |
 | Kiribati                                          | 0             | 356         | 356         |
+| Korea                                             | 0             | 7,228       | 7,228       |
 | Kuwait                                            | 17,602        | 1,332       | 18,934      |
 | Kyrgyzstan                                        | 0             | 7,204       | 7,204       |
 | Laos                                              | 0             | 10,077      | 10,077      |
@@ -470,7 +471,6 @@ The following table shows which countries/regions support Azure Maps search auto
 | Somalia                                           | 0             | 10,268      | 10,268      |
 | South Africa                                      | 213,154       | 62,426      | 275,580     |
 | South Georgia and the South Sandwich Islands      | 0             | 906         | 906         |
-| South Korea                                       | 0             | 7,228       | 7,228       |
 | South Sudan                                       | 0             | 1,873       | 1,873       |
 | Spain                                             | 1,188,521     | 112,615     | 1,301,136   |
 | Sri Lanka                                         | 1,963         | 13,237      | 15,200      |

articles/azure-maps/consent-management.md

@@ -13,17 +13,17 @@ ms.subservice: manage-account
 
 Azure Maps is a global service that is available worldwide. When creating your Azure Maps account, you select a _Region_. The Region selection is the accounts geographic scope, which allows you to limit data residency to the selected region. All requests (including input data) are processed and stored exclusively in the specified geographic area (region).
 
-In some cases, you will need to enable your search requests to be processed in a region or geography other than the one your Azure Maps Account is in. For example, due to local data residency laws, all South Korean addresses must be processed in South Korea, which is the _Korea Central_ region in Azure Maps. To do this, you must give Azure Maps consent to process your data in the _Korea Central_ region. For more information on how to give Azure Maps consent to process data in a different region, see [Configure global data processing].
+In some cases, you will need to enable your search requests to be processed in a region or geography other than the one your Azure Maps Account is in. For example, due to local data residency laws, all Korean addresses must be processed in Korea, which is the _Korea Central_ region in Azure Maps. To do this, you must give Azure Maps consent to process your data in the _Korea Central_ region. For more information on how to give Azure Maps consent to process data in a different region, see [Configure global data processing].
 
 For more information on geographic scope in Azure Maps, see [Azure Maps service geographic scope].
 
 ## Frequently asked questions
 
-**My scenario doesn't have any South Korea data. Do I still need to enable cross region processing to use Azure Maps?**
+**My scenario doesn't have any Korean data. Do I still need to enable cross region processing to use Azure Maps?**
 
-No, if your scenario doesn't require South Korea data, you don't need to enable cross region processing. This is a specific regional requirement due to data residency laws.
+No, if your scenario doesn't require Korean data, you don't need to enable cross region processing. This is a specific regional requirement due to data residency laws.
 
-**Where will my data be stored if I enable cross region processing in South Korea?**
+**Where will my data be stored if I enable cross region processing in Korea?**
 
 Giving consent to process data in a different region will not affect where your metadata and logs are stored. Those are still contained within the region specified when creating your Azure Maps Account.
 

articles/azure-maps/geocoding-coverage.md

@@ -110,6 +110,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Indonesia                                           |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Japan                                               |                 |                |              |      ✓     |       ✓        |
 | Kiribati                                            |                 |                |              |      ✓     |       ✓        |
+| Korea<sup>1</sup>                                   |                 |                |              |      ✓     |       ✓        |
 | Laos                                                |        ✓        |                |       ✓     |      ✓     |       ✓        |
 | Macao SAR                                           |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Malaysia                                            |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
@@ -133,7 +134,6 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Samoa                                               |                 |                |              |      ✓     |       ✓        |
 | Singapore                                           |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Solomon Islands                                     |                 |                |              |      ✓     |       ✓        |
-| South Korea<sup>1</sup>                             |                 |                |              |      ✓     |       ✓        |
 | Sri Lanka                                           |                 |                |              |      ✓     |       ✓        |
 | Taiwan                                              |        ✓        |        ✓      |       ✓      |      ✓     |       ✓        |
 | Thailand                                            |        ✓        |                |       ✓     |      ✓     |       ✓        |
@@ -146,7 +146,7 @@ The ability to geocode in a country/region is dependent upon the road data cover
 | Vietnam                                             |        ✓        |                |       ✓     |      ✓     |       ✓        |
 | Wallis & Futuna                                     |                 |                |              |      ✓     |       ✓        |
 
-<sup>1</sup> Coverage is dependent on enabling data processing in South Korea. For more information, see [Configure global data processing](how-to-manage-consent.md).
+<sup>1</sup> Coverage is dependent on enabling data processing in Korea. For more information, see [Configure global data processing](how-to-manage-consent.md).
 
 ## Europe
 

articles/azure-maps/how-to-manage-consent.md

@@ -16,7 +16,7 @@ In some cases, it may be necessary to process requests in a region different fro
 This article guides you on configuring global data processing settings to comply with data residency laws using multiple approaches including the [Azure Portal](#configure-global-data-processing-in-the-azure-portal), [REST APIs](#configure-global-data-processing-using-rest-api) or an [ARM deployment template](#configure-global-data-processing-using-an-arm-deployment-template). This allows Azure Maps to process address requests within the specified country's region, regardless of your Azure Maps Account's region.
 
 > [!IMPORTANT]
-> If your scenarios don't involve South Korea data, there is no need to enable cross-region processing. This requirement is specific to South Korea due to its data residency laws.
+> If your scenarios don't involve Korean data, there is no need to enable cross-region processing. This requirement is specific to Korea due to its data residency laws.
 
 ## Configure global data processing in the Azure portal
 

articles/azure-maps/migrate-find-location-address.md

@@ -26,7 +26,7 @@ This article explains how to migrate the Bing Maps [Find a Location by Address]
 - Bing Maps Find a Location by Address API returns coordinates in latitude/longitude format, while Azure Maps Get Geocoding API returns coordinates in longitude/latitude format, as defined by the [GeoJSON] format.
 - Bing Maps Find a Location by Address API supports XML and JSON response format. Azure Maps Get Geocoding API supports GeoJSON.
 - Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API has a `view` input parameter, which is a string that represents an [ISO 3166-1 Alpha-2 region/country code]. The `view` input parameter alters geopolitical disputed borders and labels to align with the specified user region. For more information, see [URI Parameters].
-- Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API doesn’t currently support address geocoding for China, Japan, or South Korea.  
+- Unlike Bing Maps Find a Location by Address API, Azure Maps Get Geocoding API doesn’t currently support address geocoding in China.  
 - Unlike Bing Maps for Enterprise, Azure Maps is a global service that supports specifying a geographic scope, allowing limits to data residency to the European (EU) or United States (US) geographic areas (geos). All requests (including input data) are processed exclusively in the specified geographic area. For more information, see [geographic scope].
 
 ## Security and authentication