Merge pull request #33497 from anosov1960/docs-editor/manage-license-billing-1741906791

Update manage-license-billing.md

Author: prmerger-automator[bot]

docs/sql-server/azure-arc/extended-security-updates.md

@@ -98,7 +98,7 @@ The option of subscribing to SQL Server ESUs by physical cores with unlimited vi
 - Your infrastructure and the selected payment method support the unlimited virtualization benefit for ESU.
 - Subscribing to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESUs by v-cores is more expensive than subscribing by the p-cores of the host.
 
-To use the unlimited virtualization benefit, you need to create a *SQLServerEsuLicense* resource that covers the specific *SQL Server - Azure Arc* instances that you intend to include. For details about managing *SQLServerEsuLicense* resources, see [Manage the unlimited virtualization benefit for a SQL Server ESU subscription](manage-configuration.md#manage-pcore-esu-license).
+To use the unlimited virtualization benefit, you need to create a *SQLServerEsuLicense* resource that represents one or more physical hosts. The covered SQL Server instances must be connected to Azure Arc and configured to use the p-core ESU license. For details about managing *SQLServerEsuLicense* resources, see [Manage the unlimited virtualization benefit for a SQL Server ESU subscription](manage-configuration.md#manage-pcore-esu-license).
 
 > [!CAUTION]  
 > The unlimited virtualization benefit isn't available to VMs running on infrastructure from any of the [listed providers](https://aka.ms/listedproviders). These VMs can be licensed only by v-cores. If you create a *SqlServerEsuLicense* resource with the intent of licensing these VMs by using unlimited virtualization, you'll be charged for the consumption of v-cores based on the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] configuration of the host. Any existing p-core licenses don't apply to offset such charges.
@@ -107,8 +107,6 @@ For more information about licensing by physical cores with unlimited virtualiza
 
 A single *SqlServerEsuLicense* resource can cover multiple virtual machines connected to Azure Arc. It includes several properties that define how the license is applied and billed.
 
-To qualify, each *Machine - Azure Arc* resource must be configured to use a physical core ESU license. Otherwise, the *Machine - Azure Arc* resource is billed for ESUs individually.
-
 ### License details
 
 The **License details** tab includes the standard Azure properties and the ESU license-specific settings:
@@ -129,12 +127,13 @@ The **License details** tab includes the standard Azure properties and the ESU l
 
 You can create the license resource in a resource group in any of the [supported regions](overview.md#supported-azure-regions). The location of the resource is set to the location of the selected resource group by default, but you can change it to a different region.
 
-The location of the license resource doesn't affect the scope. It applies to all *Machine - Azure Arc* resources in the selected license scope, regardless of the regions where these resources are onboarded.
-
+The location of the license resource doesn't affect the scope. It applies to all *Machine - Azure Arc* resources in the selected license scope, regardless of the regions where these resources are onboarded. You can associate multiple license resources with the same scope or overlapping scopes. For example, you can add a new license when you deploy additional physical servers for the increased demand.
+  
 > [!IMPORTANT]  
-> You can associate multiple license resources with the same scope or overlapping scopes. For example, you can add a new license when you deploy additional physical servers during temporary bursts of activity, or to reflect unexpected growth.
->  
-> All the virtual machines running on these physical servers must be connected to Azure Arc in the scope of the license resource. And they must have the `UsePhysicalEsuCoreLicense` host configuration property set to `True`. For more information, see [Use a physical core ESU license](manage-configuration.md#use-physical-core-esu-license).
+> When using the unlimited virtualization benefit, make sure that
+> 1. All the virtual machines on the licensed physical servers are connected to Azure Arc.
+> 1. They are in the scope specified in the license. For example, they are in the same subscription or resource group.
+> 1. They have the `UsePhysicalEsuCoreLicense` host configuration property set to `True`. For more information, review [Use a physical core ESU license](manage-configuration.md#use-physical-core-esu-license).
 
 ### License activation
 

docs/sql-server/azure-arc/manage-license-billing.md

@@ -130,14 +130,14 @@ The option of licensing SQL Server by physical cores with unlimited virtualizati
 - Your infrastructure and the selected payment method support the unlimited virtualization benefit.
 - Licensing your SQL Server instances by v-cores is more expensive than licensing the p-cores of the host.
 
-To use the unlimited virtualization benefit, you need to create a *SQLServerLicense* resource that covers the specific *SQL Server - Azure Arc* instances that you intend to include. For details about creating *SQLServerLicense* resources, see [Create a SQL Server license](manage-configuration.md#create-license-resource).
+To use the unlimited virtualization benefit, you need to create a _SQLServerLicense_ resource that represents one or more physical hosts. The covered SQL Server instances must be connected to Azure Arc and configured to use the p-core license. For details about creating _SQLServerLicense_ resources, see [Create a SQL Server license](/sql/sql-server/azure-arc/manage-configuration).
 
 > [!CAUTION]  
 > The unlimited virtualization benefit isn't available to VMs running on infrastructure from any of the [listed providers](https://aka.ms/listedproviders). These VMs can be licensed only by v-cores. If you create a *SQLServerLicense* resource with the intent of licensing these VMs by using unlimited virtualization, you'll be charged for the consumption of v-cores based on the SQL Server configuration of the host. Any existing p-core licenses don't apply to offset such charges.
 
 For more information about licensing by physical cores with unlimited virtualization, see the section "Licensing for maximum virtualization" in the [SQL Server licensing guide (download link)](https://go.microsoft.com/fwlink/p/?linkid=2215573).
 
-A single *SqlServerLicense* resource can cover multiple virtual machines connected to Azure Arc. It includes the following properties that define how the license is applied and billed.
+A single _SqlServerLicense_ resource can cover multiple virtual machines connected to Azure Arc. Its properties define how the license is applied and billed.
 
 ### License category