Merge pull request #312382 from eh8/copilot/update-azure-storage-branding

prmerger-automator[bot] · web-flow · commit 90664f582ece · 2026-02-26T20:37:38.000Z
Copilot/update azure storage branding
diff --git a/articles/backup/back-up-managed-disks-tutorial.md b/articles/backup/back-up-managed-disks-tutorial.md
@@ -65,7 +65,7 @@ To create a backup policy for disk backup, follow these steps:
 
 ## Configure backup
 
-- Azure Disk backup supports only the operational tier backup. Copying of backups to the vault storage tier is currently not supported. The Backup vault storage redundancy setting (LRS/GRS) doesn’t apply to the backups stored in the operational tier.              <br>         Incremental snapshots are stored in a Standard Hard Disk Drive (HDD) storage, irrespective of the selected storage type of the parent disk. For more reliability, incremental snapshots are stored on [Zone Redundant Storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage) by default in ZRS supported regions.
+- Azure Disk backup supports only the operational tier backup. Copying of backups to the vault storage tier is currently not supported. The Backup vault storage redundancy setting (LRS/GRS) doesn’t apply to the backups stored in the operational tier.              <br>         Incremental snapshots are stored in a Standard HDD storage, irrespective of the selected storage type of the parent disk. For more reliability, incremental snapshots are stored on [Zone Redundant Storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage) by default in ZRS supported regions.
 
 - Azure Disk backup supports cross-subscription (backup vault in one subscription and the source disk in another) backup and restore. Currently, cross-region backup and restore aren't supported by Azure Disk backup, that is, the backup vault and disk to back up are in different regions.      <br>        So, to use Azure Disk backup, ensure that the backup vault and disk to back up are in the same region.
 
diff --git a/articles/backup/backup-architecture.md b/articles/backup/backup-architecture.md
@@ -186,7 +186,7 @@ Back up deduplicated disks | | | ![Partially][yellow]<br/><br/> For DPM/MABS ser
 Azure VMs use disks to store their operating system, apps, and data. Each Azure VM has at least two disks: a disk for the operating system and a temporary disk. Azure VMs can also have data disks for app data. Disks are stored as VHDs.
 
 - VHDs are stored as page blobs in standard or premium storage accounts in Azure:
-  - **Standard storage:** Reliable, low-cost disk support for VMs running workloads that aren't sensitive to latency. Standard storage can use standard solid-state drive (SSD) disks or standard hard disk drive (HDD) disks.
+  - **Standard storage:** Reliable, low-cost disk support for VMs running workloads that aren't sensitive to latency. Standard storage can use Standard SSDs or Standard HDDs.
   - **Premium storage:** High-performance disk support. Uses Premium SSDs.
 - There are different performance tiers for disks:
   - **Standard HDD:** Backed by HDDs, and used for cost-effective storage.
diff --git a/articles/backup/backup-azure-vms-enhanced-policy.md b/articles/backup/backup-azure-vms-enhanced-policy.md
@@ -16,11 +16,11 @@ Azure Backup now supports the Enhanced policy for Azure virtual machine (VM) bac
 
 - Zone resiliency by using zone-redundant storage for Instant Restore snapshots.
 - Multiple backups per days. You can schedule backups as frequently as every 4 hours for Azure VMs.
-- Support for new Azure offerings, including Trusted Launch VMs, Premium solid-state drive (SSD) v2 and Ultra SSD disks, and multidisk crash-consistent snapshot support.
+- Support for new Azure offerings, including Trusted Launch VMs, Premium SSD v2 and Ultra Disks, and multidisk crash-consistent snapshot support.
 - Longer retention in snapshot (operational) tier up to 30 days.
 
 >[!Note]
->- The Standard policy doesn't support protecting newer Azure offerings, such as Ultra SSD and Premium SSD v2. Only the Azure CLI (version 2.73.0 and later), PowerShell (version Az 14.0.0 and later), and the REST API (version 2025-01-01 and later) support Trusted Launch VM backup with the Standard policy.
+>- The Standard policy doesn't support protecting newer Azure offerings, such as Ultra Disk and Premium SSD v2. Only the Azure CLI (version 2.73.0 and later), PowerShell (version Az 14.0.0 and later), and the REST API (version 2025-01-01 and later) support Trusted Launch VM backup with the Standard policy.
 >- Backups for VMs fail for disks enabled with data access authentication.
 >- Protection of a VM with an enhanced policy incurs more snapshot costs. [Learn more about cost impact](backup-instant-restore-capability.md#cost-impact).
 >- Backup doesn't allow changing the policy type to Standard after you enable a VM backup with the Enhanced policy.
diff --git a/articles/backup/backup-instant-restore-capability.md b/articles/backup/backup-instant-restore-capability.md
@@ -19,7 +19,7 @@ Instant Restore provides the following capabilities:
 * Uses snapshots taken as part of a backup job that's available for recovery without waiting for data transfer to the vault to finish. It reduces the wait time for snapshots to copy to the vault before triggering restore.
 * Reduces backup and restore times by retaining snapshots locally for 2 days with the Standard policy and 7 days with the Enhanced policy, by default. You can configure this default snapshot retention value from 1 to 5 days for the Standard policy and from 1 to 30 days for the Enhanced policy.
 * Supports disk sizes up to 32 TB. Don't use Azure Backup to resize disks.
-* Supports Standard solid-state drive (SSD) disks along with Standard hard-disk drive (HDD) disks and Premium SSDs with the Standard policy. Supports backup and instant restore of Premium SSD v2 and Ultra Disks, in addition to Standard HDD, Standard SSD, and Premium SSD v1 disks, with the Enhanced policy.
+* Supports Standard SSDs along with Standard HDDs and Premium SSDs with the Standard policy. Supports backup and instant restore of Premium SSD v2 and Ultra Disks, in addition to Standard HDD, Standard SSD, and Premium SSD v1 disks, with the Enhanced policy.
 * Uses an unmanaged virtual machine's (VM) original storage accounts (per disk) when restoring. This ability exists even when the VM has disks that are distributed across storage accounts. It speeds up restore operations for various VM configurations.
 * Uses unmanaged Premium disks in storage accounts for backup of VMs. We recommend that you allocate *50%* of free space of the total allocated storage space with Instant Restore. The 50% free space isn't a requirement for backups after the first backup is finished.
 
diff --git a/articles/backup/backup-managed-disks.md b/articles/backup/backup-managed-disks.md
@@ -72,7 +72,7 @@ To create a backup policy for Azure Disks, follow these steps:
 
 ## Configure Azure Disk backup
 
-- Azure Disk backup supports only the operational tier backup. Copying of backups to the vault storage tier is currently not supported. The Backup vault storage redundancy setting (LRS/GRS) doesn’t apply to the backups stored in the operational tier.              <br>         Incremental snapshots are stored in a Standard Hard Disk Drive (HDD) storage, irrespective of the selected storage type of the parent disk. For more reliability, incremental snapshots are stored on [Zone Redundant Storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage) by default in ZRS supported regions.
+- Azure Disk backup supports only the operational tier backup. Copying of backups to the vault storage tier is currently not supported. The Backup vault storage redundancy setting (LRS/GRS) doesn’t apply to the backups stored in the operational tier.              <br>         Incremental snapshots are stored in a Standard HDD storage, irrespective of the selected storage type of the parent disk. For more reliability, incremental snapshots are stored on [Zone Redundant Storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage) by default in ZRS supported regions.
 
 - Azure Disk backup supports cross-subscription (backup vault in one subscription and the source disk in another) backup and restore. Currently, cross-region backup and restore aren't supported by Azure Disk backup, that is, the backup vault and disk to back up are in different regions.      <br>        So, to use Azure Disk backup, ensure that the backup vault and disk to back up are in the same region.
 
diff --git a/articles/backup/sap-hana-database-about.md b/articles/backup/sap-hana-database-about.md
@@ -96,7 +96,7 @@ Azure Backup, now supports backing up a "Scale-out" HANA system distributed acro
 
 #### Managed disk snapshot
 
-Azure Backup uses managed disk snapshots. Azure Backup stores them in a resource group that you specify. Managed disk snapshots use standard hard disk drive (HDD) storage, irrespective of the storage type of the disk, and you're charged according to [Managed disk snapshot pricing](https://azure.microsoft.com/pricing/details/managed-disks/). The first disk snapshot is a full snapshot, and all subsequent snapshots are incremental and consist only of the changes since the last one. 
+Azure Backup uses managed disk snapshots. Azure Backup stores them in a resource group that you specify. Managed disk snapshots use Standard HDD storage, irrespective of the storage type of the disk, and you're charged according to [Managed disk snapshot pricing](https://azure.microsoft.com/pricing/details/managed-disks/). The first disk snapshot is a full snapshot, and all subsequent snapshots are incremental and consist only of the changes since the last one. 
 
 >[!Note]
 >There are no backup storage costs for snapshots, because they're *not* transferred to your Recovery Services vault.
diff --git a/articles/cost-management-billing/reservations/understand-disk-reservations.md b/articles/cost-management-billing/reservations/understand-disk-reservations.md
@@ -33,7 +33,7 @@ The following scenarios describe what happens if you underuse, overuse, or tier
 
 ### Underusing your capacity
 
-Suppose you deploy only 99 of your 100 reserved Azure premium solid-state drive (SSD) P30 disks for an hour within the reservation period. The remaining P30 disk isn't applied during that hour. It also doesn't carry over.
+Suppose you deploy only 99 of your 100 reserved Azure Premium SSD P30 disks for an hour within the reservation period. The remaining P30 disk isn't applied during that hour. It also doesn't carry over.
 
 ### Overusing your capacity
 
diff --git a/articles/cyclecloud/how-to/add-disk.md b/articles/cyclecloud/how-to/add-disk.md
@@ -35,7 +35,7 @@ This volume is created the first time the instance starts but isn't deleted when
 ## Disk types
 
 ::: moniker range="=cyclecloud-7"
-There are four [Azure disk types](/azure/virtual-machines/linux/disks-types). CycleCloud uses standard hard disk drives (HDD) by default. To use a more performant SSD drive for the disk, set `SSD` to `true`:
+There are four [Azure disk types](/azure/virtual-machines/linux/disks-types). CycleCloud uses Standard HDDs by default. To use a more performant SSD drive for the disk, set `SSD` to `true`:
 
 ``` ini
 [[[volume example-vol]]]
diff --git a/articles/lab-services/administrator-guide-1.md b/articles/lab-services/administrator-guide-1.md
@@ -283,7 +283,7 @@ Creating a shared image gallery and attaching it to your lab account is free. No
 
 #### Storage charges
 
-To store image versions, a shared image gallery uses standard hard disk drive (HDD) managed disks by default. We recommend using HDD-managed disks when using shared image gallery with Lab Services. The size of the HDD-managed disk that's used depends on the size of the image version that's being stored. Lab Services supports image and disk sizes up to 128 GB. To learn about pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
+To store image versions, a shared image gallery uses Standard HDD managed disks by default. We recommend using HDD-managed disks when using shared image gallery with Lab Services. The size of the HDD-managed disk that's used depends on the size of the image version that's being stored. Lab Services supports image and disk sizes up to 128 GB. To learn about pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
 
 #### Replication and network egress charges
 
diff --git a/articles/lab-services/administrator-guide.md b/articles/lab-services/administrator-guide.md
@@ -245,7 +245,7 @@ Creating a compute gallery and attaching it to your lab plan is free. No cost is
 
 #### Storage charges
 
-To store image versions, a compute gallery uses standard hard disk drive (HDD) managed disks by default. We recommend using HDD-managed disks when you use compute gallery with Lab Services. The size of the HDD-managed disk that is used depends on the size of the image version that is being stored. Lab Services supports image and disk sizes up to 128 GB. To learn about pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
+To store image versions, a compute gallery uses Standard HDD managed disks by default. We recommend using HDD-managed disks when you use compute gallery with Lab Services. The size of the HDD-managed disk that is used depends on the size of the image version that is being stored. Lab Services supports image and disk sizes up to 128 GB. To learn about pricing, see [Managed disks pricing](https://azure.microsoft.com/pricing/details/managed-disks/).
 
 Azure Lab Services doesn't support attaching extra disks to a lab template or lab VM.
 
diff --git a/articles/migrate/troubleshoot-assessment.md b/articles/migrate/troubleshoot-assessment.md
@@ -298,7 +298,7 @@ Use a different target location before migration.
 
 #### Fix
 
-One or more disks attached to the VM don't meet Azure requirements.<br><br> Azure Migrate: Discovery and assessment assess the disks based on the disk limits for Ultra Disks (64 TB).<br><br> For each disk attached to the VM, make sure that the size of the disk is < 64 TB (supported by Ultra SSD disks).<br><br> If it isn't, reduce the disk size before you migrate to Azure, or use multiple disks in Azure and [stripe them together](/azure/virtual-machines/premium-storage-performance#disk-striping) to get higher storage limits. Make sure that the performance (IOPS and throughput) needed by each disk is supported by [Azure managed virtual machine disks](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-storage-limits).
+One or more disks attached to the VM don't meet Azure requirements.<br><br> Azure Migrate: Discovery and assessment assess the disks based on the disk limits for Ultra Disks (64 TB).<br><br> For each disk attached to the VM, make sure that the size of the disk is < 64 TB (supported by Ultra Disks).<br><br> If it isn't, reduce the disk size before you migrate to Azure, or use multiple disks in Azure and [stripe them together](/azure/virtual-machines/premium-storage-performance#disk-striping) to get higher storage limits. Make sure that the performance (IOPS and throughput) needed by each disk is supported by [Azure managed virtual machine disks](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-storage-limits).
 
 ### Issue: One or more unsuitable network adapters
 
diff --git a/articles/migrate/tutorial-migrate-hyper-v.md b/articles/migrate/tutorial-migrate-hyper-v.md
@@ -158,7 +158,7 @@ After discovery is finished, you can begin the replication of Hyper-V VMs to Azu
     
     :::image type="content" source="./media/tutorial-migrate-hyper-v/trusted-vm-migrate.png" alt-text="Screenshot showing standard or trusted launch virtual machines.":::    
 
-    - If you ran an assessment for the VMs, you can apply VM sizing and disk type (Premium v2, Ultra SSD, Standard SSD, Standard HDD, or Premium Managed disks) recommendations from the assessment results. To do this step, in **Import migration settings from an Azure Migrate assessment?**, select **Yes**.
+    - If you ran an assessment for the VMs, you can apply VM sizing and disk type (Premium v2, Ultra Disk, Standard SSD, Standard HDD, or Premium Managed disks) recommendations from the assessment results. To do this step, in **Import migration settings from an Azure Migrate assessment?**, select **Yes**.
     - You can choose to migrate the Standard SSD as a [ZRS Disk](/azure/virtual-machines/disks-deploy-zrs?tabs=portal).
     - If you didn't run an assessment, or you don't want to use the assessment settings, select **No**.
     - If you selected to use the assessment, select the VM group and assessment name.
diff --git a/articles/migrate/tutorial-migrate-vmware-agent.md b/articles/migrate/tutorial-migrate-vmware-agent.md
@@ -283,7 +283,7 @@ Select VMs for migration.
    - **Availability Zone**: Specify the Availability Zone to use.
    - **Availability Set**: Specify the Availability Set to use.
 
-17. In **Disks**, specify whether the VM disks should be replicated to Azure, and select the disk type (Premium v2, Ultra SSD, Standard SSD, Standard HDD, or Premium Managed disks) in Azure. Then select **Next**.
+17. In **Disks**, specify whether the VM disks should be replicated to Azure, and select the disk type (Premium v2, Ultra Disk, Standard SSD, Standard HDD, or Premium Managed disks) in Azure. Then select **Next**.
     - You can exclude disks from replication.
     - If you exclude disks, they won't be present on the Azure VM after migration.
     - You can exclude disks if the mobility agent is already installed on that server. [Learn more](../site-recovery/exclude-disks-replication.md#exclude-limitations).
diff --git a/articles/migrate/tutorial-migrate-vmware.md b/articles/migrate/tutorial-migrate-vmware.md
@@ -120,7 +120,7 @@ Enable replication as follows:
     > [!NOTE]
     > If you want to select a different availability option for a set of virtual machines, go to step 1 and repeat the steps by selecting different availability options after starting replication for one set of virtual machines.
 
-12. In **Disks**, indicate whether the VM disks should be replicated to Azure, and specify the disk type (Premium v2, Ultra SSD, Standard SSD, Standard HDD, or Premium Managed disks) in Azure. Then select **Next**.
+12. In **Disks**, indicate whether the VM disks should be replicated to Azure, and specify the disk type (Premium v2, Ultra Disk, Standard SSD, Standard HDD, or Premium Managed disks) in Azure. Then select **Next**.
 
     :::image type="content" source="./media/tutorial-migrate-vmware/disks-inline.png" alt-text="Screenshot shows the Disks tab of the Replicate dialog box." lightbox="./media/tutorial-migrate-vmware/disks-expanded.png":::
 
diff --git a/articles/migrate/whats-new.md b/articles/migrate/whats-new.md
@@ -115,7 +115,7 @@ You can use this capability to:
 ## Update (May 2025)
 
 - General availability: Azure Migrate enhances support for [Premium SSD v2 disks](/azure/virtual-machines/disks-deploy-premium-v2?tabs=azure-cli). This offers a seamless experience to migrate their on-premises workloads to Azure and benefit from the advanced disk options that offer greater flexibility and enhanced performance of Pv2 disks in Azure. 
-- Public preview: Azure Migrate expands support for migrations with [Ultra SSD](/azure/virtual-machines/disks-enable-ultra-ssd?tabs=azure-portal). This enables customers to seamlessly migrate their on-premises workloads to Azure while taking advantage of Ultra Disk’s cutting-edge performance and scalability.
+- Public preview: Azure Migrate expands support for migrations with [Ultra Disk](/azure/virtual-machines/disks-enable-ultra-ssd?tabs=azure-portal). This enables customers to seamlessly migrate their on-premises workloads to Azure while taking advantage of Ultra Disk’s cutting-edge performance and scalability.
 - Public preview: Azure Migrate enhances resiliency by supporting migration to [ZRS Disks](/azure/virtual-machines/disks-deploy-zrs?tabs=portal) during Migration only. **Zone-Redundant Storage (ZRS)** for Azure Disks synchronously replicates data across three physically separate availability zones within a region – each with independent power, cooling, and networking – enhancing Disk availability and resiliency.
 
 - General availability: Azure Migrate now supports a simplified experience through its upgraded version of the agent-based migration stack. This stack offers a streamlined experience for customers and is set to replace the classic experience over the next three years. [Learn more](simplified-experience-for-azure-migrate.md).
diff --git a/articles/sap/workloads/businessobjects-deployment-guide-linux.md b/articles/sap/workloads/businessobjects-deployment-guide-linux.md
diff --git a/articles/sap/workloads/dbms-guide-sapase.md b/articles/sap/workloads/dbms-guide-sapase.md
diff --git a/articles/sap/workloads/high-availability-zones.md b/articles/sap/workloads/high-availability-zones.md
diff --git a/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md b/articles/sap/workloads/sap-ascs-ha-multi-sid-wsfc-azure-shared-disk.md
diff --git a/articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md b/articles/sap/workloads/sap-high-availability-guide-wsfc-shared-disk.md
diff --git a/articles/storage/container-storage/use-container-storage-with-managed-disks.md b/articles/storage/container-storage/use-container-storage-with-managed-disks.md
diff --git a/articles/storage/solution-integration/validated-partners/primary-secondary-storage/isv-file-services.md b/articles/storage/solution-integration/validated-partners/primary-secondary-storage/isv-file-services.md
