Microsoft BYOL licenses for all instances

[chrisverrett]

hi,
The docs page implies BYOL is only valid for dedicated host images

"If you plan to provide your own operating system license, select this checkbox. If you are importing an image with a Windows operating system, you can select this option if you plan to use the image to provision dedicated host instances."

but this doesn't align to the latest posted in this blog:
https://www.ibm.com/cloud/blog/bring-your-own-license-for-microsoft-on-multi-tenant-hosts

thanks for considering rewording!

Chris

[jmilst]

Hi @chrisverrett. Thank you for reaching out. The blog post that you're referring to is related to our VPC infrastructure and the dedicated host instances page that you're sharing relates to our Classic infrastructure. BYOL isn't an option for our Classic infrastructure. For information bout VPC and BYOL for Windows, see BYOL for Windows operating systems.

[chrisverrett]

Hi @john ***@***.***> You mentioned “BYOL isn't an option for our Classic infrastructure.” However this page https://cloud.ibm.com/docs/image-templates?topic=image-templates-preparing-and-importing-images#import-icos clearly references “If you plan to provide your own operating system license, select this checkbox. If you are importing an image with a Windows operating system, you can select this option if you plan to use the image to provision dedicated host instances<https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-dedicated-hosts-and-dedicated-instances#dedicated-hosts-and-dedicated-instances>. If your version of Windows operating system does not support the use your own license option, this option is disabled. For Windows images, you cannot select Cloud Init if you specify that you use your own license. If you are importing an encrypted image with Red Hat Enterprise Linux as your operating system, this option is selected by default and not editable because your encrypted image must include its own operating system license.” Hopefully you can see how this is confusing. Is BYOL on classic limited to dedicated hosts? If so, maybe that should be called out? Thanks, Chris Chris Verrett Sr. Customer Success Manager IBM Public Cloud, Americas ***@***.******@***.***> 972-877-1281 From: jmilst ***@***.***> Date: Friday, March 24, 2023 at 4:56 PM To: ibm-cloud-docs/image-templates ***@***.***> Cc: Chris Verrett ***@***.***>, Mention ***@***.***> Subject: [EXTERNAL] Re: [ibm-cloud-docs/image-templates] Microsoft BYOL licenses for all instances (Issue #17) Hi @chrisverrett. Thank you for reaching out. The blog post that you're referring to is related to our VPC infrastructure and the dedicated host instances page that you're sharing relates to our Classic infrastructure. BYOL isn't an option ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Hi @chrisverrett<https://github.com/chrisverrett>. Thank you for reaching out. The blog post that you're referring to is related to our VPC infrastructure and the dedicated host instances page that you're sharing relates to our Classic infrastructure. BYOL isn't an option for our Classic infrastructure. For information bout VPC and BYOL for Windows, see BYOL for Windows operating systems<https://cloud.ibm.com/docs/vpc?topic=vpc-byol-vpc-about#byol-vpc-windows>. — Reply to this email directly, view it on GitHub<#17 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJKBTH4RCOQSVFFN6IWJKWLW5YJ7ZANCNFSM6AAAAAAVWRQCAU>. You are receiving this because you were mentioned.Message ID: ***@***.***>