Merge pull request #311635 from suzuber/article-refresh-lines-21-40

2025 refresh updates lines 21-40

Author: prmerger-automator[bot]

articles/azure-vmware/configure-azure-vmware-solution-metrics.md

@@ -3,7 +3,7 @@ title: Configure the latest iteration of Azure VMware Solution private cloud per
 description: Learn how to take advantage of the latest improvements made to Azure VMware Solution private cloud performance and health metrics 
 ms.topic: how-to 
 ms.service: azure-vmware
-ms.date: 10/09/2024
+ms.date: 2/12/2026
 ms.custom: engagement-fy24
 
 #Customer intent: As an Azure service administrator, I want to collect key performance and reliability metrics from my Azure VMware Solution private cloud, so I can analyze for any diagnostic purposes.
@@ -15,7 +15,7 @@ ms.custom: engagement-fy24
 
 In this article, you learn how to take advantage of the latest iteration of metrics available to monitor your Azure VMware Solution private cloud. 
 
-Azure VMware Solution provides users with an array of high-level health and performance metrics to provide visibility into the health and performance of an Azure VMware Solution private cloud. Since early 2024, another set of identical metrics labeled with the word "(new)" were introduced, where a series of enhancements to the stability, reliability, and performance of these metrics were made to provide users a better experience relative to the older set of metrics.  
+Azure VMware Solution provides users with an array of high-level health and performance metrics to provide visibility into the health and performance of an Azure VMware Solution private cloud. In 2024, a set of identical metrics labeled as "new" were introduced. The "new" metrics, which include a series of enhancements to the stability, reliability, and performance of those metrics were made to provide users a better experience relative to the older set of metrics.  
 
 
 ### View Azure VMware Solution metrics
@@ -25,21 +25,21 @@ From your Azure VMware Solution private cloud, select **Metrics** under the **Mo
 
 ### Setting up a chart
 
-Select a metric you'd like to build a chart for, such as "Percentage CPU (new)" in this example. Upon doing so, you will see a chart like the one below showing a time series for the metric you've selected.
+Select a metric you'd like to build a chart for, such as "Percentage CPU (new)" in this example. Upon doing so, you see a chart, like the following example, that shows a time series for the metric selected.
 
 :::image type="content" source="media/new-metrics/azure-vmware-solution-metrics-new-2.png" alt-text="Screenshot showing an example metric.":::
 
-You can toggle the time window you are interested in this metric for by simply selecting the time window button in the top-right corner. The default window for your selected metric will be **24 hours**.
+You can toggle the time window you're interested in for this metric by selecting the time window button in the top-right corner. The default window for your selected metric is **24 hours**.
 
-Once you are ready to save, click **Save to Dashboard** and select one of the options presented for where this metric will live.
+Once you're ready to save, select **Save to Dashboard**, then select one of the options presented for where the metric lives.
 
 ### Send metrics to other monitoring solutions using the new metrics
 
-Additionally, you can hover over each metric in the **Metric** dropdown to see the Metric ID. You can use this Metric ID in your third-party monitoring tools to monitor your Azure VMware Solution private cloud.
+Additionally, you can hover over each metric in the **Metric** dropdown to see the Metric identifier (ID). You can use this Metric ID in your third-party monitoring tools to monitor your Azure VMware Solution private cloud.
  >[!IMPORTANT]
    >We strongly encourage all users - first time and repeat - to migrate to the new metrics suffixed with **"(new)"**.
 
-For those who have used the metrics previously and have built monitoring in downstream tools and configurations that rely on the old metric IDs, the following table provides the corresponding newer metric IDs you can use for the same set of metrics to seamlessly transition to using the newer set of metrics:
+Several customers previously used the metrics to build monitoring in downstream tools and configurations that rely on the old metric IDs. The following table provides corresponding, newer metric IDs you can use for the same set of metrics to seamlessly transition to using the newer set of metrics:
 
 | Metric Name (as viewed in the portal) | Current Metric ID | New Metric ID | 
 | :---     | :---      | :---     |

articles/azure-vmware/configure-dns-azure-vmware-solution.md

@@ -3,7 +3,7 @@ title: Configure DNS forwarder for Azure VMware Solution
 description: Learn how to configure DNS forwarder for Azure VMware Solution using the Azure portal.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 2/27/2024
+ms.date: 2/10/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
@@ -51,11 +51,11 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
    :::image type="content" source="media/networking/dns/nsxt-workload-networking-configure-fqdn-zone.png" alt-text="Screenshot showing the required information needed to add an FQDN zone.":::
 
    >[!IMPORTANT]
-   >While NSX-T Data Center allows spaces and other non-alphanumeric characters in a DNS zone name, certain NSX-T Data Center resources such as a DNS Zone are mapped to an Azure resource whose names don’t permit certain characters. 
+   >NSX-T Data Center allows spaces and other non-alphanumeric characters in a DNS zone name. However, certain NSX-T Data Center resources such as a DNS Zone are mapped to an Azure resource whose names don’t permit certain characters. 
    >
-   >As a result, DNS zone names that would otherwise be valid in NSX-T Data Center may need adjustment to adhere to the [Azure resource naming conventions](../azure-resource-manager/management/resource-name-rules.md#microsoftresources).
+   >As a result, DNS zone names that would otherwise be valid in NSX-T Data Center could need an adjustment to adhere to the [Azure resource naming conventions](../azure-resource-manager/management/resource-name-rules.md#microsoftresources).
 
-      It takes several minutes to complete, you can follow the progress from **Notifications**. You see a message in the Notifications when the DNS zone is created.
+      It takes several minutes to complete but you can follow the progress from **Notifications**. You see a message in the Notifications when the DNS zone is created.
 
 1. Ignore the message about a default DNS zone because one gets created for you as part of your private cloud.
 
@@ -65,7 +65,7 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
    >For private clouds created on or after July 1, 2021, you can ignore the message about a default DNS zone as one is created for you during private cloud creation.
 
    >[!IMPORTANT]
-   >While certain operations in your private cloud may be performed from NSX-T Manager, for private clouds created on or after July 1, 2021, you _must_ edit the DNS service from the Simplified Networking experience in the Azure portal for any configuration changes made to the default Tier-1 Gateway.  
+   >Certain operations in your private cloud can be performed from NSX-T Manager. For private clouds created on or after July 1, 2021, you _must_ edit the DNS service from the Simplified Networking experience in the Azure portal for any configuration changes made to the default Tier-1 Gateway.  
 
    :::image type="content" source="media/networking/dns/configure-dns-forwarder-2.png" alt-text="Screenshot showing the DNS service tab with the Edit button selected.":::   
 
@@ -78,19 +78,19 @@ The diagram shows that the NSX-T Data Center DNS Service can forward DNS queries
 1. Repeat the above steps for other FQDN zones.
 
 ## Change Default T1 DNS Forwarder Zone
-1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **DNS** > **DNS zones** > Check **TNT##-DNS-FORWARDER-ZONE**.  Then select **Edit**.
+1. In your Azure VMware Solution private cloud, under **Workload Networking**, select **DNS** > **DNS zones** > check **TNT##-DNS-FORWARDER-ZONE** > select **Edit**.
 
    ![AVS-DNS](https://user-images.githubusercontent.com/7501186/226980095-b0576824-e1b7-46dc-b726-58670e4e3096.png)
 
-2. Change DNS server entries to valid reachable IP addresses.  Then select **OK**
+2. Change DNS server entries to valid reachable IP addresses, then select **OK**.
 
    ![Edit_DNS_Zone](https://user-images.githubusercontent.com/7501186/226980023-8b92fce9-310e-4934-9045-238bcd5d921f.png)
 
    >[!TIP]
-   >For vCenter, NSX-T, and HCX management components to successfully perform reverse DNS lookups, a DNS server that is capable of performing reverse DNS lookups must be defined in `DNS server IP` in the Default T1 DNS Forwarder Zone.
+   >For vCenter, NSX-T, and HCX management components to successfully perform reverse DNS lookups, a DNS server that's capable of performing reverse DNS lookups must be defined in `DNS server IP` in the Default T1 DNS Forwarder Zone.
    
    >[!IMPORTANT]
-   >A DNS endpoint that is unreachable by the NSX-T DNS server will result in an NSX-T alarm stating that the endpoint is unreachable.  In cases of the default configuration provided with Azure VMware Solution, this is due to internet that is disabled by default.  The alarm can be acknowledged and ignored, or the default configuration can be changed to a valid endpoint.
+   >A DNS endpoint that's unreachable by the NSX-T DNS server results in an NSX-T alarm stating that the endpoint is unreachable. In cases of the default configuration provided with Azure VMware Solution, it's due to internet that is disabled by default. The alarm can be acknowledged and ignored, or the default configuration can be changed to a valid endpoint.
 
 ## Verify name resolution operations
 

articles/azure-vmware/configure-github-enterprise-server.md

@@ -3,7 +3,7 @@ title: Configure GitHub Enterprise Server on Azure VMware Solution
 description: Learn how to Set up GitHub Enterprise Server on your Azure VMware Solution private cloud.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 12/06/2023
+ms.date: 2/11/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
@@ -16,7 +16,7 @@ In this article, learn how to set up GitHub Enterprise Server, the "on-premises"
 
 ## Before you begin
 
-GitHub Enterprise Server requires a valid license key. You can sign up for a [trial license](https://enterprise.github.com/trial). If you're looking to extend the capabilities of GitHub Enterprise Server via an integration, check if you qualify for a free five-seat developer license. Apply for this license through [GitHub's Partner Program](https://partner.github.com/).
+GitHub Enterprise Server requires a valid license key. You can sign up for a [trial license](https://enterprise.github.com/trial). If you're looking to extend the capabilities of GitHub Enterprise Server via an integration, check if you qualify for a free five-user developer license. Apply for this license through [GitHub's Partner Program](https://partner.github.com/).
 
 ## Install GitHub Enterprise Server on VMware
 
@@ -83,7 +83,7 @@ To harden your instance for production use, the following optional setup steps a
     - Virtualization host system failures
     - Logically or physically severed network
 
-2. [Configure](https://docs.github.com/en/enterprise/admin/configuration/configuring-backups-on-your-appliance) [backup-utilities](https://github.com/github/backup-utils), providing versioned snapshots for disaster recovery, hosted in availability that is separate from the primary instance.
+2. [Configure](https://docs.github.com/en/enterprise/admin/configuration/configuring-backups-on-your-appliance) [backup-utilities](https://github.com/github/backup-utils), providing versioned snapshots for disaster recovery, hosted in availability that's separate from the primary instance.
 3. [Setup subdomain isolation](https://docs.github.com/en/enterprise/admin/configuration/enabling-subdomain-isolation), using a valid TLS certificate, to mitigate cross-site scripting and other related vulnerabilities.
 
 
@@ -96,9 +96,9 @@ At this point, you should have an instance of GitHub Enterprise Server running,
 
 Create somewhere for GitHub Actions to run using Azure VMware Solution.
 
-1. Provision a new VM on the cluster and base it on [a recent release of Ubuntu Server](http://releases.ubuntu.com/20.04.1/).
+1. Configure a new VM on the cluster and base it on [a recent release of Ubuntu Server](http://releases.ubuntu.com/20.04.1/).
 
-   :::image type="content" source="media/github-enterprise-server/provision-new-vm.png" alt-text="Screenshot showing the virtual machine name and location to provision a new VM.":::
+   :::image type="content" source="media/github-enterprise-server/provision-new-vm.png" alt-text="Screenshot showing the virtual machine name and location to configure a new VM.":::
 
 1. Continue through the setup selecting the compute resource, storage, and compatibility.
 
@@ -181,7 +181,7 @@ Configure and enable GitHub Actions on the GitHub Enterprise Server instance.
 
    You should see output: _Blob Storage is healthy_.
 
-1. Now that **GitHub Actions** is configured, enable it for your users. Sign in to your GitHub Enterprise Server instance as an administrator, and select the :::image type="icon" source="media/github-enterprise-server/rocket-icon.png"::: in the upper right corner of any page. 
+1. Now that **GitHub Actions** is configured, enable it for your users. Sign in to your GitHub Enterprise Server instance as an administrator, and select the :::image type="icon" source="media/github-enterprise-server/rocket-icon.png"::: icon in the upper right corner of any page. 
 
 1. In the left sidebar, select **Enterprise overview**, then **Policies**, **Actions**, and select the option to **enable Actions for all organizations**.
 
@@ -230,7 +230,7 @@ If you chose not to enable GitHub Connect, you could use the following alternati
 
 :::image type="content" source="media/github-enterprise-server/workflow-example-2.png" alt-text="Screenshot of an alternative example workflow.":::
 
-1. Navigate to a repo on your instance, and add the above workflow as: `.github/workflows/hello-world.yml`
+1. Navigate to a repo on your instance, and add the previous workflow as: `.github/workflows/hello-world.yml`
 
    :::image type="content" source="media/github-enterprise-server/workflow-example-3.png" alt-text="Screenshot of another alternative example workflow.":::
 
@@ -246,7 +246,7 @@ If everything ran successfully, you should see a new issue in your repo, entitle
 
 :::image type="content" source="media/github-enterprise-server/example-in-repo.png" alt-text="Screenshot of the Hello world issue in GitHub created by github-actions.":::
 
-Congratulations! You just completed your first Actions workflow on GitHub Enterprise Server, running on your Azure VMware Solution private cloud.
+Congratulations, you completed your first Actions workflow on GitHub Enterprise Server, running on your Azure VMware Solution private cloud.
 
 This article set up a new instance of GitHub Enterprise Server, the self-hosted equivalent of GitHub.com, on top of your Azure VMware Solution private cloud. The instance includes support for GitHub Actions and uses Azure Blob Storage for persistence of logs and artifacts. But we're just scratching the surface of what you can do with GitHub Actions. Check out the list of Actions on [GitHub's Marketplace](https://github.com/marketplace), or [create your own](https://docs.github.com/en/actions/creating-actions).
 

articles/azure-vmware/configure-hcx-network-extension-high-availability.md

@@ -3,7 +3,7 @@ title: Configure HCX network extension high availability
 description: Learn how to configure HCX network extension high availability
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 02/26/2023
+ms.date: 02/11/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
@@ -23,14 +23,14 @@ HCX 4.3.0 or later allows network extension high availability. Network Extension
 The Network Extension High Availability (HA) setup requires four Network Extension appliances, with two appliances at the source site and two appliances at the remote site. Together, these two pairs form the HA Group, which is the mechanism for managing Network Extension High Availability. Appliances on the same site require a similar configuration and must have access to the same set of resources.
 
 - Network Extension HA requires an HCX Enterprise license.
-- In the HCX Compute Profile, the Network Extension Appliance Limit is set to allow for the number of Network Extension appliances. The Azure VMware Solutions Limit is automatically set to unlimited. 
-- In the HCX Service Mesh, the Network Extension Appliance Scale Out Appliance Count is set to provide enough appliances to support network extension objectives, including any Network Extension HA groups.
+- For the HCX Compute Profile, the Network Extension Appliance Limit is set to allow for the number of Network Extension appliances. The Azure VMware Solutions Limit is automatically set to unlimited. 
+- For the HCX Service Mesh, the Network Extension Appliance Scale Out Appliance Count is set to provide enough appliances to support network extension objectives, including any Network Extension HA groups.
 
 When you create a service mesh, set the appliance count to a minimum of two. For an existing service mesh, you can edit and adjust the appliance count to provide the required appliance count.
 
-- The Network Extension appliances selected for HA activation must have no networks extended over them.
+- Network Extension appliances selected for HA activation must have no networks extended over them.
 - Only Network Extension appliances upgraded to HCX 4.3.0 or later can be added to HA Groups.
-- Learn more about the [Network Extension High Availability](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/extending-networks-with-vmware-hcx/understand-network-extension-high-availability.html) feature, prerequisites, considerations and limitations.
+- Learn more about the [Network Extension High Availability](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/extending-networks-with-vmware-hcx/understand-network-extension-high-availability.html) feature, prerequisites, considerations, and limitations.
 
 ## Activate high availability (HA)
 
@@ -75,6 +75,6 @@ Use the following steps to activate HA, create HA groups, and view the HA roles
 
 ## Next steps
 
- Now that you learned how to configure and extend HCX network extension high availability (HA), use the following resource to learn more about how to manage HCX network extension HA.
+ You learned how to configure and extend HCX network extension high availability (HA). Use the following resource to learn more about how to manage HCX network extension HA.
 
 [Managing Network Extension High Availability](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/extending-networks-with-vmware-hcx/understand-network-extension-high-availability/managing-network-extension-high-availability.html)