Changing "license" verbiage and updating checklist

Author: yadavsaloni2021

articles/azure-vmware/vmware-cloud-foundations-license-portability.md

@@ -1,77 +1,76 @@
 ---
-title: Use VMware Cloud Foundations (VCF) license portability on Azure VMware Solution
-author: saloniyadav
+title: Use Portable VMware Cloud Foundations (VCF) on Azure VMware Solution
 ms.author: saloniyadav
-description: Bring your own VMware Cloud Foundations (VCF) License on Azure VMware Solution
+description: Bring your own VMware Cloud Foundations (VCF) subscription on Azure VMware Solution
 ms.topic: how-to
 ms.service: azure-vmware
 ms.date: 9/30/2024
 ---
 
-# Use VMware Cloud Foundations (VCF) license portability on Azure VMware Solution
+# Use Portable VMware Cloud Foundations (VCF) on Azure VMware Solution
 
-This article discusses how to modernize your VMware workloads by bringing your VMware Cloud Foundations (VCF) entitlements to Azure VMware Solutions and take advantage of incredible cost savings as you modernize your VMware workloads. With Azure VMware Solution, you access both the physical infrastructure and the licensing entitlements for the entire VMware software-defined datacenter (SDDC) stack, including vSphere, ESXi, NSX networking, NSX Firewall, and HCX. With the new VCF license portability option, you can apply your on-premises VCF entitlements, purchased from Broadcom, directly to the Azure VMware Solution infrastructure. This flexibility means you can seamlessly integrate your VMware assets into a fully managed, state-of-the-art Azure environment, maximizing efficiency and cutting costs. Upgrade with confidence and experience the power and flexibility of Azure VMware Solution today! 
+This article discusses how to modernize your VMware workloads by bringing your portable VMware Cloud Foundations (VCF) to Azure VMware Solutions and take advantage of incredible cost savings as you modernize your VMware workloads. With Azure VMware Solution, you access both the physical infrastructure and the licensing entitlements for the entire VMware software-defined datacenter (SDDC) stack, including vSphere, ESXi, NSX networking, NSX Firewall, and HCX. With the new VCF subscription portability option, you can apply your on-premises VCF entitlements, purchased from Broadcom, directly to the Azure VMware Solution infrastructure. This flexibility means you can seamlessly integrate your VMware assets into a fully managed, state-of-the-art Azure environment, maximizing efficiency and cutting costs. Upgrade with confidence and experience the power and flexibility of Azure VMware Solution today! 
 
 ## What's changing?
 
-Private Cloud on the VCF license portability offering, must have prepurchase Firewall add-on from Broadcom along with the VCF subscription to use the vDefend Firewall on Azure VMware Solution. Prior to using the vDefend Firewall software on Azure VMware Solution ensure you register your Firewall add-on with Microsoft. For detailed instructions on how to register your VCF license, see "Register your VCF license with Azure VMware Solution" later in this article.
+Private Cloud on the portable VCF offering, must have prepurchase Firewall add-on from Broadcom along with the VCF subscription to use the vDefend Firewall on Azure VMware Solution. Prior to using the vDefend Firewall software on Azure VMware Solution ensure you register your Firewall add-on with Microsoft. For detailed instructions on how to register your VCF subscription, see "Register your VCF subscription with Azure VMware Solution" later in this article.
 
 >[!IMPORTANT]
 >
->VCF portable licenses are applied at the host level and must cover all the physical cores on a host. For example, if each host in Azure VMware Solution has 36 cores and you intend to have a Private Cloud with 3 nodes, the VCF portable license must cover 108 (3*36) cores. 
->In the current version, if you want to use your own license on an Azure subscription for the Azure VMware Solution workloads, all the nodes (cores) in that subscription including multiple Private Clouds need to be purchased through Broadcom and covered under your Broadcom VCF license portability contract. At the moment, you're required to bring VCF license entitlements that cover cores for all the nodes deployed within your Azure Subscription.
+> Your portable VCF is applied at the host level and must cover all the physical cores on a host. For example, if each host in Azure VMware Solution has 36 cores and you intend to have a Private Cloud with 3 nodes, the portable VCF must cover 108 (3*36) cores. 
+>In the current version, if you want to use your own portable VCF on your Azure subscription for the Azure VMware Solution workloads, all the nodes (cores) in that subscription including multiple Private Clouds need to be purchased through Broadcom and covered under your Broadcom portable VCF contract. At the moment, you're required to bring portable VCF entitlements that cover cores for all the nodes deployed within your Azure Subscription.
 
-## Purchasing VCF license portability offering on Azure VMware Solution
+## Purchasing VCF subscription portability offering on Azure VMware Solution
 
-We offer three flexible commitments and pricing options for using your own VCF license on Azure VMware Solution. You can choose from pay-as-you-go, 1-year Reserved Instance (RI), and 3-year RI options. 
+We offer three flexible commitments and pricing options for using your portable VCF on Azure VMware Solution. You can choose from pay-as-you-go, 1-year Reserved Instance (RI), and 3-year RI options. **NOTE:** 3-year RI option is discontinued for AV36 node type.
 
-To take advantage of the Reserved Instance (RI) pricing for the VCF license portability offering, purchase an RI under the Product Name- VCF BYOL. For example, if your private cloud uses AV36P nodes, you must [purchase the Reserved Instance](/azure/azure-vmware/reserved-instance?toc=%2Fazure%2Fcost-management-billing%2Freservations%2Ftoc.json#buy-a-reservation) for the Product Name- AV36P VCF BYOL. To use the pay-as-you-go pricing for the VCF license portability offering, you only need to register your VCF license. 
+To take advantage of the Reserved Instance (RI) pricing for the VCF subscription portability offering, purchase an RI under the Product Name- VCF BYOL. For example, if your private cloud uses AV36P nodes, you must [purchase the Reserved Instance](/azure/azure-vmware/reserved-instance?toc=%2Fazure%2Fcost-management-billing%2Freservations%2Ftoc.json#buy-a-reservation) for the Product Name- AV36P VCF BYOL. To use the pay-as-you-go pricing for the VCF subscription portability offering, you only need to register your VCF subscription. 
 
-:::image type="content" source="media/vmware-cloud-foundations-license-portability/reserved-instance-purchase.png" alt-text="Screenshot of what product type to select while purchasing reserved instance for VCF license portability offering." border="true":::
+:::image type="content" source="media/vmware-cloud-foundations-license-portability/reserved-instance-purchase.png" alt-text="Screenshot of what product type to select while purchasing reserved instance for VCF subscription portability offering." border="true":::
 
-## Request host quota with VCF license portability
+## Request host quota with VCF subscription portability
 
 Existing: 
 :::image type="content" source="media/vmware-cloud-foundations-license-portability/quota-request-old.png" alt-text="Screenshot of quota request description for existing Azure VMware Solution." border="true":::
 
-To request quota for VCF license portability offering, provide the following additional information in the **Description** of the support ticket:
+To request quota for VCF subscription portability offering, provide the following additional information in the **Description** of the support ticket:
 
 - Region Name 
 - Number of hosts 
 - Host SKU type  
-- Add the following statement as is, by replacing "N" with the "Number of VCF BYOL cores" you purchased from Broadcom for license portability to Azure VMware Solutions:  
-**"I acknowledge that I have procured portable VCF license from Broadcom for "N" cores to use with Azure VMware Solutions."**
+- Add the following statement as is, by replacing "N" with the "Number of VCF BYOL cores" you purchased from Broadcom for VCF portability to Azure VMware Solutions:  
+**"I acknowledge that I have procured portable VCF subscription from Broadcom for "N" cores to use with Azure VMware Solutions."**
 - Any other details, including Availability Zone requirements for integrating with other Azure services; for example, Azure NetApp Files, Azure Blob Storage
 
-:::image type="content" source="media/vmware-cloud-foundations-license-portability/quota-request-license-portability.png" alt-text="Picture of the quota request description for VCF license portability offering on Azure VMware Solution.":::
+:::image type="content" source="media/vmware-cloud-foundations-license-portability/quota-request-license-portability.png" alt-text="Picture of the quota request description for VCF subscription portability offering on Azure VMware Solution.":::
 
 >[!NOTE]
 >
->VCF portable license is applied at the host level and must cover all the physical cores on a host.
->Hence, quota will be approved only for the maximum number of nodes which the VCF portable license covers. For example, if you have purchased 1000 cores for portability and requesting for AV36P, you can get a maximum of 27 nodes quota approved for your subscription.
+>VCF portable subscription is applied at the host level and must cover all the physical cores on a host.
+>Hence, quota will be approved only for the maximum number of nodes which the VCF portable subscription covers. For example, if you have purchased 1000 cores for portability and requesting for AV36P, you can get a maximum of 27 nodes quota approved for your subscription.
 >
 >That is, 36 physical CPU cores per AV36P node. 27 nodes = 27\*36 = 972 cores. 28 nodes = 28\*36 = 1008 cores. If you have purchased 1000 cores for portability, you can only use up to 27 AV36P nodes under your portable VCF.
 
-## Register your VCF license with Azure VMware Solution
+## Register your VCF subscription with Azure VMware Solution
 
-To get your quota request approved, you must first register the VCF portable license details with Microsoft. Quota will be approved only after the entitlements are provided. Expect to receive a response in 1 to 2 business days. 
+To get your quota request approved, you must first register the VCF portable subscription details with Microsoft. Quota will be approved only after the entitlements are provided. Expect to receive a response in 1 to 2 business days. 
 
-### How to register the VCF license keys 
+### How to register the VCF subscription keys 
 
-- Email your VCF license entitlements (and VMware vDefender Firewall license entitlements if to enable vDefender Firewall on Azure VMware Solution) to the following email address: [email protected]. 
+- Email your VCF subscription entitlements (and VMware vDefender Firewall license entitlements if to enable vDefender Firewall on Azure VMware Solution) to the following email address: [email protected]. 
 
 - VCF entitlement sample: 
-:::image type="content" source="media/vmware-cloud-foundations-license-portability/vcf-entitlements.png" alt-text="Screenshot of how to register your VCF portable license entitlements with Microsoft." border="false":::
+:::image type="content" source="media/vmware-cloud-foundations-license-portability/vcf-entitlements.png" alt-text="Screenshot of how to register your VCF portable subscription entitlements with Microsoft." border="false":::
 
 >[!NOTE]
 >
->The "Qty" represents the number of cores eligible for VCF license portability. Your quota request should not surpass the number of nodes equivalent to your entitled cores from Broadcom. If your quota request exceeds the approved cores, the quota request will be granted only for the number of nodes that are fully covered by the entitled cores.
+>The "Qty" represents the number of cores eligible for VCF subscription portability. Your quota request should not surpass the number of nodes equivalent to your entitled cores from Broadcom. If your quota request exceeds the approved cores, the quota request will be granted only for the number of nodes that are fully covered by the entitled cores.
 
 - VCF with VMware vDefend entitlement sample: 
 :::image type="content" source="media/vmware-cloud-foundations-license-portability/vcf-vdefend-entitlements.png" alt-text="Screenshot of VCF with Vmware vDefend entitlement sample format." border="false":::
 
 Sample Email to register portable VCF entitlements: 
-:::image type="content" source="media/vmware-cloud-foundations-license-portability/email-register-vcf.png" alt-text="Screenshot of sample email to register portable VCF license." border="true":::
+:::image type="content" source="media/vmware-cloud-foundations-license-portability/email-register-vcf.png" alt-text="Screenshot of sample email to register portable VCF subscription." border="true":::
 
 The VMware vDefend Firewall add-on CPU cores required on Azure VMware Solution depend on the planned feature usage: 
 - For NSX Distributed Firewall: same core count as VCF core count. 
@@ -83,24 +82,24 @@ The VMware vDefend Firewall add-on CPU cores required on Azure VMware Solution d
 
 >[!NOTE] 
 > 
-> The VCF license entitlements submitted to Microsoft will be securely retained for our reporting purpose. You can request the permanent deletion of this data from Microsoft's systems at any time. Once the automated validation process is in place, your data will be automatically deleted from all Microsoft systems, which may take up to 120 days. Additionally, all your VCF entitlement data will be permanently deleted within 120 days any time you migrate to an Azure VMware Solution-owned VCF solution. 
+> The VCF subscription entitlements submitted to Microsoft will be securely retained for our reporting purpose. You can request the permanent deletion of this data from Microsoft's systems at any time. Once the automated validation process is in place, your data will be automatically deleted from all Microsoft systems, which may take up to 120 days. Additionally, all your VCF entitlement data will be permanently deleted within 120 days any time you migrate to an Azure VMware Solution-owned VCF solution. 
 
 ## Creating/scaling a Private Cloud
 
-You can create your Azure VMware Solution Private Cloud the same way as today regardless of your licensing method, that is, whether you bring your own VCF portable license or use the Azure VMware Solution-owned VCF license. [Learn more](/azure/azure-vmware/plan-private-cloud-deployment). Your decision of licensing is a cost optimization choice and doesn't affect your deployment workflow.
+You can create your Azure VMware Solution Private Cloud the same way as today regardless of your licensing method, that is, whether you bring your own VCF portable license or use the Azure VMware Solution-owned VCF subscription. [Learn more](/azure/azure-vmware/plan-private-cloud-deployment). Your decision of licensing is a cost optimization choice and doesn't affect your deployment workflow.
 
 For example, you want to deploy 10 nodes of AV36P node type.
 
 **Scenario 1:**
-"I want to purchase my VCF subscription from Broadcom and use the license portability offering on Azure VMware Solution."
+"I want to purchase my VCF subscription from Broadcom and use the VCF subscription portability offering on Azure VMware Solution."
 
-1. Create quota request for AV36P nodes. Declare your own VCF portable license intent and the number of cores you're entitled for portability. 
+1. Create quota request for AV36P nodes. Declare your own VCF portable subscription intent and the number of cores you're entitled for portability. 
 2. Register your VCF entitlements via email to Microsoft.  
-3. Optional- to use the Reserved Instance pricing purchase AV36P VCF BYOL Reserved Instance. You can skip this step to use the pay-as-you-go pricing for the VCF license portability.
+3. Optional- to use the Reserved Instance pricing purchase AV36P VCF BYOL Reserved Instance. You can skip this step to use the pay-as-you-go pricing for the VCF subscription portability.
 4. Create your Private Cloud with AV36P nodes. 
 
 **Scenario 2:**
-"I want to let Azure VMware Solution manage my license for all my Azure VMware Solution private cloud."
+"I want to let Azure VMware Solution manage my VCF subscription for all my Azure VMware Solution private cloud."
 
 1. Create quota request for AV36P node type. 
 2. Optional- Purchase AV36P Reserved Instance.  
@@ -115,8 +114,24 @@ If you're currently managing your own VCF licensing for Azure VMware Solution an
 1. Create a support request to inform us of your intent to convert.
 2. Exchange RI- If you have any active RI with VCF BYOL, exchange them for non-VCF BYOL RI. For instance, you can [exchange your AV36P VCF BYOL RI for an AV36P](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations). 
 
-If you're an existing Azure VMware Solution customer using Azure VMware Solution-owned licensing deployments and wish to transition to the license portability (VCF BYOL) offering, you can also easily make the switch without any changes to your Private Cloud deployments by registering your VCF entitlements with Microsoft. 
+If you're an existing Azure VMware Solution customer using Azure VMware Solution-owned licensing deployments and wish to transition to the VCF subscription portability (VCF BYOL) offering, you can also easily make the switch without any changes to your Private Cloud deployments by registering your VCF entitlements with Microsoft. 
 
 >[!NOTE]
 >
->You need to purchase the VCF entitlements from Broadcom for all cores that match your current Azure VMware Solution deployment. For instance, if your Azure subscription has a Private Cloud with 100 AV36P nodes, you must purchase VCF subscription for atleast 3600 cores from Broadcom to convert to VCF BYOL offering.  
+>You need to purchase the VCF entitlements from Broadcom for all cores that match your current Azure VMware Solution deployment. For instance, if your Azure subscription has a Private Cloud with 100 AV36P nodes, you must purchase VCF subscription for atleast 3600 cores from Broadcom to convert to VCF BYOL offering.
+
+## Onboarding to VCF portability checklist
+
+**Scenario 1:**
+"I am converting existing AVS Private Cloud to VCF BYOL." 
+
+1. Get VCF subscription portability for Azure VMware Solution proof-of-purchase from Broadcom for all cores used in your AVS Private Cloud in that Azure Subscription.
+2. If you currently have Reserved Instance (RI) for the AVS node type, exchange RI for the corresponding VCF BYOL node type. For example, if you have 1 year RI for 10 AV36P nodes, you will need to place an exchange RI order for AV36P VCF BYOL node type. All the [Azure RI exchange rules](/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations) will apply. **NOTE:** If you register your VCF subscription without this step, you will be charged BYOL Pay-as-you-go pricing by default for your usage.
+3. Register your VCF subscription with Azure VMware Solution.
+
+**Scenario 2:**
+"I am creating a new AVS Private Cloud with VCF BYOL." 
+
+1. Get VCF subscription portability for Azure VMware Solution proof-of-purchase from Broadcom for all cores used in your AVS Private Cloud in that Azure Subscription.
+2. [Request host quota](azure/azure-vmware/request-host-quota-azure-vmware-solution) for Azure VMware Solution.
+3. If you want to use the Reserved Instance (RI) pricing, purchase RI for the required node type with VCF BYOL. **NOTE:** If you register your VCF subscription without this step, you will be charged BYOL Pay-as-you-go pricing by default for your usage.