Skip to content

Commit 02daf87

Browse files
committed
Updates
1 parent 40f4ad0 commit 02daf87

File tree

1 file changed

+11
-4
lines changed
  • articles/virtual-machines/workloads/redhat

1 file changed

+11
-4
lines changed

articles/virtual-machines/workloads/redhat/byos.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -172,25 +172,32 @@ The following is an example script. You should replace the Resource Group, locat
172172

173173
Red Hat Enterprise Linux Bring-Your-Own-Subscription Gold Images can be secured through the use of [Azure Disk Encryption](../../linux/disk-encryption-overview.md). However, the subscription **must** be registered before enabling encryption. Details on registering a RHEL BYOS Gold Image are available on the Red Hat site. See [How to register and subscribe a system to the Red Hat Customer Portal using Red Hat Subscription-Manager](https://access.redhat.com/solutions/253273); if you have an active Red Hat subscription, you can also read [Creating Red Hat Customer Portal Activation Keys](https://access.redhat.com/articles/1378093).
174174

175-
Azure Disk Encryption requirements and prerequisites are documented in [Azure Disk Encryption for Linux VMs](../../virtual-machines/linux/disk-encryption-overview.md#additional-vm-requirements); steps for applying Azure Disk Encryption are available in [Azure Disk Encryption scenarios on Linux VMs](../../linux/disk-encryption-linux.md) and related articles.
175+
Azure Disk Encryption requirements and prerequisites are documented in [Azure Disk Encryption for Linux VMs](../../virtual-machines/linux/disk-encryption-overview.md#additional-vm-requirements). ADE is not supported on Red Hat images.
176+
177+
; steps for applying Azure Disk Encryption are available in [Azure Disk Encryption scenarios on Linux VMs](../../linux/disk-encryption-linux.md) and related articles.
176178

177179
Note that encryption will fail on a [Red Hat custom image](/linux/redhat-create-upload-vhd) that significantly deviates from the base image.
178180

179181
## Additional information
180-
- If you attempt to provision a VM on a subscription that is not enabled for this offer, you will get the following error:.
182+
- If you attempt to provision a VM on a subscription that is not enabled for this offer, you will get the following error:
183+
181184
```
182185
"Offer with PublisherId: redhat, OfferId: rhel-byos, PlanId: rhel-lvm75 is private and can not be purchased by subscriptionId: GUID"
183186
```
184-
Contact Microsoft or Red Hat to enable your subscription.
187+
188+
In this case, contact Microsoft or Red Hat to enable your subscription.
185189
186-
- If you create a snapshot from the RHEL BYOS image AND publish the image in [Shared Image Gallery](https://docs.microsoft.com/azure/virtual-machines/linux/shared-image-galleries), you must provide plan information that matches the original source of the snapshot. For example, the command might look like (note the plan parameters in the final line):
190+
- If you create a snapshot from the RHEL BYOS image and publish a custom image in [Shared Image Gallery](https://docs.microsoft.com/azure/virtual-machines/linux/shared-image-galleries), you must provide plan information that matches the original source of the snapshot. For example, the command might look like this:
187191
188192
```azurecli
189193
az vm create –image \
190194
"/subscriptions/GUID/resourceGroups/GroupName/providers/Microsoft.Compute/galleries/GalleryName/images/ImageName/versions/1.0.0" \
191195
-g AnotherGroupName --location EastUS2 -n VMName \
192196
--plan-publisher redhat --plan-product rhel-byos --plan-name rhel-lvm75
193197
```
198+
Note the plan parameters in the final line above.
199+
200+
[Azure Disk Encryption](#encrypt-red-hat-enterprise-linux-bring-your-own-subscription-gold-images) is not supported on custom images.
194201
195202
- If you are using automation to provision VMs from the RHEL BYOS images, you must provide plan parameters similar to what was shown above. For example, if you are using Terraform, you would provide the plan information in a [plan block](https://www.terraform.io/docs/providers/azurerm/r/virtual_machine.html#plan).
196203

0 commit comments

Comments
 (0)