Merge pull request #313003 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-11 17:00 UTC

Author: Taojunshen

.openpublishing.redirection.json

@@ -7288,6 +7288,11 @@
     {
       "source_path": "articles/virtual-network/virtual-network-troubleshoot-cannot-delete-vnet.md",
       "redirect_url": "/troubleshoot/azure/virtual-network/virtual-network-troubleshoot-cannot-delete-vnet"
-    }
+    },
+    {
+      "source_path": "articles/certification/edge-secured-core-get-certified.md",
+      "redirect_url": "/azure/certification/requirements-edge-secured-core",
+      "redirect_document_id": false
+    },
   ]
 }

articles/api-management/api-management-region-availability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 11/11/2025
+ms.date: 03/11/2026
 ms.author: danlep
 ms.custom:
   - references_regions
@@ -24,6 +24,8 @@ API Management [v2 tiers](v2-service-tiers-overview.md) and API Management [work
 
 Information in the following table is updated regularly. Capacity availability in Azure regions may vary.
 
+> [!IMPORTANT]
+> **Temporary capacity limitation:** Creation of new Basic v2 and Standard v2 instances in **UK South** is currently unavailable due to capacity constraints. We're actively working to restore availability in this region. In the meantime, consider deploying to an alternative region such as **UK West** or **North Europe**. Existing instances in UK South are not affected.
 
 | Region | Basic v2 | Standard v2 | Premium v2 | Workspace gateway (Premium) | 
 |-----|:---:|:---:|:---:|:---:|
@@ -52,12 +54,14 @@ Information in the following table is updated regularly. Capacity availability i
 | South India | ✅ | ✅ |  |  |
 | Switzerland North | ✅ |✅ |  | |
 | UAE North | ✅ | ✅ | |  |
-| UK South | ✅  | ✅ | ✅ | ✅ |
+| UK South | ✅ ¹ | ✅ ¹ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
 | West Europe  | ✅ | ✅ | | ✅ |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 
+¹ New instance creation temporarily unavailable. See the capacity limitation note above.
+
 ## Related content
 
 Learn more about:

articles/application-gateway/migrate-v1-v2.md

@@ -1,58 +1,58 @@
 ---
-title: We're retiring Application Gateway V1 SKU in April 2026
+title: We're Retiring Application Gateway V1 in April 2026
 titleSuffix: Azure Application Gateway
-description: This article provides a high-level overview of the retirement of Application gateway V1 SKUs. 
+description: This article provides a high-level overview of the retirement of Application Gateway V1. 
 services: application-gateway
 author: MJyot
 ms.service: azure-application-gateway
-ms.topic: how-to
+ms.topic: concept-article
 ms.date: 04/19/2023
 ms.author: mjyothish
-# Customer intent: As an IT administrator using Application Gateway V1, I want to migrate to Application Gateway V2 before April 28, 2026, so that I can ensure continuous support and benefit from enhanced performance and security features.
+#customer intent: As an IT administrator who's using Application Gateway V1, I want to migrate to Application Gateway V2 before April 28, 2026, so that I can ensure continuous support and benefit from enhanced performance and security features.
 ---
 
-# Migrate your Application Gateways from V1 SKU to V2 SKU by April 28, 2026 
+# Migrate from Application Gateway V1 to V2 by April 28, 2026
 
 **Applies to:** :heavy_check_mark: Application Gateway v1 deployments
 
-We announced the deprecation of Application Gateway V1 on **April 28 ,2023**. Beginning **April 28, 2026**, the Application Gateway V1 SKU will be retired, meaning it won't be supported after this date. If you use Application Gateway V1 SKU, start planning your migration to V2 now. Complete it by April 28, 2026, to take advantage of [Application Gateway V2](./overview-v2.md).
+We announced the deprecation of Azure Application Gateway V1 on April 28, 2023. On *April 28, 2026*, Application Gateway V1 will be retired. We won't support it after this date.
 
-## Retirement Timelines 
+If you use Application Gateway V1, start planning your migration to [Application Gateway V2](./overview-v2.md) now. Complete it by April 28, 2026.
 
-- Deprecation announcement: April 28 ,2023 
+## Retirement timelines
 
--	No new subscriptions for V1 deployments: July 1,2023 onwards - Application Gateway V1 is no longer available for deployment on subscriptions without V1 gateways from July 1 2023 onwards.
+- Deprecation announcement: April 28, 2023.
 
-- No new V1 deployments: Sept 1, 2024 - V1 creation is stopped completely for all customers 1 September 2024 onwards.
+- No new subscriptions for V1 deployments: July 1, 2023. Application Gateway V1 is no longer available for deployment on subscriptions without V1 gateways.
 
-- SKU retirement: April 28, 2026 - Any Application Gateway V1 that are in Running status will be stopped. Application Gateway V1s that aren't migrated to Application Gateway V2 are informed regarding timelines for deleting them and then force deleted.
+- No new V1 deployments: September 1, 2024. V1 creation stopped completely for all customers.
 
-## Resources available for migration
+- Retirement: April 28, 2026. Any Application Gateway V1 deployments that have a running status are stopped.
 
-- Follow the steps outlined in the [migration script](./migrate-v1-v2.md) to migrate from Application Gateway v1 to v2. Review [pricing](./understanding-pricing.md) before making the transition.
+We'll inform you about the timeline for deleting your Application Gateway V1 deployments. After that, we'll delete deployments that aren't migrated to Application Gateway V2.
 
-- Use the Migrate Application Gateway from v1 to v2 video guide to understand the migration steps.
+## Required action
 
-> [!VIDEO 7ed01e33-80a9-4daa-9322-e771f963a2fe]
+To start planning your migration to Application Gateway V2, make a list of all Application Gateway V1 gateways. On April 28, 2023, we sent an email with the subject "Retirement Notice: Transition to Application Gateway V2 by 28 April 2026" to V1 subscription owners. The email provided details about the subscription, the names of gateways, and Application Gateway V1 resources. Use these details to build the list.
 
--	If your company/organization has partnered with Microsoft or works with Microsoft representatives (like cloud solution architects (CSAs) or customer success account managers (CSAMs)), work with them for migration.
+Complete the migration as soon as possible to prevent business impact and to take advantage of the improved performance, security, and new features of Application Gateway V2.
 
-## Required action
+## Resources for migration
+
+- For migration instructions, see [Migrate Azure Application Gateway and Web Application Firewall from V1 to V2](./migrate-v1-v2.md).
+
+- For pricing information, see [Understanding pricing for Azure Application Gateway and Web Application Firewall](./understanding-pricing.md).
 
-Start planning your migration to Application Gateway V2 today.
+- To better understand the migration steps, see this video guide:
 
-- Make a list of all Application Gateway V1 Sku gateways: On April 28,2023, we sent out emails with subject "Retirement Notice: Transition to Application Gateway V2 by 28 April 2026" to V1 subscription owners. The email provides the Subscription, Gateway Name, and Application Gateway V1 resource details. Use the details to build this list.
+  > [!VIDEO 7ed01e33-80a9-4daa-9322-e771f963a2fe]
 
-- [Learn more](./migrate-v1-v2.md) about migrating your application gateway V1 to V2 SKU. For more information, see [Frequently asked questions about V1 to V2 migration.](./retirement-faq.md#faq-on-v1-to-v2-migration)
+- For FAQ, see [Frequently asked questions about Application Gateway V1 retirement](./retirement-faq.md).
 
-- For technical questions, issues, and help get answers from community experts in  [Microsoft Q&A](https://aka.ms/ApplicationGatewayQA) or reach out to us at [AppGatewayMigrationTeam](mailto:[email protected]). If you have a support question and you need technical help, create a [support request](https://portal.azure.com/#view/Microsoft_Azure_Support/NewSupportRequestV3Blade) . 
+- For the announcement about the capabilities of V2, see the blog post [Taking advantage of the new Azure Application Gateway V2](https://azure.microsoft.com/blog/taking-advantage-of-the-new-azure-application-gateway-v2/).
 
-- Complete the migration as soon as possible to prevent business impact and to take advantage of the improved performance, security, and new features of Application Gateway V2.
+- If your company or organization partners with Microsoft or works with Microsoft representatives, like cloud solution architects (CSAs) or customer success account managers (CSAMs), work with them for the migration.
 
-Blog: [Take advantage of Application gateway V2](https://azure.microsoft.com/blog/taking-advantage-of-the-new-azure-application-gateway-v2/)
+- For technical questions, issues, and help, you can get answers from community experts in [Microsoft Q&A](https://aka.ms/ApplicationGatewayQA) or [email the Application Gateway migration team](mailto:appgatewaymigration@microsoft.com).
 
-## Next steps
-  
-  * [Migration Guidance](./migrate-v1-v2.md)
-  * [Common questions on Migration](./retirement-faq.md)
-  
+- If you need further technical help, create a [support request](https://portal.azure.com/#view/Microsoft_Azure_Support/NewSupportRequestV3Blade).

articles/application-gateway/retirement-faq.md

@@ -182,9 +182,9 @@ You can view the complete project template in the [Azure Functions .NET MCP Serv
 ::: zone pivot="programming-language-java"
 The function code for the MCP server tools is defined in the `src/main/java/com/function/` folder. The `@McpToolTrigger` annotation exposes the functions as MCP Server tools:
 
-:::code language="java" source="~/functions-scenarios-custom-mcp-java/src/main/java/com/function/HelloWorld.java" range="35-51" :::
+<!- :::code language="java" source="~/functions-scenarios-custom-mcp-java/src/main/java/com/function/HelloWorld.java" range="35-51" ::: >
 
-:::code language="java" source="~/functions-scenarios-custom-mcp-java/src/main/java/com/function/Snippets.java" range="80-118" :::
+<!- :::code language="java" source="~/functions-scenarios-custom-mcp-java/src/main/java/com/function/Snippets.java" range="80-118" ::: >
 
 You can view the complete project template in the [Azure Functions Java MCP Server](https://github.com/Azure-Samples/remote-mcp-functions-java) GitHub repository.
 ::: zone-end  

articles/application-gateway/v1-retirement.md

@@ -102,7 +102,7 @@ The following functions are available for working with lambda expressions. All o
 * [filter](bicep-functions-lambda.md#filter)
 * [groupBy](bicep-functions-lambda.md#groupby)
 * [map](bicep-functions-lambda.md#map)
-* [mapValue](bicep-functions-lambda.md#mapvalues)
+* [mapValues](bicep-functions-lambda.md#mapvalues)
 * [reduce](bicep-functions-lambda.md#reduce)
 * [sort](bicep-functions-lambda.md#sort)
 * [toObject](bicep-functions-lambda.md#toobject)

articles/azure-functions/scenario-custom-remote-mcp-server.md

@@ -2,10 +2,8 @@
   href: index.yml
 - name: What is Edge Secured-core?
   href: overview.md
-- name: Program requirements
-  href: program-requirements-edge-secured-core.md
-- name: Get your device certified
-  href: edge-secured-core-get-certified.md
+- name: Requirements
+  href: requirements-edge-secured-core.md
 - name: List of certified devices
   href: edge-secured-core-devices.md
 - name: Validate Edge Secured-core device

articles/azure-resource-manager/bicep/bicep-functions.md

@@ -4,12 +4,16 @@ description: List of devices that have passed the Edge Secured-core certificatio
 author: sufenfong
 ms.author: sufon
 ms.topic: concept-article
-ms.date: 08/06/2024 
+ms.date: 01/12/2026
 ms.custom: Edge Secured-core certified devices
 ms.service: azure-certified-device
 ---
 
 # Edge Secured-core certified devices
+> [!IMPORTANT]
+> The Edge Secured-core certification program has been discontinued as of December 2025. Devices listed below were certified prior to this date.
+> For similar certification programs, please refer to [Secured-core PC on Windows](/windows-hardware/design/device-experiences/oem-highly-secure-11).
+
 This page contains a list of devices that have successfully passed the Edge Secured-core certification. The listed models may not be shipped as secure-by-default. When ordering, please request specifically for Edge Secured-core devices. 
 
 |Manufacturer|Device Name|OS|Last Updated|