Merge pull request #307163 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

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/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/sentinel/work-with-threat-indicators.md

@@ -172,7 +172,7 @@ Threat indicators are stored in the Microsoft Sentinel `ThreatIntelligenceIndica
 
 >[!IMPORTANT]
 > On April 3, 2025, we publicly previewed two new tables to support STIX indicator and object schemas: `ThreatIntelIndicators` and `ThreatIntelObjects`. Microsoft Sentinel will ingest all threat intelligence into these new tables, while continuing to ingest the same data into the legacy `ThreatIntelligenceIndicator` table until July 31, 2025. 
->**Be sure to update your custom queries, analytics and detection rules, workbooks, and automation to use the new tables by July 31, 2025.** After this date, Microsoft Sentinel will stop ingesting data to the legacy `ThreatIntelligenceIndicator` table. We're updating all out-of-the-box threat intelligence solutions in Content hub to leverage the new tables. For more information about the new table schemas, see [ThreatIntelIndicators](/azure/azure-monitor/reference/tables/threatintelligenceindicator) and [ThreatIntelObjects](/azure/azure-monitor/reference/tables/threatintelobjects).
+>**Be sure to update your custom queries, analytics and detection rules, workbooks, and automation to use the new tables by July 31, 2025.** After this date, Microsoft Sentinel will stop ingesting data to the legacy `ThreatIntelligenceIndicator` table. We're updating all out-of-the-box threat intelligence solutions in Content hub to leverage the new tables. For more information about the new table schemas, see [ThreatIntelIndicators](/azure/azure-monitor/reference/tables/threatintelindicators) and [ThreatIntelObjects](/azure/azure-monitor/reference/tables/threatintelobjects).
 > For information on using and migrating to the new tables, see (Work with STIX objects to enhance threat intelligence and threat hunting in Microsoft Sentinel (Preview))[work-with-stix-objects-indicators.md]. 
 
 

includes/storage-file-sync-cost-categories.md

@@ -10,7 +10,7 @@
  ms.custom: include file
 ---
 
-- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure virtual machine, or even in another cloud. The costs for sync servers hosted on-premises or in other cloud providers include both capital and operating costs that aren't tracked as part of your Azure bill, but are still part of the total cost of ownership of the solution. Captial expenses are the upfront hardware costs of your solution. Operating expenses are the ongoing costs of labor, electricity, etc. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads, and other organization-specific costs you might have. For more information, see [recommended system resources](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources).
+- **Capital and operational costs of Windows File Servers with one or more server endpoints.** Azure File Sync as a replication solution is agnostic of where the Windows File Servers that are synchronized with Azure Files are; they could be hosted on-premises, in an Azure virtual machine, or even in another cloud. The costs for sync servers hosted on-premises or in other cloud providers include both capital and operating costs that aren't tracked as part of your Azure bill, but are still part of the total cost of ownership of the solution. Capital expenses are the upfront hardware costs of your solution. Operating expenses are the ongoing costs of labor, electricity, etc. You should consider the amount of data you need to cache on-premises, the number of CPUs and amount of memory your Windows File Servers need to host Azure File Sync workloads, and other organization-specific costs you might have. For more information, see [recommended system resources](../articles/storage/file-sync/file-sync-planning.md#recommended-system-resources).
 
 - **Per server licensing cost for servers registered with Azure File Sync.** To use Azure File Sync with a specific Windows File Server, you must first register it with Azure File Sync's Azure resource, the Storage Sync Service. Each server that you register after the first server has a flat monthly fee. Although this fee is small, it is one component of your bill to consider. To see the current price of the server registration fee for your desired region, see [the File Sync section on Azure Files pricing page](https://azure.microsoft.com/pricing/details/storage/files/).