Merge pull request #307173 from MicrosoftDocs/main

Auto Publish – main to live - 2025-10-21 17:00 UTC

Author: learn-build-service-prod[bot]

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/power-bi-visual-conversion.md

@@ -14,11 +14,22 @@ ms.subservice: power-bi-visual
 
 The Azure Maps visual is now Generally Available, providing a streamlined and intuitive experience for working with your data.
 
+> [!IMPORTANT]
+> The **Bing Maps** visual is scheduled for deprecation, although the timeline hasn't yet been determined. Any Bing Maps visuals that are already included in your reports remain available.
+>
+> To ensure a smooth transition, upgrade to Azure Maps unless one of the following applies:
+>
+> * You have team members who need to access the report in China, Korea, or within government cloud environments.
+> * You're physically located in China or Korea, regardless of your home tenant's location.
+> * You're part of a government cloud, irrespective of your home tenant's location.
+>
+> We're actively working to expand Azure Maps support to currently unsupported regions. **If you and all report users are located within a supported region, we encourage you to begin using Azure Maps now**. This article provides guidance on how to transition to Azure Maps. For a list of supported regions, see [Azure Maps service geographic scope](geographic-scope.md).
+
 ## How to convert your existing Map and Filled map visuals
 
 A conversion function is available in Power BI desktop to convert any existing Map and Filled map visuals to the new Azure Maps visual.
 
-When opening a report with Map and Filled map visuals, you'll see the following dialog giving you the option to upgrade to the new Azure Maps visual:
+When opening a report with Map and Filled map visuals, you see the following dialog giving you the option to upgrade to the new Azure Maps visual:
 
 :::image type="content" source="media/power-bi-visual/introducing-azure-map-visual.png" alt-text="Screenshot showing the option to upgrade maps to the Azure Maps visual.":::
 

articles/communication-services/resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/includes/server-code-subcode.md

@@ -31,7 +31,7 @@ ms.subservice: calling
 | 10004 | 487 | Call was canceled on timeout, no callee endpoint accepted on time. Ensure that user saw the notification and try to initiate that call again. | ExpectedError | |
 | 10024 | 487 | Call ended successfully as it was declined by all callee endpoint. | Success | - Try to place the call again. |
 | 301005 | 410 | Participant was removed from the call by the Azure Communication Services infrastructure due to loss of media connectivity with Azure Communication Services infrastructure, this usually happens if participant leaves the call abruptly or looses network connectivity. If participant wants to continue the call, it should reconnect. | UnexpectedClientError | - Ensure that you're using the latest SDK in a supported environment.<br> |
-| 510403 | 403 | Call ended, as it has been marked as a spam and got blocked. | ExpectedError | - Ensure that your Communication Services token is valid and not expired.<br>  - Ensure to pass in AlternateId in the call options.<br> |
+| 510403 | 403 | Call blocked:<br/> - No matching voice route found for the dialed number.<br/> - Alternate ID not supplied for the call.<br/> - Phone number not allowed by user's Session Border Controller (SBC).<br/> - Previously marked as spam and now blocked. | ExpectedError | For more information about Alternate ID, see [Manage calls](../../../../../how-tos/calling-sdk/manage-calls.md#place-a-call).<br/> - Confirm that you have a valid Voice Route for the dialed number.<br/> - Make sure that you specified a valid Alternate ID. It must be a phone number that belongs to the Resource you're using.<br/> - Verify that you own the Resource you're using to make a call.<br/> - For direct routing calls, verify why your Session Border Controller disallowed the call.<br/> - Ensure that your Communication Services token is valid and not expired. |
 | 540487 | 487 | Call ended successfully as caller canceled the call. | Success | |
 | 560000 | 0 | Call ended successfully by remote PSTN participant. | Success |Possible causes:<br> - User ended the call.<br> - Call was ended by media agent.<br> |
 | 560486 | 486 | Call ended because remote PSTN participant was busy. The number called was already in a call or having technical issues. | Success | - For Direct Routing calls, check your Session Border Control logs and settings and timeouts configuration.<br> Possible causes: <br>  - The number called was already in a call or having technical issues.<br> |

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/call-end.md

@@ -71,7 +71,7 @@ There are different explanations for why a call ended. Here are the meanings of
 | 301004 | 410 | Participant was removed from the call by the Azure Communication Services infrastructure due to inability to establish media connectivity with Azure Communication Services infrastructure during call setup. Check user's network configuration, including local network, firewalls, VPNs configuration and try again. | UnexpectedClientError | Ensure that user's network is configured correctly, follow 'Network Recommendations' public documentation. |
 | 301005 | 410 | Participant removed from the call by the Azure Communication Services infrastructure due to loss of media connectivity with the same infrastructure. This usually happens if participant leaves the call abruptly or loses network connectivity. If the participant wants to continue the call, they can reconnect. | UnexpectedClientError | Ensure that you're using the latest SDK in a supported environment. |
 | 540000 | 0 | Call ended successfully by local PSTN caller. | Success | |
-| 510403 | 403 | Call ended, previously marked as a spam and now blocked. | ExpectedError | - Ensure that your Communication Services token is valid and not expired. <br />  - Ensure to pass in `AlternateId` in the call options. |
+| 510403 | 403 | Call blocked:<br/> - No matching voice route found for the dialed number.<br/> - Alternate ID not supplied for the call.<br/> - Phone number not allowed by users Session Border Controller (SBC).<br/> - Previously markes as spam and now blocked. | ExpectedError | For more information about Alternate ID, see [Manage calls](../../../../../how-tos/calling-sdk/manage-calls.md#place-a-call).<br/> - Confirm that you have a valid Voice Route for the dialed number.<br/> - Make sure that you specified a valid Alternate ID. It must be a phone number that belongs to the Resource you're using.<br/> - Verify that you own the Resource you're using to make a call.<br/> - For direct routing calls, verify why your Session Border Controller disallowed the call.<br/> - Ensure that your Communication Services token is valid and not expired. |
 | 540487 | 487 | Call ended successfully as caller canceled the call. | Success | |
 | 560000 | 0 | Call ended successfully by remote PSTN participant. | Success |Possible causes: <br /> - User ended the call. <br /> - Call ended by media agent. |
 | 560486 | 486 | Call ended because remote PSTN participant was busy. The number called was already in a call or having technical issues. | Success | - For Direct Routing calls, check your Session Border Control logs and settings and timeouts configuration. Possible causes: The number called was already in a call or having technical issues. |

articles/communication-services/resources/troubleshooting/voice-video-calling/includes/codes/pstn.md

@@ -40,7 +40,7 @@ Response `ParticipantEndReason` with value 4xx means that the call didn't connec
 
 | SubCode | Code | Message | Result Categories | Advice |
 |--- |--- |--- |--- |--- |
-| 510403 | 403 | Call blocked:<br/> - Alternate ID not supplied for the call.<br/> - Phone number not allowed by users Session Border Controller (SBC). |  | - For more information about Alternate ID, see [Manage calls](../../../../../how-tos/calling-sdk/manage-calls.md#place-a-call).<br/> - Make sure that you specified a valid Alternate ID. It must be a phone number that belongs to the Resource you're using.<br/> - Verify that you own the Resource you're using to make a call.<br/> - For direct routing calls, verify why your Session Border Controller disallowed the call. |
+| 510403 | 403 | Call blocked:<br/> - No matching voice route found for the dialed number.<br/> - Alternate ID not supplied for the call.<br/> - Phone number not allowed by user's Session Border Controller (SBC).<br/> - Previously marked as spam and now blocked. |  | For more information about Alternate ID, see [Manage calls](../../../../../how-tos/calling-sdk/manage-calls.md#place-a-call).<br/> - Confirm that you have a valid Voice Route for the dialed number.<br/> - Make sure that you specified a valid Alternate ID. It must be a phone number that belongs to the Resource you're using.<br/> - Verify that you own the Resource you're using to make a call.<br/> - For direct routing calls, verify why your Session Border Controller disallowed the call.<br/> - Ensure that your Communication Services token is valid and not expired. |
 | 560403 | 403 | - Call forbidden.<br/> - Call canceled.<br/> - Call rejected. |  | Make sure that you called a valid phone number in the correct format. For more information about supported number formats, see <https://en.wikipedia.org/wiki/E.164>. |
 | 511532 | 403 | Resource SIP trunk configuration not found. |  | Check your direct routing setup in the [Azure portal](https://portal.azure.com). For more information, see [Direct routing provisioning](../../../../../concepts/telephony/direct-routing-provisioning.md). |
 | 560404 | 404 | - Phone number not found.<br/> - Phone number not assigned to any target.<br/> - Phone number not allowed by Session Border Controller.  |  | - Make sure the phone number belongs to the Resource you're using and that you own the Resource.<br/> - Verify that the number you're calling exists, and is assigned to valid target. |

articles/deployment-environments/how-to-configure-extensibility-model-custom-image.md

@@ -504,6 +504,10 @@ In this configuration, ADE uses the Managed Identity for the PET, whether system
 > [!Tip]
 > This role assignment has to be made for every project environment type. It can be automated through the Azure CLI.
 
+> [!Tip]
+> If your ACR uses Microsoft Entra attribute-based access control (ABAC) for repository permissions, you may need to make additional role assignments like `Container Registry Repository Reader` to the PET identity. For more information, see [Microsoft Entra ABAC for repository permissions](/azure/container-registry/container-registry-rbac-abac-repository-permissions).
+
+
 When you're ready to push your image to your registry, run the following command:
 
 ```docker
@@ -545,4 +549,4 @@ To learn more about how to create environment definitions that use the ADE conta
 - [ADE CLI variables reference](reference-deployment-environment-variables.md)
 ::: zone pivot="pulumi"
 - [Pulumi's azure-deployment-environments repository](https://github.com/pulumi/azure-deployment-environments)
-::: zone-end
+::: zone-end

articles/expressroute/expressroute-about-virtual-network-gateways.md

@@ -92,7 +92,7 @@ When Auto-Assigned Public IP is enabled, the ExpressRoute gateway's Overview pag
 
 **How it works:**  
 
-When you create an ExpressRoute gateway, Microsoft automatically provisions and manages the public IP address in a secure, backend subscription. This IP is encapsulated within the gateway resource, enabling Microsoft to enforce policies such as data rate limits and enhance auditability.
+When you create an ExpressRoute gateway, Microsoft automatically provisions and manages the public IP address in a secure, backend subscription. This IP is encapsulated within the gateway resource, enabling Microsoft to enforce policies such as data rate limits and enhance auditability. Previously it was possible to create the public IP resource as a zonal resource which ensured that all instances of the gateway in that zone shared the same public IP address. New behavior is that the gateway is always zone redundant.
 
 **Availability:**  
 

articles/expressroute/expressroute-howto-add-gateway-portal-resource-manager.md

@@ -80,8 +80,7 @@ The steps for this tutorial use the values in the following configuration refere
     | Minimum Scale Units | This option is only available when you select the **ErGwScale (Preview)** SKU. Enter the minimum number of scale units you want to use. For more information, see [ExpressRoute Gateway Scale Units](scalable-gateway.md). |
     | Maximum Scale Units | This option is only available when you select the **ErGwScale (Preview)** SKU. Enter the maximum number of scale units you want to use. For more information, see [ExpressRoute Gateway Scale Units](scalable-gateway.md). |
     | Virtual network | Select *vnet-1*. |
-    | **Public IP address** | |
-    | Assignment | By default, all ExpressRoute Gateways will have an [Auto-Assigned Public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). |
+    | **Public IP address** | ExpressRoute Gateways now have an [Auto-Assigned Public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). This Public IP address is automatically assigned to the gateway during its creation, which means zonal gateways can no longer be created. |
 
     > [!IMPORTANT]
     > If you plan to use IPv6-based private peering over ExpressRoute, please make sure to create your gateway with a Public IP address of type Standard, Static using the [PowerShell instructions](./expressroute-howto-add-gateway-resource-manager.md#add-a-gateway).

articles/expressroute/expressroute-howto-add-gateway-resource-manager.md

@@ -41,8 +41,6 @@ The steps for this task use a VNet based on the values in the following configur
 | Gateway IP Name | *GWIP* |
 | Gateway IP configuration Name | *gwipconf* |
 | Type | *ExpressRoute* |
-| Gateway Public IP Name  | *gwpip* |
-
 ## Add a gateway
 
 > [!IMPORTANT]
@@ -106,7 +104,8 @@ The steps for this task use a VNet based on the values in the following configur
 
    > [!NOTE]
    > Basic SKU public IP isn't supported with new ExpressRoute virtual network gateway.
-   > Creating a public IP is no longer required, Microsoft will create and manage your public IP.
+   > Creating a public IP is no longer required, [Microsoft will create and manage your public IP](expressroute-about-virtual-network-gateways.md#auto-assigned-public-ip). This means all ExpressRoute virtual network gateways are created as zone-redundant.
+
 
 1. Create the configuration for your gateway. The gateway configuration defines the subnet to use. In this step, you're specifying the configuration that will be used when you create the gateway. Use the following sample to create your gateway configuration.
 

articles/iot-operations/connect-to-cloud/howto-configure-local-storage-endpoint.md

@@ -158,17 +158,17 @@ The only supported serialization format is Parquet.
 
 ## Use Azure Container Storage enabled by Azure Arc (ACSA)
 
-You can use the local storage data flow endpoint together with [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/cloud-ingest-edge-volume-configuration) to store data locally or send data to a cloud destination.
+You can use the local storage data flow endpoint together with [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/howto-configure-cloud-ingest-subvolumes) to store data locally or send data to a cloud destination.
 
 ### Local shared volume
 
-To write to a local shared volume, first create a PersistentVolumeClaim (PVC) according to the instructions from [Local Shared Edge Volumes](/azure/azure-arc/container-storage/local-shared-edge-volumes).
+To write to a local shared volume, first create a PersistentVolumeClaim (PVC) according to the instructions from [Local Shared Edge Volumes](/azure/azure-arc/container-storage/tutorial-create-local-shared-volume).
 
 Then, when configuring your local storage data flow endpoint, input the PVC name under `persistentVolumeClaimRef`.
 
 ### Cloud ingest
 
-To write your data to the cloud, follow the instructions in [Cloud Ingest Edge Volumes configuration](/azure/azure-arc/container-storage/cloud-ingest-edge-volume-configuration) to create a PVC and attach a subvolume for your desired cloud destination.
+To write your data to the cloud, follow the instructions in [Cloud Ingest Edge Volumes configuration](/azure/azure-arc/container-storage/howto-configure-cloud-ingest-subvolumes) to create a PVC and attach a subvolume for your desired cloud destination.
 
 > [!IMPORTANT]
 > Don't forget to create the subvolume after creating the PVC, or else the data flow fails to start and the logs show a "read-only file system" error.