Merge pull request #313061 from MicrosoftDocs/main

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

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

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -108,12 +108,12 @@ If the subnet has a combination of volumes with the Standard and Basic network f
 Configuring UDRs on the source VM subnets with the address prefix of delegated subnet and next hop as NVA isn't supported for volumes with the Basic network features. Such a setting will result in connectivity issues.
 
 > [!NOTE]
-> To access an Azure NetApp Files volume from an on-premises network via a VNet gateway (ExpressRoute or VPN) and firewall, configure the route table assigned to the VNet gateway to include the `/32` IPv4 address of the Azure NetApp Files volume listed and point to the firewall as the next hop. Using an aggregate address space that includes the Azure NetApp Files volume IP address doesn't forward the Azure NetApp Files traffic to the firewall. 
+> To access an Azure NetApp Files volume from an on-premises network via a VNet gateway (ExpressRoute or VPN) and firewall, configure the route table assigned to the VNet gateway to include the IPv4 address of the Azure NetApp Files volume and point to the firewall as the next hop. Using an aggregate address space that includes the Azure NetApp Files volume IP address doesn't forward the Azure NetApp Files traffic to the firewall. 
 
 >[!NOTE]
 > If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Azure NetApp Files standard volume from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Azure NetApp Files volume. If the UDR prefix is less specific than the delegated subnet size, it isn't effective. 
 >
-> For example, if your delegated subnet is `x.x.x.x/24`, you must configure your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
+> For example, if your delegated subnet is `x.x.x.x/24`, you must configure your UDR to `x.x.x.x/24` (equal) or `x.x.x.x` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
 
 ## Azure native environments
 

articles/backup/threat-detection-overview.md

@@ -55,7 +55,7 @@ The following table describes the available summary statuses for source scans in
 
 ## Supported regions for threat detection for Azure VM backups
 
-Threat detection for Azure VM backups is available in preview in these regions: West Central US, Australia East, North Europe, Switzerland North, West Europe, Central US, East US, East US2, West US, UK South, UK West, Canada Central, Japan East, Japan West, India Central, India South, India West, Australia Central, Australia Southeast, Brazil South, Northcentral US, Canada East, East US3, Korea Central, Norway East, South Africa North, Sweden Central, Australia Central 2, France Central, Germany North, Jio India Central, Korea South, Poland Central, South Africa West, Switzerland West, Sweden South, Southeast Asia, UAE North, West US3, Brazil Southeast, South Central US, France South, Germany West Central, Jio India West, Malaysia South, Norway West, Southeast US, Taiwan North, New Zealand North, Malaysia West, Chile Central, Belgium Central, Austria East and Denmark East. 
+Threat detection for Azure VM backups is available in preview in all Azure public regions except these regions: UAE Central, Israel Central, Qatar Central and Israel North West.
 
 ## Limitations and known issues
 

articles/frontdoor/standard-premium/how-to-enable-private-link-apim.md

@@ -18,9 +18,6 @@ zone_pivot_groups: front-door-dev-exp-portal-ps-cli
 
 This article guides you through the steps to configure an Azure Front Door Premium to connect privately to your Azure API Management origin using Azure Private Link.
 
-> [!NOTE]
-> This functionality is not supported with API Management Premium v2 tier.
-
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).

articles/managed-grafana/how-to-connect-to-data-source-privately.md

@@ -41,6 +41,7 @@ Managed private endpoints work with Azure services that support private link. Us
 - Azure SQL server
 - Azure Databricks
 - Private link services
+- Azure Database for PostgreSQL flexible servers
 
 When you create a managed private endpoint in your Azure Managed Grafana workspace, a private endpoint connection is created in a *Pending* state. This action begins an approval workflow. The private link resource owner is responsible for approving or rejecting the new connection. If the owner approves the connection, the private link is established. Otherwise, the private link isn't set up.
 

articles/migrate/how-to-build-a-business-case.md

@@ -31,19 +31,20 @@ This article describes how to build a Business case for on-premises servers and
 
 The **Business case** helps you understand where Azure can bring the most value to your organization by estimating total cost of ownership (TCO), potential savings, and sustainability impact for your **applications and workloads**. Highlights include:
 
-- On‑premises vs Azure TCO and year‑over‑year (YoY) cash‑flow.  
+- On‑premises vs Azure (including Azure VMware Solution) TCO and year‑over‑year (YoY) cash‑flow.  
 - Current on-premises vs On-premises with Arc TCO. 
 - Savings from Azure Hybrid Benefit (AHB), Extended Security Updates (ESU) on Azure, and Security & Management with Microsoft Defender for Cloud and Azure Monitor/Update Manager.  
 - Long term cost savings by moving from a capital expenditure model to an Operating expenditure model, by paying for only what you use.
 - Sustainability insights (estimated emissions on‑premises vs Azure and YoY reductions). 
 - Discovery insights that summarize scope, utilization, OS/DB support status, and quick wins for migration/modernization.
 
-There are 2 types of migration preferences that you can choose while building your Business case:
+There are 3 types of migration preferences that you can choose while building your Business case:
 
 | Migration Strategy | Details | Assessment insights |
 | --- | --- | --- |
 | **Modernize (Platform as a Service)** | You can get a PaaS preferred recommendation that means, the logic identifies workloads best fit for PaaS targets. <br/><br/>General servers are recommended with a quick lift and shift recommendation to Azure IaaS. | For SQL Servers, sizing and cost comes from the *Recommended report* with optimization strategy - *Modernize to PaaS* from Azure SQL assessment.<br/><br/> For web apps, sizing and cost comes from Azure App Service and Azure Kubernetes Service assessments, with a preference to App Service. For general servers, sizing and cost comes from Azure VM assessment.<br/><br/> All of these recommendations are  aggregated using the heterogenous assessments.
 | **Migrate to all IaaS (Infrastructure as a Service)** | You can get a quick lift and shift recommendation to Azure IaaS. | For SQL Servers, sizing and cost comes from the *Instance to SQL Server on Azure VM* report. <br/><br/>For general servers and servers hosting web apps, sizing and cost comes from Azure VM assessment. <br/><br/> All of these recommendations are  aggregated using the heterogenous assessments. |
+| **Migrate to Azure VMware Solution** | You can get the TCO for a quick lift and shift recommendation to Azure VMware Solution. | Sizing and cost are derived from an Azure VMware Solution assessment. <br/><br/> All of these recommendations are  aggregated using the heterogenous assessments. |
 
 Business case picks Azure recommendations from heterogenous assessments, and you will be able to access the assessments directly. To deep dive into sizing, readiness, and Azure cost estimates, you can open the respective assessment for the applications or workloads.
 
@@ -83,7 +84,7 @@ To build a business case, follow these steps:
 1. In **Migration preference**, specify the migration preference for your Business case:
 
     - With the default *Modernize*, you can get the most cost-efficient and compatible target recommendation in Azure across Azure PaaS targets with a fallback to IaaS targets if workloads aren't ready to be modernized to PaaS targets.
-    - With the Migrate to IaaS Time option, you can get a quick lift-and-shift recommendation to Azure IaaS offerings like Azure VM and Azure VMware Solution. 
+    - With the *Migrate* option, you can get a quick lift-and-shift recommendation to Azure IaaS offerings like Azure VM and Azure VMware Solution. 
     - Select **Preferred Target** as Azure VM for a quick lift and shift recommendation to Azure VM 
     - Select **Preferred Target** as Azure VMware Solution (AVS) for the most cost-effective and compatible target recommendation for hosting workloads on AVS.
     > [!Note]
@@ -102,4 +103,4 @@ To build a business case, follow these steps:
     :::image type="content" source="./media/how-to-build-a-business-case/review-and-build.png" alt-text="Screenshot shows how to review and build a business case.":::
 
 ## Next steps
-- [Learn more](how-to-view-a-business-case.md) about how to review the Business case reports.
+- [Learn more](how-to-view-a-business-case.md) about how to review the Business case reports.

articles/resource-mover/support-matrix-move-region-azure-vm.md

@@ -3,7 +3,7 @@ title: Support matrix for moving Azure VMs to another region with Azure Resource
 description: Review support for moving Azure VMs between regions with Azure Resource Mover.
 author: RochakSingh-blr
 ms.author: v-rochak2
-ms.date: 07/31/2025
+ms.date: 03/05/2026
 ms.service: azure-resource-mover
 ms.topic: how-to
 ms.update-cycle: 365-days
@@ -19,8 +19,7 @@ This article summarizes support and prerequisites when you move virtual machines
 
 Resource Mover supports Azure VMs running these Windows operating systems.
 
-> [!NOTE]
-> Windows Trusted Launch VMs are supported by Resource Mover. 
+[!INCLUDE [end-of-support-notes-windows-server-2008.md](../../includes/end-of-support-notes-windows-server-2008.md)]
 
 **Operating system** | **Details**
 --- | ---
@@ -34,6 +33,8 @@ Windows 8.1 (x64) | Supported.
 Windows 8 (x64) | Supported.
 Windows 7 (x64) with SP1 onwards | Install a Windows [servicing stack update (SSU)](https://support.microsoft.com/help/4490628) and [SHA-2 update](https://support.microsoft.com/help/4474419) on machines running Windows 7 with SP1. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the 'prepare' step won't succeed. Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
 
+> [!NOTE]
+> Windows Trusted Launch VMs are supported by Resource Mover.
 
 ## Linux VM support
 

articles/site-recovery/includes/end-of-life-notes-windows-server-2008.md

@@ -10,4 +10,4 @@ ms.service: azure-site-recovery
 
 ---
 > [!NOTE]
-> Windows Server 2008 and Windows Server 2008 R2 have reached End of Life (EOL). For more information, see, [End of support for Windows Server 2008 and Windows Server 2008 R2](/troubleshoot/windows-server/windows-server-eos-faq/end-of-support-windows-server-2008-2008r2) and [Perform in-place upgrade to Windows Server 2016, 2019, 2022, or 2025](/azure/virtual-machines/windows-in-place-upgrade#perform-in-place-upgrade-to-windows-server-2016-2019-2022-or-2025). Review your usage and plan OS upgrades and migrations accordingly.
+> Windows Server 2008 and Windows Server 2008 R2 have reached End of Support (EOS). For more information, see, [End of support for Windows Server 2008 and Windows Server 2008 R2](/troubleshoot/windows-server/windows-server-eos-faq/end-of-support-windows-server-2008-2008r2) and [Perform in-place upgrade to Windows Server 2016, 2019, 2022, or 2025](/azure/virtual-machines/windows-in-place-upgrade#perform-in-place-upgrade-to-windows-server-2016-2019-2022-or-2025). Review your usage and plan OS upgrades and migrations accordingly.

articles/storage/blobs/TOC.yml

@@ -232,6 +232,8 @@ items:
                 href: secure-file-transfer-protocol-support-how-to.md
               - name: Authorize access
                 href: secure-file-transfer-protocol-support-authorize-access.md
+              - name: Authorize access with Microsoft Entra ID (preview)
+                href: secure-file-transfer-protocol-support-entra-id-based-access.md
               - name: Connect from an SFTP client
                 href: secure-file-transfer-protocol-support-connect.md
               - name: Performance considerations