Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us424071-nat-qs-combo

Author: asudbring

articles/iot-operations/deploy-iot-ops/overview-deploy.md

@@ -5,7 +5,7 @@ author: SoniaLopezBravo
 ms.author: sonialopez
 ms.topic: conceptual
 ms.custom:
-ms.date: 11/06/2024
+ms.date: 04/28/2025
 
 #CustomerIntent: As an IT professional, I want to understand the components and deployment details before I start using Azure IoT Operations.
 ---
@@ -106,7 +106,7 @@ If you use enterprise firewalls or proxies to manage outbound traffic, configure
 
   |Endpoints (DNS) | Description |
   |-|-|
-  | `<customer-specific>.blob.storage.azure.net` | Storage for schema registry. Refer to [storage account endpoints](/azure/storage/common/storage-account-overview#storage-account-endpoints) for identifying the customer specific subdomain of your endpoint. |
+  | `<customer-specific>.blob.core.windows.net` | Storage for schema registry. Refer to [storage account endpoints](/azure/storage/common/storage-account-overview#storage-account-endpoints) for identifying the customer specific subdomain of your endpoint. |
 
 * To push data to the cloud, enable the following endpoints based on your choice of data platform.
 

articles/reliability/regions-paired.md

@@ -24,7 +24,7 @@ You can design a highly resilient solution whether you use paired regions, nonpa
 
 Some Azure services use paired regions to build their multi-region geo-replication and geo-redundancy strategy. For example, [Azure geo-redundant storage](../storage/common/storage-redundancy.md#geo-redundant-storage) (GRS) can automatically replicate data to a paired region.
 
-If you're in a region with a pair, then using its pair as a secondary region provides several benefits:
+If you're in a region that's paired, then using its pair as a secondary region provides several benefits:
 
 - **Region recovery sequence**. In the unlikely event of a geography-wide outage, the recovery of one region is prioritized out of every region pair. Components that are deployed across paired regions have one of the regions prioritized for recovery.
 - **Sequential updating**. Planned Azure system updates are staggered across region pairs to minimize the impact of bugs or logical failures in the rare event of a faulty update, and to prevent downtime to solutions that have been designed to use paired regions together for resiliency.

articles/reliability/reliability-aks.md

@@ -167,7 +167,7 @@ If you need to deploy your Kubernetes workload to multiple Azure regions, you ha
 
 Azure Backup has an extension that you can use to back up AKS cluster resources and persistent volumes that attach to the cluster. The Backup vault communicates with the AKS cluster through the extension to perform backup and restore operations.
 
-If your AKS cluster is in a [paired region](./regions-paired.md), you can configure backups to be stored in geo-redundant storage. You can restore geo-redundant backups into the paired region.
+If your AKS cluster is in a [region that's paired](./regions-paired.md), you can configure backups to be stored in geo-redundant storage. You can restore geo-redundant backups into the paired region.
 
 For more information, see the following articles:
 

articles/reliability/reliability-community-training.md

@@ -81,7 +81,7 @@ The Microsoft Community Training team manages the entire disaster recovery proce
 
 
 >[!NOTE]
-> RTO depends on database and storage size, latency between the paired region. Database or storage VM capacity (SKU). RPO depends on underlying Azure resources, such as [Azure SQL](/azure/azure-sql/database/recovery-using-backups?view=azuresql&tabs=azure-portal&preserve-view=true#geo-restore-considerations) and Azure storage. For more information on RTO and RPO, see [What are business continuity, high availability, and disaster recovery?](./concept-business-continuity-high-availability-disaster-recovery.md#disaster-recovery).
+> RTO depends on database and storage size, and latency between the paired regions. Database or storage VM capacity (SKU). RPO depends on underlying Azure resources, such as [Azure SQL](/azure/azure-sql/database/recovery-using-backups?view=azuresql&tabs=azure-portal&preserve-view=true#geo-restore-considerations) and Azure storage. For more information on RTO and RPO, see [What are business continuity, high availability, and disaster recovery?](./concept-business-continuity-high-availability-disaster-recovery.md#disaster-recovery).
 
 
 #### Outage detection, notification, and management

articles/reliability/reliability-fabric.md

@@ -12,7 +12,7 @@ ms.custom:
   - references_regions
   - build-2023
   - ignite-2023
-ms.date: 04/02/2025
+ms.date: 04/24/2025
 ---
 
 # Reliability in Microsoft Fabric
@@ -140,7 +140,7 @@ Fabric provides a disaster recovery switch on the capacity settings page. It's a
 :::image type="content" source="/fabric/security/media/disaster-recovery-guide/disaster-recovery-capacity-setting.png" alt-text="Screenshot of the disaster recovery tenant setting.":::
 
 > [!NOTE]
-> After turning on the disaster recovery capacity setting, it can take up to one week for the data to start replicating.
+> After enabling the disaster recovery capacity setting or creating new workspaces within the capacity, data replication may take some time to start. You can verify that replication has begun by checking if your storage for a particular workspace is billed as "OneLake BCDR Storage" in the [Microsoft Fabric Capacity Metrics app](/fabric/enterprise/metrics-app).
 
 ### Data replication