openshift · AedinC · Jan 27, 2025
diff --git a/modules/creating-a-machine-pool-cli.adoc b/modules/creating-a-machine-pool-cli.adoc
@@ -196,19 +196,43 @@ I: To view all machine pools, run 'rosa list machinepools -c mycluster'
 ----
 
 //ifdef::openshift-rosa-hcp[] Uncomment this out once HCP split occurs
-* To add a Windows License Included enabled machine pool to a {hcp-title} cluster, see link:https://access.redhat.com/articles/7096903[AWS Windows License Included for ROSA with HCP].
+* If you are using {VirtProductName} on a {hcp-title} cluster, you might want to run Windows VMs. In order to be license-compliant with Microsoft Windows in AWS, the hosts (metal EC2 instances) running these VMs must be enabled with AWS EC2 Windows License Included.
 +
-Windows License Included enabled machine pools can only be created when the following criteria is met:
-
-** The host cluster is a {hcp-title} cluster.
-** The instance type is bare metal EC2.
+To add a Windows Licence Included enabled machine pool to a {hcp-title} cluster, create the machine pool with the following instance type and labels.
 +
 [IMPORTANT]
 ====
-AWS Windows License Included for {hcp-title} is a Technology Preview feature only. Technology Preview features are not supported with Red{nbsp}Hat production service level agreements (SLAs) and might not be functionally complete. Red{nbsp}Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
-
-For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
+You can only add a Windows Licence Included enabled machine pool to a {hcp-title} cluster version 4.19 and above, created in the `us-west-2` region, and using a bare metal EC2 instance type.
 ====
++
+[source,terminal]
+----
+$ rosa create machinepool --cluster=<cluster-name> \
+                          --name=<machine_pool_id> \
+                          --replicas=<replica_count> \
+                          --instance-type=<instance_type> \
+                          --labels=<key>=<value>,<key>=<value>
+----
+where:
+
+`--name=<machine_pool_id>`:: Specifies the name of the machine pool. Replace `<machine_pool_id>` with the name of your machine pool.
+`--replicas=<replica_count>`:: Specifies the number of compute nodes to provision. If you deployed ROSA using a single availability zone, this defines the number of compute nodes to provision to the machine pool for the zone. If you deployed your cluster using multiple availability zones, this defines the number of compute nodes to provision in total across all zones and the count must be a multiple of 3. The `--replicas` argument is required when autoscaling is not configured.
+`--instance-type=<instance_type>`:: Specifies the instance type. You can only select a bare metal instance type to enable Windows LI.(x86-64).
+`--labels=<key>=<value>,<key>=<value>`:: Defines the labels for the machine pool. Replace `<key>=<value>,<key>=<value>` with a comma-delimited list of key-value pairs, for example `--labels=key1=value1,key2=value2`. You must include the `image_type:windows` label to ensure the machine pool is created with Windows LI enabled.
++
+The following example creates a machine pool with Windows License LI enabled called `mymachinepool` that uses the `bm5zn.metal` instance type and has 1 compute node replica:
++
+[source,terminal]
+----
+$ rosa create machinepool --cluster=mycluster --name=mymachinepool --type win-li --instance-type m5zn.metal --replicas 1
+----
++
+.Example output
+[source,terminal]
+----
+I: Machine pool 'mymachinepool' created successfully on cluster 'mycluster'
+I: To view all machine pools, run 'rosa list machinepools -c mycluster'
+----
 //endif::openshift-rosa-hcp[] Uncomment this out once HCP split occurs
 
 .Verification

diff --git a/modules/creating-a-machine-pool-ocm.adoc b/modules/creating-a-machine-pool-ocm.adoc
@@ -57,9 +57,16 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 ====
 You cannot change the instance type for a machine pool after the pool is created.
 ====
-
+ifdef::openshift-rosa,openshift-rosa-hcp[]
+. Optional: If you are using {VirtProductName} on a {hcp-title} cluster, you might want to run Windows VMs. In order to be license-compliant with Microsoft Windows in AWS, the hosts (metal EC2 instances) running these VMs must be enabled with AWS EC2 Windows License Included. To enable the machine pool for AWS Windows License Included, select the *Enable machine pool for AWS Windows License Included* checkbox.
++
+[IMPORTANT]
+====
+You can only select this option when the host cluster is a {hcp-title} cluster version 4.19 and above, the instance type is bare metal EC2, and the region is `us-west-2`.
+====
 . Optional: Configure autoscaling for the machine pool:
 .. Select *Enable autoscaling* to automatically scale the number of machines in your machine pool to meet the deployment needs.
+endif::openshift-rosa,openshift-rosa-hcp[]
 ifdef::openshift-dedicated[]
 +
 [NOTE]

diff --git a/rosa_release_notes/rosa-release-notes.adoc b/rosa_release_notes/rosa-release-notes.adoc
@@ -14,6 +14,13 @@ toc::[]
 [id="rosa-new-changes-and-updates_{context}"]
 == New changes and updates
 
+[id="rosa-q3-2025_{context}"]
+=== Q3 2025
+//The following is included in Classic only until the Images doc has been split for HCP
+ifndef::openshift-rosa-hcp[]
+* **AWS Windows Licence Included now available for {hcp-title}.** You can now add a Windows Licence Included enabled machine pool to a {hcp-title} cluster. For more information, see xref:../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_cli[Managing compute nodes].
+endif::openshift-rosa-hcp[]
+
 [id="rosa-q2-2025_{context}"]
 === Q2 2025
 
@@ -71,7 +78,6 @@ endif::openshift-rosa[]
 ** Configure a `cluster-admin` user and optionally define a custom password.
 ** Configure the root disk size for the default machine pool.
 
-//The following is included in Classic only until the Images doc has been split for HCP
 ifndef::openshift-rosa-hcp[]
 * **Image configuration is now available for {hcp-title}.** You can configure registries within a cluster to exclude some registries or allow only a defined list. It also allows to expose additional trusted bundle for registries to pull from. For more information, see xref:../openshift_images/image-configuration-hcp.adoc#images-configuration-parameters-hcp_image-configuration-hcp[Image configuration resources for {hcp-title}].
 endif::openshift-rosa-hcp[]