Publish automatic recurrent billing

MikeRayMSFT · MikeRayMSFT · commit f04c6334b8a0 · 2025-07-16T16:52:28.000-07:00
diff --git a/docs/sql-server/azure-arc/extended-security-updates.md b/docs/sql-server/azure-arc/extended-security-updates.md
@@ -178,9 +178,9 @@ For information, see:
 
 [!INCLUDE [manage-passive-instance](includes/manage-passive-instance.md)]
 
-[!INCLUDE [billing-after-failover](includes/billing-after-failover.md)]
+The ESU subscription enabled on a connected server with passive SQL Server instances doesn't incur the ESU charges. This way you can guarantee that future ESUs will be applied to that server. To qualify, all SQL Server instances on this server must meet the passivity criteria defined in [Manage passive license for high availability and disaster recovery](manage-license-billing.md#free-dr).
 
-For additional information on passive replica detection logic, review [Manage passive license for high availability and disaster recovery](manage-license-billing.md#manage-passive-license-for-high-availability-and-disaster-recovery).
+[!INCLUDE [billing-after-failover](includes/billing-after-failover.md)]
 
 ## <a id="server-cal"></a> Manage SQL Server instances that use a Server+CAL license
 
@@ -234,7 +234,7 @@ The usage of the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESU
 
 - [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] ESU subscription usage is reported per OSE whether one or multiple [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances are installed on the same OSE.
 
-- If multiple out-of-support [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances of the same version are installed on the same OSE, the highest [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] edition defines the ESU subscription meter that's sent every hour.
+- If multiple out-of-support [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances of the same version are installed on the same OSE, the highest [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] edition defines the ESU subscription meter.
 
 - If multiple out-of-support instances of both [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)] and [!INCLUDE [sssql14-md](../../includes/sssql14-md.md)] are installed on the same OSE, with the same or different editions, one instance of the same version is billed separately because they have different prices and bill-back periods.
 
@@ -320,15 +320,15 @@ If the Arc enabled machine goes offline and reconnects to Azure in a different s
 >
 > This difference is expected, and it should be a one-time charge.
 >
-> During the following months, you should see only the regular hourly charges. Additional bill-back charges could be added in cases of connectivity disruptions, but they're typically much smaller amounts.
+> In later months, you should see only the regular hourly charges. Additional bill-back charges could be added to account for the connectivity disruptions, but they're typically much smaller amounts.
 
 ## Related content
 
 - [Product terms for SQL Server enabled by Azure Arc](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/eaeas#ServiceSpecificTerms)
 - [SQL Server licensing guide (download link)](https://download.microsoft.com/download/e/2/9/e29a9331-965d-4faa-bd2e-7c1db7cd8348/SQL_Server_2019_Licensing_guide.pdf)
 - [SQL Server 2022 pricing and licensing](https://www.microsoft.com/sql-server/sql-server-2022-pricing)
 - [Configure SQL Server enabled by Azure Arc](manage-configuration.md)
-- [Frequently asked questions about billing](faq.yml#billing)
+- [Frequently asked questions about billing](faq.yml#recurring-pay-as-you-go-billing)
 - [Extended Security Updates: Frequently asked questions](../end-of-support/extended-security-updates-frequently-asked-questions.md)
 - [Prerequisites - SQL Server enabled by Azure Arc](prerequisites.md)
 - [Manage the unlimited virtualization benefit for a SQL Server ESU subscription](manage-configuration.md#manage-pcore-esu-license)
diff --git a/docs/sql-server/azure-arc/faq.yml b/docs/sql-server/azure-arc/faq.yml
@@ -27,7 +27,7 @@ sections:
         answer: |
            No. Microsoft only captures metadata and information about your SQL Server to help troubleshoot and inventory. The data sent doesn't include user data or about your utilization of SQL Server.
 
-  - name: Billing
+  - name: Pay-as-you-go billing
     questions:
       - question: Does pay-as-you-go billing stop charging when connectivity between the SQL Server resource and Azure is temporarily interrupted?
         answer: No, Intermittent internet connectivity doesn't stop the pay-as-you-go billing. The usage is reported and accounted for by the billing logic when the connectivity is restored.
@@ -50,6 +50,26 @@ sections:
       - question: Can I switch from pay-as-you-go to license and vice versa?
         answer: Yes, you can change your selection. To change, run SQL Server Setup again, and choose the **Maintenance** tab, then select **Edition Upgrade**. The mode is now changed to Enterprise license. To revert back to pay-as-you-go, you can use the same steps and change the setting.
 
+      - question: I have an enterprise or a small business account with Microsoft, do I need to enable the recurring pay-as-you-go billing?
+        answer: |
+          No. At this point, recurring billing is only enabled in the cloud solution provider (CSP) managed Azure subscriptions.
+
+      - question: How do I ensure that my VM and SQL server are not billed when it is disconnected or turned off intentionally?
+        answer: |
+          If the machine is offline for less than 30 days and then reconnects, the uploaded SQL Server usage will reflect the offline period, and the monthly invoice will account for it. If you keep the machine offline for longer than 30 days, the pay-as-you-go billing will resume when the machine is back online and reconnects to Azure Arc.
+
+      - question: If I have a server that is regularly disconnected for more than 30 days, what should I do?
+        answer: |
+          - If you take your VM offline intentionally for a period longer than 30 days, and stop using SQL Server, the pay-as-you-go billing will resume when the machine is back online and reconnects to Azure Arc.
+          - If your SQL Server instance is continuously running during the disconnected time period, you must restore the connectivity to stay compliant. Review [Troubleshoot extension](troubleshoot-extension.md).
+
+      - question: How can I be notified about when a given machine does not send usage data when expected or when recurring billing has happened or is happening?
+        answer: |
+          You can:
+          - See the billing mode of each machine in the Arc-enabled SQL Server Billing dashboard in the Azure portal.
+          - Write your own ARG query to get the billing mode and last billed data points.
+          - Subscribe to Activity Log events for when usage records are not received when expected or when recurring billing starts or is happening. Review [Use activity logs with SQL Server enabled by Azure Arc](activity-logs.md).
+
   - name: Security
     questions:
       - question: What are the best practices for security?
@@ -92,6 +112,28 @@ sections:
       - question: How does SQL Server enabled by Azure Arc license management work with associated services? 
         answer: The associated services are represented as SQL Server instances in Azure Resource Manager (ARM) with a service_type property reflecting if it is an engine or an associated service installation. Review [Manage licensing and billing](manage-license-billing.md) and [Extended Security Updates](extended-security-updates.md) for details. 
 
+  - name: "Recurring pay-as-you-go billing"
+    questions:
+      - question: I have an enterprise or a small business account with Microsoft, can I enable recurring pay-as-you-go billing?
+        answer: |
+          No. At this point, recurring billing is only offered to cloud solution provider (CSP) managed customers.
+
+      - question: How do I ensure that my VM and SQL server are not billed when it is disconnected or turned off intentionally?
+        answer: |
+          If the machine is offline for less than 30 days and then reconnects, the uploaded SQL Server usage will reflect the offline period, and the monthly invoice will account for it. If you keep it offline for longer than 30 days, the billing will resume when the machine is back online and reconnects.
+
+      - question: How can I be notified about when a given machine does not send usage data when expected or when recurring billing has happened or is happening?
+        answer: |
+          You can:
+          - See the billing mode of each machine in the Arc-enabled SQL Server Billing dashboard in the Azure portal.
+          - Write your own ARG query to get the billing mode and last billed data points.
+          - Subscribe to Activity Log events for when usage records are not received when expected or when recurring billing starts or is happening.
+          Review [Manage recurrent billing for pay-as-you go licenses](manage-pay-as-you-go-transition.md) for details. 
+
+      - question: Can I enable recurring pay-as-you-go billing for my Arc-enabled SQL Servers that use the license with SA to ensure continuous reclassification?
+        answer: |
+          No. Recurring billing is a feature of pay-as-you-go subscriptions.
+
 additionalContent: |
 
      ## Related content
diff --git a/docs/sql-server/azure-arc/manage-configuration.md b/docs/sql-server/azure-arc/manage-configuration.md
@@ -738,5 +738,5 @@ resources
 - [SQL Server 2022 pricing](https://www.microsoft.com/sql-server/sql-server-2022-pricing)
 - [SQL Server installation guide](../../database-engine/install-windows/install-sql-server.md)
 - [What are Extended Security Updates for SQL Server?](../end-of-support/sql-server-extended-security-updates.md)
-- [Frequently asked questions](faq.yml#billing)
+- [Frequently asked questions](faq.yml#recurring-pay-as-you-go-billing)
 - [Configure automatic updates for SQL Server enabled by Azure Arc](update.md)
diff --git a/docs/sql-server/azure-arc/manage-license-billing.md b/docs/sql-server/azure-arc/manage-license-billing.md
@@ -91,6 +91,8 @@ The following license types are supported when you're licensing v-cores:
 
 - The pay-as-you-go hourly charges are issued only when SQL Server is running on the machine at any point within a particular hour, and if the machine is online.
 
+- You can configure recurrent billing. For details, review [Manage recurrent billing for SQL Server enabled by Azure Arc with pay-as-you-go license](manage-pay-as-you-go-transition.md).
+
 - By selecting a license with Software Assurance, you attest that you have Enterprise or Standard licenses with active Software Assurance or an active SQL Server subscription license.
 
 - For SQL Server Enterprise, Standard, or Web edition instances of SQL Server licensed from cloud service providers or hosting service providers using the Service Provider Licensing Agreement (SPLA), use `license only` for the license type.
@@ -209,19 +211,23 @@ For information, see:
 - [Creating Enterprise and Organization Azure Dev/Test Subscriptions](/azure/devtest/offer/quickstart-create-enterprise-devtest-subscriptions).
 - The section "Licensing SQL Server for non-production use" in the [SQL Server licensing guide (download link)](https://go.microsoft.com/fwlink/p/?linkid=2215573).
 
-## Manage passive license for high availability and disaster recovery
+## <a id="free-dr"></a> Manage passive license for high availability and disaster recovery
 
 [!INCLUDE [manage-passive-instance](includes/manage-passive-instance.md)]
 
 ### To qualify as passive instance for an availability group (AG)
 
 - All replicas present in the operating system environment (OSE) must be a secondary replica of an Always On availability group or the forwarder of a distributed availability group.
 - No standalone database outside of an AG irrespective of [database state](../../relational-databases/databases/database-states.md#database-state-definitions).
-- No active connections to any database except master, msdb, tempdb, or model databases.
+- No active connections to any database except `master`, `msdb`, `tempdb`, or `model` databases.
 - No instances of [associated services](#manage-ssxs) in the same OSE.
 
 If there are multiple SQL Server instances on the OSE, all instances and replicas must meet the conditions above.
 
+> [!NOTE]  
+> You can query DMVs or issue `DATABASE BACKUP` commands as long as your connections are limited to `master`, `msdb`, `tempdb`, or `model` databases. These operations will not disqualify your passive instance(s). 
+
+
 ### To qualify as passive node of failover clustered Instance (FCI)
 
 
@@ -233,16 +239,16 @@ If there are multiple SQL Server instances on the OSE, all instances and replica
 
 The current passive instance detection logic has the following limitations.
 
-- The checks are done every hour. A failover within the hour may or may not bill both replicas.
+- The checks are done hourly. A failover within the hour may or may not bill both replicas.
 - Passive instances for other HADR technologies like log shipping or mirroring are not automatically detected at this time.
-- The detection logic does not support free disaster recovery testing or monitoring connections like database consistency checks, backups or monitoring resource usage data.
+- The detection logic does not support free disaster recovery testing 
+
+- Monitoring resource usage data on the replica requires an app attribute in the connection string: `App = Monitoring or Backup`.
 
 If you are unable to work within these limitations, you can use volume licensing instead of `PAYG`. For details, review [Configure SQL Server enabled by Azure Arc](manage-configuration.md).
 
 [!INCLUDE [billing-after-failover](includes/billing-after-failover.md)]
 
-For additional information, review [SQL Server Extended Security Updates enabled by Azure Arc](extended-security-updates.md#manage-hadr).
-
 ## <a id="server-cal"></a> Manage SQL Server instances that use a Server+CAL license
 
 You can connect any licensed SQL Server instance to Azure Arc, including instances that use the Server+CAL licensing model. If your instance uses this license, you must set the license type to `LicenseOnly`, even if you have active Software Assurance for it.
@@ -279,7 +285,7 @@ The usage of the SQL Server software is reported once an hour. The specific mete
 
 - If two or more instances of the same edition are installed, the first instance in alphabetical order reports usage.
 
-- The combination of the selected `LicenseType` value and the highest SQL Server edition installed on the OSE defines which meter is sent every hour.
+- The combination of the selected `LicenseType` value and the highest SQL Server edition installed on the OSE defines which meter is sent.
 
 For more information, see [SQL Server Licensing Resources and Documents](https://www.microsoft.com/licensing/docs/view/SQL-Server).
 
@@ -325,6 +331,7 @@ The following table shows the meter SKUs that are used for metering and billing
 
 - [Product terms for SQL Server enabled by Azure Arc](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/eaeas#ServiceSpecificTerms)
 - [SQL Server Licensing Resources and Documents](https://www.microsoft.com/licensing/docs/view/SQL-Server)
+
 - [SQL Server 2022 pricing and licensing](https://www.microsoft.com/sql-server/sql-server-2022-pricing)
 - [Configure SQL Server enabled by Azure Arc](manage-configuration.md)
-- [Frequently asked questions](faq.yml#billing)
+- [Frequently asked questions](faq.yml#recurring-pay-as-you-go-billing)
diff --git a/docs/sql-server/azure-arc/manage-pay-as-you-go-transition.md b/docs/sql-server/azure-arc/manage-pay-as-you-go-transition.md
diff --git a/docs/toc.yml b/docs/toc.yml
