Merge pull request #305100 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-05 05:00 UTC

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

articles/app-service/deploy-azure-pipelines.md

@@ -157,7 +157,7 @@ FasAPI already contains OpenAPI functionality at the default path `/openapi.json
     - "Create a restaurant. Use your imagination for the details."
     - "I didn't like the food at this restaurant. Please create a 2 star review."
 
-    :::image type="content" source="media/tutorial-ai-integrate-azure-ai-agent-python/agents-playground.png" alt-text="Screenshot showing the agents playground in the middle of a conversation that takes actions by using the OpenAPI tool.":::
+    :::image type="content" source="media/tutorial-ai-integrate-azure-ai-agent-python/agents-playground.png" alt-text="Screenshot showing the agents playground in the middle of a conversation that takes actions by using the OpenAPI tool. The prompt says to create a restaurant.":::
 
 ## Security best practices
 

articles/app-service/tutorial-ai-integrate-azure-ai-agent-python.md

@@ -19,6 +19,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
 ## September 2025
 
+* [Azure NetApp Files datastore support in Azure VMware Solution Generation 2](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md)
+
+  [Azure NetApp Files datastore](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md) is now supported in [Azure VMware Solution (AVS) Generation 2](../azure-vmware/native-introduction.md). AVS Generation 2 private clouds are deployed inside an Azure virtual network. This means that ExpressRoute is no longer needed to connect the Azure VMware Solution to Azure NetApp Files datastores. This deployment simplifies networking architecture, enhances data transfer speeds, reduces latency for workloads, and improves performance when accessing other Azure services. This capability is supported in all regions where Azure VMware Solution Generation 2 and Azure NetApp Files are available.
+
 * [Azure NetApp Files migration assistant](migrate-volumes.md) is now generally available (GA)
 
     Azure NetApp Files [migration assistant](migrate-data.md) enables you to accelerate and simplify migrations of business-critical applications and data to Azure. Migration assistant offers efficient and cost-effective data migration, leveraging ONTAP's built-in replication engine for seamless transition from on-premises storage or Cloud Volumes ONTAP to Azure NetApp Files. It's a storage-efficient data transfer that reduces network transfer costs for both baseline and incremental updates. Migration assistant also offers a low cutover/downtime window, ensuring faster and more efficient final updates, minimizing disruption to operations. Volume migration using migration assistant includes source volume snapshots for primary data protection, and directory and file metadata maintaining security attributes.

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

@@ -3,7 +3,7 @@ title: Attach Azure NetApp Files datastores to Azure VMware Solution hosts
 description: Learn how to create Azure NetApp Files-based NFS datastores for Azure VMware Solution hosts.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 09/02/2025
+ms.date: 09/04/2025
 ms.custom: "references_regions, engagement-fy23"
 # Customer intent: "As an IT administrator, I want to attach Azure NetApp Files NFS datastores to Azure VMware Solution hosts, so that I can optimize storage performance and manage virtual machine workloads effectively in a cloud environment."
 ---
@@ -16,18 +16,22 @@ ms.custom: "references_regions, engagement-fy23"
 
 By using NFS datastores backed by Azure NetApp Files, you can expand your storage instead of scaling the clusters. You can also use Azure NetApp Files volumes to replicate data from on-premises or primary VMware vSphere environments for the secondary site. 
 
-Create your Azure VMware Solution and create Azure NetApp Files NFS volumes in the virtual network connected to it using an ExpressRoute. Ensure there's connectivity from the private cloud to the NFS volumes created. Use those volumes to create NFS datastores and attach the datastores to clusters of your choice in a private cloud. As a native integration, you need no other permissions configured via vSphere.
+You create your Azure VMware Solution and Azure NetApp Files NFS volumes in a virtual network. For Azure VMware Solution Generation 1 private clouds, the ExpressRoute is required for connectivity between the clusters and the Azure NetApp Files volumes. For Azure VMware Solution Generation 2 private clouds, Azure NetApp Files volumes can use the same virtual network or a virtual network that is peered with the virtual network of your private cloud. Ensure there's connectivity from the private cloud to the NFS volumes created. Use those volumes to create NFS datastores and attach the datastores to clusters of your choice in a private cloud. As a native integration, you don't need other permissions configured via vSphere.
 
-The following diagram demonstrates a typical architecture of Azure NetApp Files backed NFS datastores attached to an Azure VMware Solution private cloud via ExpressRoute.
+This diagram shows the typical architecture of Azure NetApp Files backed NFS datastores attached to Azure VMware Solution Generation 1. 
 
-:::image type="content" source="media/attach-netapp-files-to-cloud/architecture-netapp-files-nfs-datastores.png" alt-text="Diagram shows the architecture of Azure NetApp Files backed NFS datastores attached to an Azure VMware Solution private cloud." lightbox="media/attach-netapp-files-to-cloud/architecture-netapp-files-nfs-datastores.png"::: 
+:::image type="content" source="media/attach-netapp-files-to-cloud/architecture-netapp-files-generation-one.png" alt-text="Diagram shows the architecture of Azure NetApp Files backed NFS datastores attached to an Azure VMware Solution Generation 1 private cloud." lightbox="media/attach-netapp-files-to-cloud/architecture-netapp-files-generation-one.png"::: 
 
->[!Note]
+This diagram shows the typical architecture of Azure NetApp Files backed NFS datastores attached to Azure VMware Solution Generation 2.
+
+:::image type="content" source="media/attach-netapp-files-to-cloud/architecture-netapp-files-generation-two.png" alt-text="Diagram shows the architecture of Azure NetApp Files backed NFS datastores attached to an Azure VMware Solution Generation 2 private cloud." lightbox="media/attach-netapp-files-to-cloud/architecture-netapp-files-generation-two.png"::: 
+
+>[!NOTE]
 > NFS traffic from the ESXi hosts does not traverse any NSX components. Traffic traverses the ESXi VMkernel port directly to the NFS mount via the Azure network. 
 
 ## Prerequisites
 
-Before you begin the prerequisites, review the [Performance best practices](#performance-best-practices) section to learn about optimal performance of NFS datastores on Azure NetApp Files volumes.
+Before you begin, review the [Performance best practices](#performance-best-practices) section to learn about optimal performance of NFS datastores on Azure NetApp Files volumes.
 
 >[!IMPORTANT]
 >As of September 2025, creating and deleting a datastore in Azure VMware Solution and changing the service level of an Azure NetApp Files datastore requires appropriate permissions. If you're using built-in roles such as Owner and Contributor across the these two services, no changes are necessary. If you're using custom roles, ensure you have the correct permissions configured.
@@ -50,12 +54,13 @@ Before you begin the prerequisites, review the [Performance best practices](#per
 >For information about creating and modifying custom roles, see [create or update Azure custom roles using the Azure portal](../role-based-access-control/custom-roles-portal.md).
 </details>
 
-
-1. [Deploy Azure VMware Solution](./deploy-azure-vmware-solution.md) private cloud and a dedicated virtual network connected via ExpressRoute gateway. The virtual network gateway should be configured with the Ultra performance or ErGw3Az SKU and have FastPath enabled. For more information, see [Configure networking for your VMware private cloud](tutorial-configure-networking.md) and [Network planning checklist](tutorial-network-checklist.md).
+1. [Deploy Azure VMware Solution](./deploy-azure-vmware-solution.md) private cloud.
+    * **Gen 1**: [Deploy Azure VMware Solution Gen 1](./deploy-azure-vmware-solution.md) private cloud and a dedicated virtual network connected via ExpressRoute gateway. The virtual network gateway should be configured with the Ultra performance or ErGw3Az SKU and have FastPath enabled. For more information, see [Configure networking for your VMware private cloud](tutorial-configure-networking.md) and [Network planning checklist](tutorial-network-checklist.md).
+    * **Gen 2**: For [deploying a Azure VMware Solution Gen 2](./native-create-azure-vmware-virtual-network-private-cloud.md) private cloud, use a subnet in the virtual network provisioned as part of the deployment process or use a subnet in a dedicated virtual network for Azure NetApp Files that is peered with the private cloud's virtual network.
 1. Create an [NFSv3 volume for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-create-volumes.md) in the same virtual network created in the previous step.
     1. Verify connectivity from the private cloud to Azure NetApp Files volume by pinging the attached target IP.
     1. Based on your performance requirements, select the correct service level needed for the Azure NetApp Files capacity pool. Select option **Azure VMware Solution Datastore** listed under the **Protocol** section.
-    1. Create a volume with **Standard** [network features](../azure-netapp-files/configure-network-features.md) if available for ExpressRoute FastPath connectivity.
+    1. Create a volume with **Standard** [network features](../azure-netapp-files/configure-network-features.md).
     1. Under the **Protocol** section, select **Azure VMware Solution Datastore** to indicate the volume is created to use as a datastore for Azure VMware Solution private cloud.
     1. If you're using [export policies](../azure-netapp-files/azure-netapp-files-configure-export-policy.md) to control access to Azure NetApp Files volumes, enable the Azure VMware private cloud IP range, not individual host IPs. Faulty hosts in a private cloud could get replaced. If the IP isn't enabled, connectivity to datastore is impacted.
 
@@ -101,25 +106,29 @@ Azure NetApp Files datastores for Azure VMware Solution are currently supported
 
 Azure NetApp Files datastores for Azure VMware Solution are currently supported in the following host types:
 
+For Azure VMware Solution Gen1:
 * AV36 
 * AV36P
 * AV48
 * AV52
 * AV64
 
+For Azure VMware Solution Gen 2:
+* AV64
+
 ## Performance best practices
 
 There are some important best practices to follow for optimal performance of NFS datastores on Azure NetApp Files volumes.
 
-- Create Azure NetApp Files volumes using **Standard** network features to enable optimized connectivity from Azure VMware Solution private cloud via ExpressRoute FastPath connectivity.
-- For optimized performance, choose either **UltraPerformance** gateway or **ErGw3Az** gateway, and enable [FastPath](../expressroute/expressroute-howto-linkvnet-arm.md#configure-expressroute-fastpath) from a private cloud to Azure NetApp Files volumes virtual network. View more detailed information on gateway SKUs at [About ExpressRoute virtual network gateways](../expressroute/expressroute-about-virtual-network-gateways.md).
+- Create Azure NetApp Files volumes using **Standard** network features to enable optimized connectivity from Azure VMware Solution private cloud.
+- For optimized performance with Azure VMware Solution Generation&nbsp;1, choose either **UltraPerformance** gateway or **ErGw3Az** gateway and enable [FastPath](../expressroute/expressroute-howto-linkvnet-arm.md#configure-expressroute-fastpath) from a private cloud to Azure NetApp Files volumes virtual network. View more detailed information on gateway SKUs at [About ExpressRoute virtual network gateways](../expressroute/expressroute-about-virtual-network-gateways.md).
 - Based on your performance requirements, select the correct service level needed for the Azure NetApp Files capacity pool. See [Service levels for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-service-levels.md) to understand the throughput allowed per provisioned TiB for each service level. 
 
     >[!IMPORTANT]
     > If you've changed the Azure NetApp Files volumes performance tier or the volume size after creating the volume and datastore, see [Service level change for Azure NetApp files datastore](#service-level-change-for-azure-netapp-files-datastore) to ensure that volume/datastore metadata is in sync to avoid unexpected behavior in the portal or the API due to metadata mismatch. To do any kind of change to the volume you can use Azure Portal or any other supported solution (CLI\Powershell\API).
     
-- Create one or more volumes based on the required throughput and capacity. See [Performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) for Azure NetApp Files to understand how volume size, service level, and capacity pool QoS type determines volume throughput. For assistance calculating workload capacity and performance requirements, contact your Azure VMware Solution or Azure NetApp Files field expert. The default maximum number of Azure NetApp Files datastores is 8, but it can be increased to a maximum of 256 by submitting a support ticket. To submit a support ticket, see [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
--  Ensure that the Azure VMware Solution private cloud and the Azure NetApp Files volumes are deployed within the same [availability zone](../reliability/availability-zones-overview.md) using the [the availability zone volume placement](../azure-netapp-files/manage-availability-zone-volume-placement.md) in the same subscription. Information regarding your AVS private cloud's availability zone can be viewed from the overview pane within the AVS private cloud.
+- Create one or more volumes based on the required throughput and capacity. See [Performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) for Azure NetApp Files to understand how volume size, service level, and capacity pool QoS type determines volume throughput. For assistance calculating workload capacity and performance requirements, contact your Azure VMware Solution or Azure NetApp Files field expert. The default maximum number of Azure NetApp Files datastores is 8, but it can be increased to 256 by submitting a support ticket. To submit a support ticket, see [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request).
+-  Ensure that the Azure VMware Solution private cloud and the Azure NetApp Files volumes are deployed within the same [availability zone](../reliability/availability-zones-overview.md) using the [availability zone volume placement](../azure-netapp-files/manage-availability-zone-volume-placement.md) in the same subscription. Information regarding your AVS private cloud's availability zone can be viewed from the overview pane within the AVS private cloud.
 
 For performance benchmarks that Azure NetApp Files datastores deliver for VMs on Azure VMware Solution, see [Azure NetApp Files datastore performance benchmarks for Azure VMware Solution](../azure-netapp-files/performance-benchmarks-azure-vmware-solution.md).  
 
@@ -159,7 +168,7 @@ Under **Manage**, select **Storage**.
 
 1. Verify the protocol is NFS. You need to verify the virtual network and subnet to ensure connectivity to the Azure VMware Solution private cloud.
 1. Under **Associated cluster**, in the **Client cluster** field, select one or more clusters to associate the volume as a datastore.
-1. Under **Data store**, create a personalized name for your **Datastore name**.
+1. Under **Datastore**, create a personalized name for your **Datastore name**.
     1. When the datastore is created, you should see all of your datastores in the **Storage**.
     2. Notice that the NFS datastores are added in vCenter Server.
 

articles/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md

@@ -11,4 +11,4 @@ ms.author: chachachachami
 > The deprecation of the MedTech service was initiated 3 May 2025.
 > If using a MedTech service is no longer a priority, deprovision your instance, which can be found [here](https://ms.portal.azure.com/#browse/Microsoft.HealthcareApis%2Fworkspaces%2Fiotconnectors).
 > Support for active instances in the following regions will end 3 May 2028: West US2, UK South, West Europe, East US, Australia East, East US 2, Central India, North Europe. 
-> The Open Source version of the MedTech service can be found [here](https://learn.microsoft.com/azure/healthcare-apis/iot/git-projects#medtech-service-github-projects).
+> The Open Source version of the MedTech service can be found [here](../iot/git-projects.md#medtech-service-github-projects).

articles/azure-vmware/media/attach-netapp-files-to-cloud/architecture-netapp-files-generation-one.png

@@ -6,7 +6,7 @@ ms.service: azure-logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: concept-article
-ms.date: 07/18/2025
+ms.date: 09/03/2025
 ---
 
 # Differences between Standard single-tenant logic apps versus Consumption multitenant logic apps
@@ -311,6 +311,8 @@ For the **Standard** logic app workflow, the following capabilities are differen
 
 * **Terraform templates**: You can't use these templates with a **Standard** logic app resource for complete infrastructure deployment. For more information, see [What is Terraform on Azure](/azure/developer/terraform/overview)?
 
+* **Incoming client certificate**: **Standard** logic apps don't support incoming client certificates, and no client certificate setting exists for the logic app in the Azure portal. If you use ARM template deployment, make sure that you don't enable client certificates.
+
 <a name="firewall-permissions"></a>
 
 ## Strict network and firewall traffic permissions