Merge pull request #301115 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 6/10

Author: ttorble

articles/backup/azure-kubernetes-service-cluster-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: Azure Kubernetes Service (AKS) backup support matrix
 description: This article provides a summary of support settings and limitations of Azure Kubernetes Service (AKS) backup.
 ms.topic: reference
-ms.date: 09/09/2024
+ms.date: 06/10/2025
 ms.custom:
   - references_regions
   - ignite-2023
@@ -151,6 +151,7 @@ This behavior prevents accidental data loss and ensures consistent backups. Cons
 
 ## Next steps
 
-- [About Azure Kubernetes Service cluster backup](azure-kubernetes-service-cluster-backup-concept.md)
-- [Back up Azure Kubernetes Service cluster](azure-kubernetes-service-cluster-backup.md)
-- [Restore Azure Kubernetes Service cluster](azure-kubernetes-service-cluster-restore.md)
+- [About Azure Kubernetes Service cluster backup](azure-kubernetes-service-cluster-backup-concept.md).
+- Back up Azure Kubernetes Service cluster using [Azure portal](azure-kubernetes-service-cluster-backup.md), [Azure CLI](azure-kubernetes-service-cluster-backup-using-cli.md), [Azure PowerShell](azure-kubernetes-service-cluster-backup-using-powershell.md), [Azure Resource Manager](quick-kubernetes-backup-arm.md), [Bicep](quick-kubernetes-backup-bicep.md), [Terraform](quick-kubernetes-backup-terraform.md).
+- Restore Azure Kubernetes Service cluster using [Azure portal](azure-kubernetes-service-cluster-restore.md), [Azure CLI](azure-kubernetes-service-cluster-restore-using-cli.md), [Azure PowerShell](azure-kubernetes-service-cluster-restore-using-powershell.md).
+- [Manage Azure Kubernetes Service backups using Azure Backup](azure-kubernetes-service-cluster-manage-backups.md).

articles/backup/backup-azure-vm-migrate-enhanced-policy.md

@@ -2,7 +2,7 @@
 title: Move VM backup - standard to enhanced policy in Azure Backup
 description: Learn how to trigger Azure VM backups migration from standard  policy to enhanced policy, and then monitor the configuration backup migration job.
 ms.topic: reference
-ms.date: 05/27/2025
+ms.date: 06/10/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -18,7 +18,7 @@ This article describes how to migrate Azure Virtual Machine (VM) backups from st
 Azure Backup now supports migration to the enhanced policy for Azure VM backups using standard policy. The migration of VM backups to enhanced policy enables you to schedule multiple backups per day (up to every 4 hours), retain snapshots for longer duration, and use multi-disk crash consistency for VM backups. Snapshot-tier recovery points (created using enhanced policy) are zonally resilient. The migration of VM backups to enhanced policy also allows you to migrate your VMs to Trusted Launch and use Premium SSD v2 and Ultra-disks for the VMs without disrupting the existing backups.
 
 >[!Note]
->Standard policy supports backup only for unprotected trusted launch VMs via PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later). To enable trusted launch for existing VMs protected by Standard Policy, migrate to Enhanced Policy first.
+>Standard policy supports backup only for unprotected trusted launch VMs via CLI (version 2.73.0 and later), PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later). To enable trusted launch for existing VMs protected by Standard Policy, migrate to Enhanced Policy first.
 
 ## Considerations
 

articles/backup/backup-azure-vms-enhanced-policy.md

@@ -2,7 +2,7 @@
 title: Back up Azure VMs with Enhanced policy
 description: Learn how to configure Enhanced policy to back up VMs.
 ms.topic: how-to
-ms.date: 05/27/2025
+ms.date: 06/10/2025
 ms.reviewer: sharrai
 ms.service: azure-backup
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
@@ -19,7 +19,7 @@ Azure Backup now supports Enhanced policy for Azure VM backup that offers:
 - Longer retention in snapshot (operational) tier up to 30 days.
 
 >[!Note]
->- Standard policy doesn't support protecting newer Azure offerings, such as Ultra SSD and Premium SSD v2. Only PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) support trusted launch VM backup with Standard policy.
+>- Standard policy doesn't support protecting newer Azure offerings, such as Ultra SSD and Premium SSD v2. Only CLI (version 2.73.0 and later), PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) support trusted launch VM backup with Standard policy.
 >- Backups for VMs with data access authentication enabled disks fails.
 >- Protection of a VM with an enhanced policy incurs additional snapshot costs. [Learn more](backup-instant-restore-capability.md#cost-impact).
 >- Once you enable a VM backup with Enhanced policy, Azure Backup doesn't allow to change the policy type to Standard.

articles/backup/backup-support-matrix-iaas.md

@@ -2,7 +2,7 @@
 title: Support matrix for Azure VM backups
 description: Get a summary of support settings and limitations for backing up Azure VMs by using the Azure Backup service.
 ms.topic: reference
-ms.date: 06/09/2025
+ms.date: 06/10/2025
 ms.custom:
   - references_regions
   - linux-related-content
@@ -185,7 +185,7 @@ Back up Azure VMs with locks | Supported for managed VMs. <br><br> Not supported
 Configure standalone Azure VMs in Windows Storage Spaces | Not supported.
 [Restore Virtual Machine Scale Sets](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#scale-sets-with-flexible-orchestration) | Supported for the flexible orchestration model to back up and restore a single Azure VM.
 Restore with managed identities | Supported for managed Azure VMs. <br><br> Not supported for classic and unmanaged Azure VMs. <br><br> Cross-region restore isn't supported with managed identities. <br><br> Currently, this is available in all Azure public and national cloud regions. <br><br> [Learn more](backup-azure-arm-restore-vms.md#restore-vms-with-managed-identities).
-<a name="tvm-backup">Back up trusted launch VMs</a>    |  Supported via [Enhanced policy](backup-azure-vms-enhanced-policy.md) and [Standard policy](backup-instant-restore-capability.md). <br><br>    **Feature details**:  <br><br> - Backup is supported in all regions where trusted launch VMs are available.  <br>   - Item-level restore is supported for the [applicable scenarios](#support-for-file-level-restore).      <br><br>  **Backup support via Enhanced policy**:  <br><br> - Azure portal, PowerShell, and REST API clients support trusted launch VM backup with Enhanced policy.   <br>  - The Azure portal allows you to enable backup through a [Recovery Services vault](backup-azure-arm-vms-prepare.md), the [VM management pane](backup-during-vm-creation.md#run-an-on-demand-backup-after-vm-creation), and the VM creation pane.   <br>  - Azure Business Continuity Center supports [backup](../business-continuity-center/tutorial-configure-protection-datasource.md), [alerts](../business-continuity-center/tutorial-monitor-alerts-metrics.md), and [monitoring](../business-continuity-center/tutorial-monitor-protection-summary.md) for trusted launch VMs.    <br><br>       **Backup support via Standard policy**:    <br><br>  - PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) only support trusted launch VM backup with Standard policy.  <br>  - Trusted Launch virtual machines with standard policy use managed disk snapshots for Instant Restore. In this scenario, you incur Snapshot storage cost same as that of Enhanced policy. [Learn more](backup-instant-restore-capability.md#cost-impact).    <br><br>    Note that migration of an existing Gen2 VM (protected by Azure Backup Standard policy) to Trusted Launch VM requires first [switching to Enhanced policy](backup-azure-vm-migrate-enhanced-policy.md).
+<a name="tvm-backup">Back up trusted launch VMs</a>    |  Supported via [Enhanced policy](backup-azure-vms-enhanced-policy.md) and [Standard policy](backup-instant-restore-capability.md). <br><br>    **Feature details**:  <br><br> - Backup is supported in all regions where trusted launch VMs are available.  <br>   - Item-level restore is supported for the [applicable scenarios](#support-for-file-level-restore).      <br><br>  **Backup support via Enhanced policy**:  <br><br> - Azure portal, PowerShell, and REST API clients support trusted launch VM backup with Enhanced policy.   <br>  - The Azure portal allows you to enable backup through a [Recovery Services vault](backup-azure-arm-vms-prepare.md), the [VM management pane](backup-during-vm-creation.md#run-an-on-demand-backup-after-vm-creation), and the VM creation pane.   <br>  - Azure Business Continuity Center supports [backup](../business-continuity-center/tutorial-configure-protection-datasource.md), [alerts](../business-continuity-center/tutorial-monitor-alerts-metrics.md), and [monitoring](../business-continuity-center/tutorial-monitor-protection-summary.md) for trusted launch VMs.    <br><br>       **Backup support via Standard policy**:    <br><br>  - CLI (version 2.73.0 and later), PowerShell (version Az 14.0.0 and later), and REST API (version 2025-01-01 and later) only support trusted launch VM backup with Standard policy.  <br>  - Trusted Launch virtual machines with standard policy use managed disk snapshots for Instant Restore. In this scenario, you incur Snapshot storage cost same as that of Enhanced policy. [Learn more](backup-instant-restore-capability.md#cost-impact).    <br><br>    Note that migration of an existing Gen2 VM (protected by Azure Backup Standard policy) to Trusted Launch VM requires first [switching to Enhanced policy](backup-azure-vm-migrate-enhanced-policy.md).
 [Back up confidential VMs](../confidential-computing/confidential-vm-overview.md) | Unsupported. <br><br>    Note that the following limited preview support scenarios are discontinued and currently not available: <br><br> - Backup of Confidential VMs with no confidential disk encryption.   <br> - Backup of Confidential VMs with confidential OS disk encryption through a platform-managed key (PMK).
 Backup of VMs with SSE and CMK encryption using HSM | Supported. <br><br> You must assign the permissions get, wrap, and unwrap key to the Key Vault to User-assigned managed identity.
 

articles/backup/sap-hana-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: SAP HANA Backup support matrix
 description: In this article, learn about the supported scenarios and limitations when you use Azure Backup to back up SAP HANA databases on Azure VMs.
 ms.topic: reference
-ms.date: 06/05/2025
+ms.date: 06/10/2025
 ms.custom: references_regions 
 ms.service: azure-backup
 author: jyothisuri
@@ -22,7 +22,7 @@ Azure Backup supports the backup of SAP HANA databases to Azure. This article su
 | -------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
 | **Topology**               | SAP HANA running in Azure Linux  VMs only                    | HANA Large Instances (HLI)                                   |
 | **Regions**                   | **Americas** – Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, Canada Central, Canada East, Brazil South <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India, China East, China East 2, China East 3, China North, China North 2, China North 3 <br> **Europe** – West Europe, North Europe, France Central, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South <br> **Africa / ME** - South Africa North, South Africa West, UAE North, UAE Central  <BR>  **Azure Government regions** | France South, Germany Central, Germany Northeast, US Gov IOWA |
-| **OS versions**            | SLES 12 with SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, SP5, and SP6 <br><br>  RHEL 7.4, 7.6, 7.7, 7.9, 8.1, 8.2, 8.4, 8.6, 8.8, 9.0, 9.2, and 9.4.               |                                             |
+| **OS versions**            | SLES 12 with SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, SP5, and SP6 <br><br>  RHEL 7.4, 7.6, 7.7, 7.9, 8.1, 8.2, 8.4, 8.6, 8.8, 8.10, 9.0, 9.2, and 9.4.               |                                             |
 | **HANA versions**          | SDC on HANA 1.x, MDC on HANA 2.x SPS 04, SPS 05 Rev <= 59, SPS 06 (validated for encryption enabled scenarios as well), SPS 07, and SPS 08.      |                                                            |
 | **Encryption** | SSLEnforce, HANA data encryption |            |
 | **HANA Instances**         | - A single SAP HANA instance on a  single Azure VM – scale up only. <br><br> - Multiple SAP HANA instances on a  single VM. You can protect only one of these multiple instances at a time. |                            |

articles/cost-management-billing/manage/direct-ea-azure-usage-charges-invoices.md

@@ -28,6 +28,9 @@ To view detailed usage for specific accounts, download the usage detail report.
 
 Enterprise Administrators and partner administrators can view historical data usage for terminated enrollments just as they do for active ones using the following information.
 
+> [!NOTE]
+> Old Partner can access their usage details for up to 120 days after their participation in the agreement has ended.
+
 As an enterprise administrator:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).