Merge pull request #304246 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-14 22:00 UTC

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

articles/application-gateway/application-load-balancing-aws-to-azure-how-to.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 05/12/2025
+ms.date: 08/14/2025
 ms.author: anfdocs 
 # Customer intent: As a cloud administrator, I want to configure cross-zone-region replication for Azure NetApp Files, so that I can ensure data accessibility and disaster recovery across multiple regions and availability zones.
 ---
@@ -17,7 +17,7 @@ Azure NetApp Files supports volume cross-zone and cross-region replication on th
 
 - Cross-zone-region replication supports creating two replication relationships for a source volume: cross-zone replication, cross-region replication, or a combination.  
 - Cross-zone-region replication volumes must abide by the same requirements and considerations as individual [cross-region and cross-zone replication](replication-requirements.md) volumes.  
-- You must break the secondary relationship before you can perform a reverse resync operation with cross-zone-region replication. For more information, see [Resync volumes after disaster recovery](cross-region-replication-manage-disaster-recovery.md#resync-replication).
+- You must break and delete the secondary relationship before you can perform a reverse resync operation with cross-zone-region replication. For more information, see [Resync volumes after disaster recovery](cross-region-replication-manage-disaster-recovery.md#resync-replication).
 - Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant.
 - Fan-out deployments are supported for two destination volumes: one source (read/write) volume and two destination volumes. 
 

articles/azure-netapp-files/cross-zone-region-replication-configure.md

@@ -21,7 +21,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 * [Flexible service level](manage-cool-access.md#register-the-feature) now supports storage with cool access (Preview)
 
-    Azure NetApp Files now supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. You must be registered for the F[Flexible service level](azure-netapp-files-set-up-capacity-pool.md) before enrolling in [the preview for the Flexible service level with cool access](manage-cool-access.md#register-the-feature). 
+    Azure NetApp Files now supports cool access for the Flexible service level, enabling you to further optimize performance and cost by automatically tiering infrequently accessed data to lower-cost Azure storage accounts. This enhancement builds on the Flexible service level's ability to decouple storage capacity and throughput, allowing precise resource alignment for diverse workloads while maintaining configured throughput levels—even with cool access enabled. These features help organizations reduce total cost of ownership without compromising performance. You must be registered for the [Flexible service level](azure-netapp-files-set-up-capacity-pool.md) before enrolling in [the preview for the Flexible service level with cool access](manage-cool-access.md#register-the-feature). 
 
 ## June 2025
 

articles/azure-netapp-files/whats-new.md

@@ -4,7 +4,7 @@ description: Learn how to connect to VMs using Bastion Developer.
 author: abell
 ms.service: azure-bastion
 ms.topic: quickstart
-ms.date: 05/27/2025
+ms.date: 08/14/2025
 ms.author: abell
 ms.custom: references_regions
 # Customer intent: As a cloud administrator, I want to connect to virtual machines securely using a browser-based solution, so that I can manage resources without exposing public IP addresses or installing additional software.
@@ -15,7 +15,7 @@ ms.custom: references_regions
 In this quickstart, you learn how to connect to VMs using Azure Bastion Developer. In just a few seconds, you can connect to virtual machines (VM) in the virtual network at no extra cost via Bastion Developer using the private IP address of the VM. The VMs you connect to don't need a public IP address, client software, agent, or a special configuration. For more information about Azure Bastion, see [What is Azure Bastion](bastion-overview.md)?
 
 > [!IMPORTANT]
-> Bastion Developer is currently only available in East Asia, West Central US, UK South, and Central US. We're working to restore service in all public regions. As a workaround, you can use the [Basic SKU](tutorial-create-host-portal.md) or the [Standard SKU](quickstart-host-portal.md) to connect to your VMs. We'll update this article periodically as Bastion Developer becomes available in more regions.
+> Bastion Developer is currently only available in East Asia, East US 2, Central US, North Central US, UK South, West Central US. We're working to restore service in all public regions. As a workaround, you can use the [Basic SKU](tutorial-create-host-portal.md) or the [Standard SKU](quickstart-host-portal.md) to connect to your VMs. We'll update this article periodically as Bastion Developer becomes available in more regions.
 
 [!INCLUDE [Bastion developer](../../includes/bastion-developer-description.md)] Virtual network peering isn't currently supported for Bastion Developer.
 

articles/bastion/quickstart-developer.md

@@ -6,7 +6,7 @@ ms.reviewer: jkinma
 ms.service: cost-management-billing
 ms.subservice: billing
 ms.topic: how-to
-ms.date: 08/12/2025
+ms.date: 08/14/2025
 ms.author: jkinma
 ---
 
@@ -418,9 +418,8 @@ Enterprise administrators and department administrators are listed as invoice se
 - **Automatic purchases** - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
 - **Management groups** – Subscriptions in management groups under a Microsoft Customer Agreement aren’t supported in Cost Management yet. Cost Management + Billing is managed with APIs and Azure portal functionality. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
 - **Export jobs** from Enterprise Agreement (EA) do not automatically migrate to Microsoft Customer Agreement (MCA). You must manually recreate export jobs under the MCA billing scope.
-    - Understand how management group scope affects cost views. EA-based views are not supported in MCA. To work around this, rebuild views using billing profile and invoice section scopes.
     - Reconfigure the Export API using Azure Commerce Toolbox or PowerShell scripts to recreate export jobs with MCA-compatible APIs.
-    - Confirm that your MCA billing scope aligns with the MCA framework. Refer to [Understand and work with scopes](../costs/understand-work-scopes.md) to learn more about the required agreement types, scopes and roles.
+    - Confirm that your MCA billing scope aligns with the MCA framework. For more details, refer to [Understand and work with scopes](../costs/understand-work-scopes.md).
     - To learn more about Exports data types and supported scopes, refer to the Understand export data types section in [this article](../costs/tutorial-improved-exports.md).
 - **Tax exemption certificates** - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 

articles/cost-management-billing/manage/mca-setup-account.md

@@ -5,7 +5,7 @@ author: KennyDay
 ms.service: cost-management-billing
 ms.subservice: microsoft-customer-agreement
 ms.topic: conceptual
-ms.date: 08/12/2025
+ms.date: 08/14/2025
 ms.author: kenday
 ms.reviewer: clionabolger
 ---
@@ -235,9 +235,8 @@ This section of the onboarding guide describes the steps you follow to migrate f
 - Automatic purchases - If used under your old EA enrollment, you need to set them up under your new Microsoft Customer Agreement.
 - **Management groups** – Subscriptions in management groups under a Microsoft Customer Agreement aren’t supported in Cost Management yet. Cost Management + Billing is managed with APIs and Azure portal functionality. For more information, see [Azure RBAC scopes](../costs/understand-work-scopes.md#azure-rbac-scopes).
 - **Export jobs** from Enterprise Agreement (EA) do not automatically migrate to Microsoft Customer Agreement (MCA). You must manually recreate export jobs under the MCA billing scope.
-    - Understand how management group scope affects cost views. EA-based views are not supported in MCA. To work around this, rebuild views using billing profile and invoice section scopes.
     - Reconfigure the Export API using Azure Commerce Toolbox or PowerShell scripts to recreate export jobs with MCA-compatible APIs.
-    - Confirm that your MCA billing scope aligns with the MCA framework. Refer to [Understand and work with scopes](../costs/understand-work-scopes.md) to learn more about the required agreement types, scopes and roles.
+    - Confirm that your MCA billing scope aligns with the MCA framework. For more details, refer to [Understand and work with scopes](../costs/understand-work-scopes.md).
     - To learn more about Exports data types and supported scopes, refer to the Understand export data types section in [this article](../costs/tutorial-improved-exports.md).
 - **Tax exemption certificates** - If your EA account has a tax exemption certificate, you need to create an Azure support request to have a support representative associate your existing tax exempt certificate to your new Microsoft Customer Agreement account. Create a support request in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).