Merge pull request #291894 from MicrosoftDocs/main

12/12/2024 AM Publish

Author: Taojunshen

articles/api-management/inject-vnet-v2.md

@@ -88,7 +88,7 @@ When you [create](get-started-create-service-instance.md) a Premium v2 instance
 
 1. In the **Create API Management service** wizard, select the **Networking** tab.
 1. In **Connectivity type**, select **Virtual network**.
-1. In **Type**, select **Internal**. 
+1. In **Type**, select **Virtual Network injection**. 
 1. In **Configure virtual networks**, select the virtual network and the delegated subnet that you want to inject. 
 1. Complete the wizard to create the API Management instance.
 

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

@@ -47,7 +47,7 @@ Using snapshot technology, you can replicate your Azure NetApp Files across desi
 - Data availability and redundancy for remote data processing and user access 
 - Efficient storage-based data replication without load on compute infrastructure 
 
-To learn more, see [How volumes and snapshots are replicated cross-region for DR](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-cross-region-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
+To learn more, see [How volumes and snapshots are replicated cross-region for DR](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
 
 ## Cross-zone replication 
 

articles/azure-netapp-files/manage-cool-access.md

@@ -28,7 +28,6 @@ The storage with cool access feature provides options for the “coolness period
 * To prevent data retrieval from the cool tier to the hot tier during sequential read operations (for example, antivirus or other file scanning operations), set the cool access retrieval policy to **Default** or **Never**. For more information, see [Enable cool access on a new volume](#enable-cool-access-on-a-new-volume).
 * After the capacity pool is configured with the option to support cool access volumes, the setting can't be disabled at the _capacity pool_ level. You can turn on or turn off the cool access setting at the _volume_ level anytime. Turning off the cool access setting at the volume level stops further tiering of data.  
 * Files moved to the cool tier remains there after you disable cool access on a volume. You must perform an I/O operation on _each_ file to return it to the warm tier. 
-* You can't use [large volumes](large-volumes-requirements-considerations.md) with cool access.
 * For the maximum number of volumes supported for cool access per subscription per region, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits).
 * Considerations for using cool access with [cross-region replication](cross-region-replication-requirements-considerations.md) and [cross-zone replication](cross-zone-replication-introduction.md):
     * The cool access setting on the destination volume is updated automatically to match the source volume whenever the setting is changed on the source volume or during authorization. The setting is also updated automatically when a reverse resync of the replication is performed, but only if the destination volume is in a cool access-enabled capacity pool. Changes to the cool access setting on the destination volume don't affect the setting on the source volume.

articles/azure-netapp-files/snapshots-introduction.md

@@ -81,7 +81,7 @@ You can use several methods to create and maintain snapshots:
     * Snapshot policies, via the [Azure portal](snapshots-manage-policy.md), [REST API](/rest/api/netapp/snapshotpolicies), [Azure CLI](/cli/azure/netappfiles/snapshot/policy), or [PowerShell](/powershell/module/az.netappfiles/new-aznetappfilessnapshotpolicy) tools
     * Application consistent snapshot tooling such as [AzAcSnap](azacsnap-introduction.md) or third-party solutions
 
-## How volumes and snapshots are replicated cross-region for disaster recovery and business continuity 
+## How volumes and snapshots are replicated for disaster recovery and business continuity 
 
 Azure NetApp Files supports [cross-region replication](cross-region-replication-introduction.md) for disaster-recovery (DR) purposes and [cross-zone replication](cross-zone-replication-introduction.md) for business continuity. Azure NetApp Files cross-region replication and cross-zone replication both use SnapMirror technology. Only changed blocks are sent over the network in a compressed, efficient format. After replication is initiated between volumes, the entire volume contents (that is, the actual stored data blocks) are transferred only once. This operation is called a *baseline transfer*. After the initial transfer, only changed blocks (as captured in snapshots) are transferred. The result is an asynchronous 1:1 replica of the source volume, including all snapshots. This behavior follows a full and incremental-forever replication mechanism. This technology minimizes the amount of data required for replication, therefore saving data transfer costs. It also shortens the replication time. You can achieve a smaller Recovery Point Objective (RPO), because more snapshots can be created and transferred more frequently with minimal data transfers. Further, it takes away the need for host-based replication mechanisms, avoiding virtual machine and software license cost.
 

articles/azure-resource-manager/management/preview-features.md

@@ -2,7 +2,7 @@
 title: Set up preview features in Azure subscription
 description: Describes how to list, register, or unregister preview features in your Azure subscription for a resource provider.
 ms.topic: how-to
-ms.date: 09/26/2024
+ms.date: 12/12/2024
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 # Customer intent: As an Azure user, I want to use preview features in my subscription so that I can expose a resource provider's preview functionality.
 ---
@@ -25,7 +25,8 @@ You can list all the preview features and their registration states for an Azure
 
 # [Portal](#tab/azure-portal)
 
-The portal only shows a preview feature when the service that owns the feature has explicitly opted in to the preview features management experience.
+> [!NOTE]
+> The portal only shows a preview feature when the service that owns the feature has explicitly opted in to the preview features management experience. In case the feature you are looking for doesn't appear on the list available, we recommend using [Azure CLI](./preview-features.md?tabs=azure-cli#list-preview-features) and [Azure Powershell](./preview-features.md?tabs=azure-powershell#list-preview-features).
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 1. In the search box, enter _subscriptions_ and select **Subscriptions**.
@@ -101,7 +102,7 @@ Name                                     RegistrationState
 Microsoft.Compute/InGuestPatchVMPreview  NotRegistered
 ```
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To list all the subscription's preview features, use the [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) cmdlet.
 
@@ -210,7 +211,7 @@ Microsoft.Compute/InGuestPatchVMPreview  Registered
 > [!NOTE]
 > When the register command runs, a message is displayed that after the feature is registered, to run `az provider register --namespace <provider-name>` to propagate the changes.
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To register a preview feature, use the [Register-AzProviderFeature](/powershell/module/az.resources/register-azproviderfeature) cmdlet.
 
@@ -306,7 +307,7 @@ Name                                     RegistrationState
 Microsoft.Compute/InGuestPatchVMPreview  Unregistered
 ```
 
-# [PowerShell](#tab/azure-powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 
 To unregister a preview feature, use the [Unregister-AzProviderFeature](/powershell/module/az.resources/unregister-azproviderfeature) cmdlet. The `RegistrationState` state changes to **Unregistered**.
 

articles/azure-vmware/azure-vmware-solution-platform-updates.md

@@ -4,7 +4,7 @@ description: Learn about the platform updates to Azure VMware Solution.
 ms.topic: reference
 ms.custom: "references_regions, engagement-fy23"
 ms.service: azure-vmware
-ms.date: 11/22/2024
+ms.date: 12/12/2024
 ---
 
 # What's new in Azure VMware Solution
@@ -17,7 +17,7 @@ Azure VMware Solution is now ready to update all existing Azure Commercial custo
 
 All new Azure VMware Solution private clouds are being deployed with VMware vSphere 8.0 version in [Microsoft Azure Government](https://azure.microsoft.com/explore/global-infrastructure/government/#why-azure). [Learn more](architecture-private-clouds.md#vmware-software-versions)
 
-Trusted Launch is now available in all Azure VMware Solution regions. This enables Virtual Trusted Platform Module (vTPM) on virtual machines, ensuring compliance with the latest security standards and unlocking the potential to run modern operating systems like Microsoft Windows 11. [Learn more](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-A43B6914-E5F9-4CB1-9277-448AC9C467FB.html)
+Trusted Launch is now available in all Azure VMware Solution regions. This enables Virtual Trusted Platform Module (vTPM) on virtual machines, ensuring compliance with the latest security standards and unlocking the potential to run modern operating systems like Microsoft Windows 11. [Learn more](configure-virtual-trusted-platform-module.md#configure-virtual-trusted-platform-module-vtpm-on-virtual-machines-with-azure-vmware-solution)
 
 ## October 2024
 

articles/azure-vmware/media/nsxt/nsx-create-tier-1.png

@@ -33,13 +33,15 @@ items:
     href: tutorial-configure-networking.md
   - name: 4 - Access a private cloud
     href: tutorial-access-private-cloud.md
-  - name: 5 - Create an NSX network segment
+  - name: 5 - Create an NSX Tier-1 Gateway
+    href: tutorial-nsx-tier-1-gateway.md
+  - name: 6 - Create an NSX network segment
     href: tutorial-nsx-t-network-segment.md
-  - name: 6 - Peer on-premises to private cloud
+  - name: 7 - Peer on-premises to private cloud
     href: tutorial-expressroute-global-reach-private-cloud.md
-  - name: 7 - Scale a private cloud
+  - name: 8 - Scale a private cloud
     href: tutorial-scale-private-cloud.md
-  - name: 8 - Delete a private cloud
+  - name: 9 - Delete a private cloud
     href: tutorial-delete-private-cloud.md
 - name: Cost optimization
   items:

articles/azure-vmware/toc.yml

@@ -0,0 +1,64 @@
+---
+title:  Tutorial - NSX-Tier-1-Gateway
+description: Learn how to create a Tier-1 Gateway
+ms.topic: tutorial
+ms.service: azure-vmware
+ms.date: 12/11/2024
+ms.custom: engagement-fy25
+---
+
+# Tutorial: Create an NSX Tier-1 Gateway 
+
+After deploying the Azure VMware Solution, you can create additional Tier-1 Gateways from the NSX Manager. Once configured, the additional Tier-1 Gateway is visible in the NSX Manager. NSX comes pre-provisioned by default with an NSX Tier-0 Gateway in **Active/Active** mode and a default Tier-1 Gateway in **Active/Standby** mode. 
+
+In this tutorial, you learn how to:
+
+> [!div class="checklist"]
+> * Create an additional NSX Tier-1 Gateway in the NSX Manager
+> * Configure the High Availability (HA) mode on a Tier-1 Gateway 
+
+## Prerequisites
+
+An Azure VMware Solution private cloud with access to the NSX Manager interface. For more information, see the [Configure networking](tutorial-configure-networking.md) tutorial. 
+
+## Use NSX Manager to create a Tier-1 Gateway
+
+A Tier-1 Gateway is typically added to a Tier-0 Gateway in the northbound direction and to segments in the southbound direction. 
+
+1. With the CloudAdmin account, sign-in to the NSX Manager.
+
+2. In NSX Manager, select **Networking** > **Tier-1 Gateways**.
+
+3. Select **Add Tier-1 Gateway**. 
+
+4. Enter a name for the gateway. 
+
+5. Select the **HA Mode** for the Tier-1 Gateway. Choose between **Active/Standby**, **Active/Active**, or **Distributed Only**:
+ 
+    | HA Mode | Description |
+    | :--------- | :------------- |
+    | Active Standby | One active instance and one standby instance. The Standby takes over is the active fails. |
+    | Active Active | Both instances are active and can handle traffic simultaneously. |
+    | Distributed Only | No centralized instances; routing is distributed across all transport nodes. |
+
+6. Select a Tier-0 Gateway to connect to this Tier-1 Gateway to create a multi-tier topology. 
+
+7. Select an NSX Edge cluster if you want this Tier-1 Gateway to host stateful services such as NAT, load balancer, or firewall. 
+
+8. After you select an NSX Edge cluster, a toggle gives you the option to select NSX Edge Nodes. 
+
+9. If you selected an NSX Edge cluster, select a failover mode or accept the default. 
+
+     | Option | Description | 
+     | :----- | :---------- |
+     | Preemptive | If the preferred NSX Edge node fails and recovers, it preempts its peer and becomes the active node. The peer changes its state to standby. |
+     | Non-preemptive  | If the preferred NSX Edge node fails and recovers, it checks if its peer is the active node. If so, the preferred node will not preempt its peer and will be the standby node. This is the default option. |
+
+:::image type="content" source="media/nsxt/nsx-create-tier-1.png" alt-text="Diagram showing the creation of a new Tier-1 Gateway in NSX Manager." border="false" lightbox="media/nsxt/nsx-create-tier-1.png":::
+
+10. Select **Save**. 
+
+## Next steps
+
+In this tutorial, you created an additional Tier-1 Gateway to use in your Azure VMware Solution private cloud. 
+

articles/azure-vmware/tutorial-nsx-tier-1-gateway.md

@@ -1,5 +1,5 @@
 ---
-title: Use a private endpoint with an Azure Container Apps environment
+title: Use a private endpoint with an Azure Container Apps environment (preview)
 description: Learn how to use a private endpoint with an Azure Container Apps environment.
 services: container-apps
 author: craigshoemaker
@@ -11,7 +11,7 @@ ms.author: cshoe
 zone_pivot_groups: azure-cli-or-portal
 ---
 
-# Use a private endpoint with an Azure Container Apps environment
+# Use a private endpoint with an Azure Container Apps environment (preview)
 
 In this article, you learn how to use a private endpoint to securely access your Azure Container App without exposing it to the public Internet.