Merge branch 'docs-editor/manage-license-billing-1737662261' of https://github.com/MikeRayMSFT/sql-docs-pr into docs-editor/manage-license-billing-1737662261

Author: MikeRayMSFT

docs/sql-server/azure-arc/includes/billing-after-failover.md

@@ -9,7 +9,4 @@ ms.custom: ignite-2023
 
 ### ESU billing after failover
 
-During the failovers, the extension is aware of the transition and automatically switches the ESU billing to the active replica without new bill-back charges and follow below logic
-
-- If the period of failover <= 90 days, ESU billback occurs only from the prior watermark of usage upload.
-- If the period of failover > 90 days, ESU billback occurs from the start of the ESU period.
+During the failovers, the extension is aware of the transition and automatically switches the ESU billing to the active replica without new bill-back charges.

docs/sql-server/azure-arc/includes/manage-passive-instance.md

@@ -9,4 +9,4 @@ ms.custom: ignite-2023
 
 SQL Server licenses with Software Assurance or pay-as you go (`PAYG`) can benefit from free passive instances of SQL Server for their high availability and disaster recovery (HADR) configurations. For more information about the failover benefits, see the section "Licensing SQL Server for high availability and disaster recovery" in the [SQL Server licensing guide](https://go.microsoft.com/fwlink/p/?linkid=2215573).
 
-To help you manage the failover benefits and remain compliant, Azure Extension for SQL Server automatically detects the passive instances for availability groups (AGs) or failover clustered instances (FCIs) and reflects the use of the SQL Server software by emitting special $0 meters for disaster recovery, as long as you properly configured the LicenseType property. For more information, see [Metering software usage](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-license-billing?view=sql-server-ver16#usage-metering) later in this article.
+To help you manage the failover benefits and remain compliant, Azure Extension for SQL Server automatically detects the passive instances for availability groups (AGs) or failover clustered instances (FCIs) and reflects the use of the SQL Server software by emitting special $0 meters for disaster recovery, as long as you configured the LicenseType property to `Paid` or `PAYG`. For more information, see [Metering software usage](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-license-billing?view=sql-server-ver16#usage-metering). 

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

@@ -46,7 +46,7 @@ For each of these options, you have to decide how you want to pay for the licens
 
 | Payment option | V-core licensing | P-core licensing without VMs | P-core licensing with unlimited virtualization |
 | --- | --- | --- | --- |
-| Subscribe to the service through Microsoft Azure by using a pay-as-you-go method | Yes | Yes | Yes |
+| Subscribe to the service through Microsoft Azure by using a pay-as-you-go (PAYG) method | Yes | Yes | Yes |
 | Bring your own license with Software Assurance or a SQL Server subscription <sup>1</sup> | Yes | Yes | Yes |
 | Bring your own license without Software Assurance <sup>2</sup> | Yes | Yes | No |
 
@@ -214,15 +214,13 @@ For information, see:
 - All replicas present in the operating system environment (OSE) must be secondary.
 - No user database outside of an AG, irrespective of [database state](../../relational-databases/databases/database-states.md#database-state-definitions)).
 - No active connection to any user database.
-- License type is set to `Paid` or `PAYG`.
 
 If there are multiple SQL Server instances on the OSE, all instances and replicas must meet the conditions above.
 
 ### To qualify as passive node of failover clustered Instance (FCI)
 
 - The node must be passive of all FCIs present.
 - There is no standalone instance present in the node that does not qualify for AG passive replica.
-- License type is set to `Paid` or `PAYG`.
 
 ### Limitations