Merge pull request #837 from MicrosoftDocs/main

1/13/2025 AM Publish
MicrosoftDocs · Jan 13, 2025 · 43a6b10 · 43a6b10
2 parents 3ee8af9 + aef20c6
commit 43a6b10
Showing 1 changed file with 21 additions and 20 deletions.
diff --git a/articles/virtual-machines/workloads/redhat/redhat-rhui.md b/articles/virtual-machines/workloads/redhat/redhat-rhui.md
@@ -19,20 +19,20 @@ ms.author: jushiman
 
 - Mirror Red Hat-hosted repository content
 - Create custom repositories with Azure-specific content
-- Make the content available to end-user VMs
+- Make the content available to end-user Virtual Machines (VMs)
 
 Red Hat Enterprise Linux (RHEL) Pay-As-You-Go (PAYG) images come preconfigured to access Azure RHUI. No other configuration is needed. To get the latest updates, run `sudo yum update` after your RHEL instance is ready. This service is included as part of the RHEL PAYG software fees. For more information on RHEL images in Azure, including publishing and retention policies, see [Overview of Red Hat Enterprise Linux images in Azure](./redhat-images.md).
 
 For more information on Red Hat support policies for all versions of RHEL, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
 
 > [!IMPORTANT]
-> RHUI is intended only for pay-as-you-go (PAYG) images. For golden images, also known as bring your own subscription (BYOS), the system needs to be attached to RHSM or Satellite in order to receive updates. For more information, see [How to register and subscribe a RHEL system](https://access.redhat.com/solutions/253273).
+> RHUI is intended only for pay-as-you-go (PAYG) images. For golden images, also known as bring your own subscription (BYOS), the system needs to be attached to Red Hat Subscription Manager (RHSM) or Satellite in order to receive updates. For more information, see [How to register and subscribe a RHEL system](https://access.redhat.com/solutions/253273).
 
 ## Important information about Azure RHUI
 
 - Azure RHUI is the update infrastructure that supports all RHEL PAYG VMs created in Azure. This infrastructure doesn't prevent you from registering your PAYG RHEL VMs with Subscription Manager, Satellite, or another source of updates. Registering with a different source with a PAYG VM results in indirect double-billing. See the following point for details.
 
-- Access to the Azure-hosted RHUI is included in the RHEL PAYG image price. Unregistering a PAYG RHEL VM from the Azure-hosted RHUI doesn't convert the virtual machine into a BYOL type of VM. If you register the same VM with another source of updates, you might incur *indirect* double charges. You're charged the first time for the Azure RHEL software fee. You're charged the second time for Red Hat subscriptions that were purchased previously. If you consistently need to use an update infrastructure other than Azure-hosted RHUI, consider registering to use [RHEL BYOS images](./byos.md).
+- Access to the Azure-hosted RHUI is included in the RHEL PAYG image price. Unregistering a PAYG RHEL VM from the Azure-hosted RHUI doesn't convert the virtual machine into a BYOS type of VM. If you register the same VM with another source of updates, you might incur *indirect* double charges. You're charged the first time for the Azure RHEL software fee. You're charged the second time for Red Hat subscriptions that were purchased previously. If you consistently need to use an update infrastructure other than Azure-hosted RHUI, consider registering to use [RHEL BYOS images](./byos.md).
 
 - RHEL SAP PAYG images in Azure are connected to dedicated RHUI channels that remain on the specific RHEL minor version as required for SAP certification. RHEL SAP PAYG images in Azure include RHEL for SAP, RHEL for SAP HANA, and RHEL for SAP Business Applications.
 
@@ -42,19 +42,20 @@ For more information on Red Hat support policies for all versions of RHEL, see [
 
 The Red Hat images provided in Azure Marketplace are connected by default to one of two different types of life-cycle repositories:
 
-- Non-EUS: Will have the latest available software published by Red Hat for their particular Red Hat Enterprise Linux (RHEL) repositories.
-- Extended Update Support (EUS): Updates won't go beyond a specific RHEL minor release.
+- Non-EUS: Has the latest available software published by Red Hat for their particular Red Hat Enterprise Linux (RHEL) repositories.
+
+- Extended Update Support (EUS): Updates for a specific RHEL minor release.
 
 > [!NOTE]
 > For more information on RHEL EUS, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata) and [Red Hat Enterprise Linux Extended Update Support Overview](https://access.redhat.com/articles/rhel-eus).
 
-The packages contained in the Red Hat Update Infrastructure repositories are published and maintained exclusively by Red Hat, extra packages to support custom Azure services, are published in independent repositories maintained by Microsoft.
+The packages contained in the Red Hat Update Infrastructure repositories are published and maintained by Red Hat. Extra packages to support custom Azure services are published in independent repositories maintained by Microsoft.
 
 For a full image list, run `az vm image list --offer RHEL --all -p RedHat --output table` using the Azure CLI.
 
 ### Images connected to non-EUS repositories
 
-RHEL VM images connected to non-EUS repositories, it will upgrade to the latest RHEL minor version when you run `sudo yum update`. For example, if you provision a VM from a RHEL 8.4 PAYG image and run `sudo yum update`, you end up with a RHEL 8.9 VM, the latest minor version in the RHEL8 family.
+For RHEL VM images connected to non-EUS repositories, running `sudo yum update` will upgrade to the latest RHEL minor version. For example, if you provision a VM from a RHEL 8.4 PAYG image and run `sudo yum update`, you end up with a RHEL 8.9 VM, the latest minor version in the RHEL8 family.
 
 Images that are connected to non-EUS repositories don't contain a minor version number in the SKU. The SKU is the third element in the image name. For example, all of the following images come attached to non-EUS repositories:
 
@@ -82,14 +83,14 @@ RedHat:RHEL:9_0:9.0.2023061412
 ```
 
 > [!NOTE]
-> Not all minor versions are valid EUS stops, for example, for RHEL8 only 8.1, 8.2, 8.4, 8.6 and 8.8 are valid EUS releases, while 8.3, 8.5 and 8.7 are not.
+> For RHEL8, the following are EUS releases: 8.1, 8.2, 8.4, 8.6 and 8.8. RHEL 8.3, 8.5 and 8.7 aren't EUS releases.
 
 ## RHEL EUS and version-locking RHEL VMs
 
 Extended Update Support (EUS) repositories are available to customers who might want to lock their RHEL VMs to a certain RHEL minor release after provisioning the VM. You can version-lock your RHEL VM to a specific minor version by updating the repositories to point to the Extended Update Support repositories. You can also undo the EUS version-locking operation.
 
 > [!NOTE]
-> EUS is not supported on RHEL Extras. This means that if you install a package that is usually available from the RHEL Extras channel, you can't install while on EUS. For more information, see [Red Hat Enterprise Linux Extras Product Life Cycle](https://access.redhat.com/support/policy/updates/extras/).
+> The RHEL Extras channel does not follow the EUS lifecycle. This means that if you install a package from the RHEL Extras channel, it will not be specific to the EUS release you are on. Red Hat does not support installing content from the RHEL Extras channel while on an EUS release. For more information, see [Red Hat Enterprise Linux Extras Product Life Cycle](https://access.redhat.com/support/policy/updates/extras/).
 
 Support for EUS RHEL7 ended in June 30, 2024. For more information, see [Red Hat Enterprise Linux Extended Maintenance](https://access.redhat.com/support/policy/updates/errata/#Long_Support).
 
@@ -108,7 +109,7 @@ Support for EUS RHEL7 ended in June 30, 2024. For more information, see [Red Hat
 #### [Switching to EUS repositories on RHEL7](#tab/rhel7)
 
 >[!NOTE]
->Support for RHEL7 EUS ended in June 30, 2024. It is not recommended to switch to EUS repositories in RHEL7 anymore.
+>Support for RHEL7 EUS ended in June 30, 2024. It isn't recommended to switch to EUS repositories in RHEL7 anymore.
 
 
 #### [Switching to EUS repositories on RHEL8](#tab/rhel8)
@@ -140,8 +141,8 @@ Use the following procedure to lock a RHEL 8.x VM to a particular minor release.
 
    If there are permission issues to access the `releasever`, you can edit the file using a text editor, add the image version details, and save the file.
 
-   > [!NOTE]
-   > This instruction locks the RHEL minor release to the current minor release. Enter a specific minor release if you are looking to upgrade and lock to a later minor release that is not the latest. For example, `echo 8.1 > /etc/yum/vars/releasever` locks your RHEL version to RHEL 8.1.
+   >[!NOTE]
+   >This instruction locks the RHEL minor release to the current minor release. Enter a specific minor release if you're looking to upgrade and lock to a later minor release that isn't the latest. For example, `echo 8.1 > /etc/yum/vars/releasever` locks your RHEL version to RHEL 8.1.
 
 1. Update your RHEL VM.
 
@@ -153,8 +154,8 @@ Use the following procedure to lock a RHEL 8.x VM to a particular minor release.
 
 Use the following procedure to lock a RHEL 9.x VM to a particular minor release. Run the commands as `root`:
 
-> [!NOTE]
-> This procedure only applies for RHEL 9.x versions for which EUS is available. Currently, the list of versions includes RHEL 9.0, 9.2, and 9.4. Red Hat also plans to make EUS available for 9.6 and 9.8. For more information, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
+>[!NOTE]
+>This procedure only applies for RHEL 9.x versions for which EUS is available. Currently, the list of versions includes RHEL 9.0, 9.2, and 9.4. Red Hat also plans to make EUS available for 9.6 and 9.8. For more information, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
 
 1. Disable non-EUS repositories.
 
@@ -177,8 +178,8 @@ Use the following procedure to lock a RHEL 9.x VM to a particular minor release.
 
       If there are permission issues to access the `releasever`, you can edit the file using a text editor, add the image version details, and save the file.
 
-      > [!NOTE]
-   > This instruction locks the RHEL minor release to the current minor release. Enter a specific minor release if you are looking to upgrade and lock to a later minor release that is not the latest. For example, `echo 9.2 > /etc/yum/vars/releasever` locks your RHEL version to RHEL 9.2.
+      >[!NOTE]
+      >This instruction locks the RHEL minor release to the current minor release. Enter a specific minor release if you're looking to upgrade and lock to a later minor release that isn't the latest. For example, `echo 9.2 > /etc/yum/vars/releasever` locks your RHEL version to RHEL 9.2.
 
 1. Update your RHEL VM.
 
@@ -281,7 +282,7 @@ To remove the version lock, use the following commands. Run the commands as `roo
 
 RHUI is available in all regions where RHEL on-demand images are available. Availability currently includes all public regions listed in the [Azure status dashboard](https://azure.microsoft.com/status/), Azure US Government, and Microsoft Azure Germany regions.
 
-If you're using a network configuration (custom Firewall or UDR configurations) to further restrict `https` access from RHEL PAYG VMs, make sure the following IPs are allowed for `dnf update` to work depending on your environment:
+If you're using a network configuration (custom Firewall or user-defined routes (UDR) configuration) to further restrict `https` access from RHEL PAYG VMs, make sure the following IPs are allowed for `dnf update` to work depending on your environment:
 
 ```output
 # Azure Global - RHUI 4
@@ -311,13 +312,13 @@ If you experience problems connecting to Azure RHUI from your Azure RHEL PAYG VM
 
 1. Verify that access to Azure-hosted RHUI is limited to VMs within the [Azure datacenter IP ranges](https://www.microsoft.com/download/details.aspx?id=56519).
 
-1. If you're using the new configuration and you've verified that the VM connects from the Azure IP range, and you still can't connect to Azure RHUI, file a support case with Microsoft or Red Hat.
+1. If you're still having issues using the new configuration and the VM connects from the Azure IP range, file a support case with Microsoft or Red Hat.
 
 ### Infrastructure update
 
 In September 2016, Azure deployed an updated Azure RHUI. In April 2017, the old Azure RHUI was shut down. If you have been using the RHEL PAYG images or their snapshots from September 2016 or later, you're automatically connecting to the new Azure RHUI. If, however, you have older snapshots on your VMs, you need to manually update their configuration to access the Azure RHUI as described in a following section.
 
-The new Azure RHUI servers are deployed with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/). In Traffic Manager, any VM can use a single endpoint, rhui-1.microsoft.com and rhui4-1.microsoft.com, regardless of region.
+The new Azure RHUI servers are deployed with [Azure Traffic Manager](https://azure.microsoft.com/services/traffic-manager/). In Traffic Manager, any VM can use a single endpoint, rhui-1.microsoft.com, and rhui4-1.microsoft.com, regardless of region.
 
 ### Manual update procedure to use the Azure RHUI servers
 
@@ -366,4 +367,4 @@ This procedure is provided for reference only. RHEL PAYG images already have the
 
 - To create a Red Hat Enterprise Linux VM from an Azure Marketplace PAYG image and to use Azure-hosted RHUI, go to the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/redhat.rhel-20190605).
 - To learn more about the Red Hat images in Azure, see [Overview of Red Hat Enterprise Linux images](./redhat-images.md).
-- Information on Red Hat support policies for all versions of RHEL can be found at [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).
+- To learn more about Red Hat's support policies, see [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata).