Merge pull request #4691 from kabharati/patch-82

Revise Premium SSD v2 documentation for clarity

Author: prmerger-automator[bot]

articles/postgresql/compute-storage/concepts-storage-premium-ssd-v2.md

@@ -55,31 +55,30 @@ To learn more, see [Compute options in Azure Database for PostgreSQL](concepts-c
 
 ## Supported features
 
-Premium SSD v2 supports *High Availability, Geo-Redundant backups, Geo Replicas, Major Version Upgrade and, Geo DR(Disaster Recovery)* features for Azure Database for PostgreSQL – Flexible Server in below supported regions.
+Premium SSD v2 supports *High Availability, Geo-Redundant backups, Geo Replicas, Major Version Upgrade Customer Managed Keys and, Geo DR(Disaster Recovery)* features for Azure Database for PostgreSQL – Flexible Server in below supported regions.
 
-Australia Central 2*, Australia East, Australia South East, Brazil South*, Canada Central, Canada East, Central India*, Central US, East Asia, East US, East US 2, Germany West Central*, Indonesia Central*, Israel Central*, Italy North*, Japan East, Korea Central*, Mexico Central*, New Zealand North*, North Central US, North Europe, Norway East, Norway West, Poland Central*, South African North*, Southeast Asia, Sweden Central*, Switzerland North*, UAE North*, UK South, UK West, US South Central US, West Central US, West Europe, West US, West US 2, and West US 3* regions.
+Australia Central 2*, Australia East, Australia South East, Austria East, Brazil South*, Brazil Southeast*  Canada Central, Canada East, Central India, Central US, East Asia, East US, East US 2, France Central*  Germany West Central, Germany North, Indonesia Central*, Israel Central*, Italy North*, Japan East, Japan West, Korea Central*, Malaysia West*, Mexico Central*, New Zealand North*, North Central US, North Europe, Norway East, Norway West, Poland Central*, South Africa North, South Africa West, Southeast Asia, Spain Central*, Sweden Central*, Switzerland North, Switzerland West, South India, UAE North*, UK South, UK West, US South Central US, West Central US, West Europe, West US, West US 2, and West US 3* regions.
 
 Sovereign regions such as China North 3 and US Gov Virginia support standalone SSDv2 deployments only and currently don't support the features listed above. 
 
-Customer Managed Keys is available in following regions Central India, Central US, East Asia, East US, East US2, France Central, Japan West, New Zealand North, North Europe, South Central US, Southeast Asia, West Europe, West US 2.
-
 > [!NOTE]  
 >  Geo‑redundant backups are currently unavailable in the region marked with* because one of the paired regions doesn't support native SSDv2 storage or the region doesn't have an Azure paired region. Additionally, if SSDv2 is unavailable in a region, disable the High Availability option to enable SSDv2 storage.
 
 
 ### Limitations and Considerations
 
- - Online Disk Scaling, On-demand Backups, Long Term Backups, and storage autogrow features aren't supported for Premium SSD v2.
+ - Long‑term backups, storage autogrow, and PostgreSQL version 13 are currently not supported with Premium SSD v2.
 
 - You can provision Premium SSD v2 by using General Purpose and Memory Optimized compute tiers only. Creating new Burstable compute tier with Premium SSD v2 isn't supported.
 
 - You can adjust disk performance settings (IOPS or throughput) up to four times within a 24-hour period. For newly created disks, the limit is three adjustments during the first 24 hours.
 
-- For larger servers, the initial automated backup may take a little longer to complete and will appear in the Azure portal once it finishes. This is expected behavior while the service completes the first full backup.
-  No action is required during this time. We recommend waiting for the first backup to complete before performing any backup‑dependent operations. After the initial backup is completed, all subsequent backups are      incremental and typically complete quickly.
+- For larger servers, the initial automated backup may take longer to complete and will appear in the Azure portal once it finishes. This is expected behavior while the service completes the first full backup. No action is required during this time. We recommend waiting for the initial backup to complete before performing any backup‑dependent operations, such as creating in‑region read replicas. After the initial backup, all subsequent backups are incremental and typically complete quickly.
+
 
+- Online migration from Premium SSD to Premium SSD v2 is not supported. To migrate between these storage types, you can either perform a [point-in-time-restore](../backup-restore/concepts-backup-restore.md#point-in-time-recovery) from a Premium SSD server to a new server using Premium SSD v2, or create a read replica from Premium SSD to Premium SSD V2 server. Because storage autogrow is not currently supported on Premium SSD v2, you must disable storage autogrow on the source Premium SSD server before starting the migration.
 
-- Online migration from Premium SSD (PV1) to Premium SSD v2 (PV2) isn't supported. As an alternative, if you want to migrate across the different storage types, you can perform a [point-in-time-restore](../backup-restore/concepts-backup-restore.md#point-in-time-recovery) of Premium SSD (v1) server to a new one with Premium SSD v2 storage type. Because storage autogrow isn't currently supported on Premium SSD v2, you must disable the storage autogrow setting before migrating from Premium SSD (v1) to Premium SSD v2 (v2).
+ - Replication from Premium SSD to Premium SSD v2 is supported only for migration scenarios.It is not supported for ongoing operations, as Premium SSD cannot keep pace with Premium SSD v2 performance and may introduce latency issues.
 
 - If you perform any operation that requires disk hydration following error might occur. This error occurs because Premium SSD v2 disks don't support any operation while the disk is still hydrating.