Arc SQL | February 25 associated services billing

MikeRayMSFT · MikeRayMSFT · commit 911075a3c8cb · 2025-03-07T09:11:36.000-08:00
diff --git a/docs/sql-server/azure-arc/extended-security-updates.md b/docs/sql-server/azure-arc/extended-security-updates.md
@@ -186,6 +186,21 @@ For additional information on passive replica detection logic, review [Manage pa
 
 You can connect any licensed [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instance to Azure Arc, including instances that use the Server+CAL licensing model. However, the ESU subscription enabled by Azure Arc isn't available for the out-of-support Server+CAL licensing model. If you want to receive ESUs, you can set the license type to `PAYG` and then enable the ESU subscription.
 
+## <a id="esu-subscription-ssxs"></a> Manage SQL Server ESU subscriptions for the associated services
+
+SQL Server ESU subscriptions support the following associated services:
+
+[!INCLUDE [sql-server-associated-services](includes/sql-server-associated-services.md)]
+
+For details, see [Feature availability by service type](overview.md#feature-availability-by-service-type).
+
+The SQL Server associated services are billed for ESU using the regular ESU meters. For details, see  [Understand ESU usage meters](extended-security-updates.md#esu-usage-metering).
+
+> [!IMPORTANT]
+>
+> - The SQL Server associated service installations are billed for the ESU subscription only when they are installed on the machine as a standalone instance (without SQL Server engine). Otherwise, the SQL Server engine instance is billed.
+> - If a p-core ESU license is activated for the corresponding scope and the machine is configured to use it, the SQL Server associated service is not individually billed for ESU even if it is a standalone instance (without SQL Server engine). For details, see [Manage resources in the scope of an ESU p-core license](manage-configuration.md#manage-esu-license-resources).
+
 ## <a id="license-transition"></a> Manage the transition from a p-core ESU license to a v-core ESU license
 
 Because the p-core ESU license is billed with an ESU meter for the Enterprise edition, it's cost-effective when the out-of-support [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] instances are colocated on a set of designated physical hosts. As you upgrade the individual instances or migrate them to Azure, you might lose the cost-effectiveness of the p-core ESU license. Using the v-core ESU licensing might then become more attractive. You can terminate the p-core ESU license and switch to billing the individual VMs for the ESU subscriptions.
diff --git a/docs/sql-server/azure-arc/faq.yml b/docs/sql-server/azure-arc/faq.yml
@@ -85,7 +85,7 @@ sections:
         answer: Yes, least privilege mode is currently in preview for SQL Server enabled by Azure Arc. When this mode is generally available, least privilege mode will become the default configuration. Existing deployments will also be migrated automatically to least privilege mode to bolster security. Learn more about the permission assigned at [Configure Windows service accounts and permissions for Azure extension for SQL Server](configure-windows-accounts-agent.md).
 
       - question: How do I set the minimum permissions to deploy SQL Server enabled by Azure Arc?
-        answer: Least privileges mode uses the minimum amount of permissions to deploy SQL Server enabled by Azure Arc.
+        answer: Least privilege mode uses minimum permissions to deploy SQL Server enabled by Azure Arc. To enable least privilege mode, review [Operate SQL Server enabled by Azure Arc with least privilege](configure-least-privilege.md).
 
 additionalContent: |
 
diff --git a/docs/sql-server/azure-arc/includes/features-service-type.md b/docs/sql-server/azure-arc/includes/features-service-type.md
@@ -0,0 +1,32 @@
+---
+author: MikeRayMSFT
+ms.author: mikeray
+ms.reviewer: randolphwest
+ms.date: 02/26/2025
+ms.topic: include
+ms.custom:
+---
+
+The following table identifies features available by [!INCLUDE [ssnoversion-md](../../../includes/ssnoversion-md.md)] service type:
+
+| Feature | SQL Server Database Engine | SQL Server Integration Services | SQL Server Reporting Services | SQL Server Analysis Services | Power BI Report Server |
+| --- | --- | --- | --- | --- | --- |
+| [Connect to Azure Arc](../connect.md) | Yes | Yes | Yes | Yes | Yes |
+| [Azure pay-as-you-go billing](../manage-configuration.md) | Yes | Yes | Yes | Yes | Yes |
+| [ESU subscription](../manage-license-billing.md) | Yes | Yes | Yes | Yes | Yes |
+| SQL Server inventory | Yes | Yes | Yes | Yes | Yes |
+| [Best practices assessment](../assess.md) | Yes | No | No | No | No |
+| [Migration readiness (preview)](../migration-assessment.md) | Yes | No | No | No | No |
+| [Database inventory](../view-databases.md#inventory-databases) | Yes | Not applicable | Not applicable | Not applicable | Not applicable |
+| [Microsoft Entra ID authentication](../../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md)  | Yes <sup>1</sup> | No | No | No | No |
+| [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-sql-usage) | Yes | No | No | No | No |
+| [Microsoft Purview: Govern using DevOps and data owner policies](/azure/purview/tutorial-register-scan-on-premises-sql-server) | Yes | No | No | No | No |
+| [Automated backups to local storage (preview)](../backup-local.md) | Yes | No | No | No | No |
+| [Point-in-time-restore](../point-in-time-restore.md) | Yes | No | No | No | No |
+| [Automatic updates](../update.md) | Yes | Yes | Yes | Yes | Yes |
+| [Failover cluster instances](../support-for-fci.md) | Yes | Not applicable | Not applicable | Not applicable | Not applicable |
+| [Always On availability groups](../manage-availability-group.md) | Yes | Not applicable | Not applicable | Not applicable | Not applicable |
+| [Monitoring (preview)](../sql-monitoring.md)  | Yes | No | No | No | No |
+| [Operate with least privilege](../configure-least-privilege.md) | Yes | Yes | Yes | Yes | Yes |
+
+<sup>1</sup> [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] only.
diff --git a/docs/sql-server/azure-arc/includes/sql-server-associated-services.md b/docs/sql-server/azure-arc/includes/sql-server-associated-services.md
@@ -0,0 +1,13 @@
+---
+author: MikeRayMSFT
+ms.author: mikeray
+ms.reviewer: randolphwest
+ms.date: 02/26/2025
+ms.topic: include
+ms.custom:
+---
+
+- [[!INCLUDE [SQL Server](../../../includes/ssnoversion-md.md)] [!INCLUDE [Analysis Services](../../../includes/ssasnoversion-md.md)]](/azure/analysis-services/)
+- [[!INCLUDE [SQL Server](../../../includes/ssnoversion-md.md)] [!INCLUDE [Integration Services](../../../includes/ssisnoversion-md.md)]](../../../integration-services/sql-server-integration-services.md)
+- [[!INCLUDE [SQL Server](../../../includes/ssnoversion-md.md)] [!INCLUDE [Reporting Services](../../../includes/ssrsnoversion-md.md)]](../../../reporting-services/create-deploy-and-manage-mobile-and-paginated-reports.md)
+- [Power BI Report Server](/power-bi/report-server/get-started)
diff --git a/docs/sql-server/azure-arc/manage-license-billing.md b/docs/sql-server/azure-arc/manage-license-billing.md
@@ -4,13 +4,15 @@ description: This article explains how to manage SQL Server licensing options. I
 author: anosov1960
 ms.author: sashan
 ms.reviewer: mikeray, randolphwest, maghan
-ms.date: 09/25/2024
+ms.date: 02/25/2025
 ms.topic: conceptual
 ---
 
 # Manage licensing and billing of SQL Server enabled by Azure Arc
 
-This article explains how to manage licensing and billing of SQL Server enabled by Azure Arc. SQL Server enabled by Azure Arc directly supports only the core-based licensing methods. For information about how you can manage SQL Server instances with a Server+CAL license, see [Manage SQL Server instances with a Server+CAL license](manage-license-billing.md#server-cal). The full range of the licensing options is described in the [SQL Server licensing guide (download link)](https://go.microsoft.com/fwlink/p/?linkid=2215573).
+This article explains how to manage licensing and billing of SQL Server enabled by Azure Arc. SQL Server enabled by Azure Arc directly supports only the core-based licensing methods. For information about how you can manage SQL Server instances with a Server+CAL license, see [Manage SQL Server instances with a Server+CAL license](manage-license-billing.md#server-cal). 
+
+The full range of the licensing options is described in the [SQL Server licensing guide (download link)](https://go.microsoft.com/fwlink/p/?linkid=2215573).
 
 ## Licensing and billing in the production environment
 
@@ -244,6 +246,24 @@ You can connect any licensed SQL Server instance to Azure Arc, including instanc
 
 If you converted your Enterprise Server+CAL license to a core-based license, you should set the license type to `Paid` or `PAYG`. The best practice is to also upgrade the SQL Server edition from Enterprise to Enterprise Core, because the latter provides the complete set of SQL Server capabilities. But even if you didn't upgrade the instances, Azure Extension for SQL Server monitors software usage as Enterprise Core.
 
+## <a id="manage-ssxs"></a> Manage SQL Server associated services
+
+[!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] enabled by Azure Arc provides license management for the following associated services:
+
+[!INCLUDE [sql-server-associated-services](includes/sql-server-associated-services.md)]
+
+For details, see [Feature availability by service type](overview.md#feature-availability-by-service-type).
+
+The SQL Server associated services are represented and managed for licensing purposes as SQL Server instances. Their usage is reported using the same metering rules as described in [Metering software usage](manage-license-billing.md#usage-metering).
+
+> [!IMPORTANT]
+>
+> The SQL Server associated service installations require a separate license only when they are installed on the machine as a standalone instance (without SQL Server database engine). Otherwise, separate license is not required.
+>
+> When the SQL Server associated service is a standalone instance (without SQL Server database engine) and the machine is configured using a pay-as-you-go subscription, the corresponding pay-as-you-go meters are activated for the instance.
+>
+> If a p-core license is activated as a pay-as-you-go subscription in the corresponding scope, and the machine is configured to use it, the SQL Server associated service is not individually billed for the pay-as-you-go subscription when it is a standalone instance (without SQL Server engine). For details, see [Use a physical core license](manage-configuration.md#use-physical-core-license).
+
 ## <a id="usage-metering"></a> Metering software usage
 
 The usage of the SQL Server software is reported once an hour. The specific meter is automatically selected based on the SQL Server edition and the number v-cores or p-cores visible to the OSE. The following rules apply:
diff --git a/docs/sql-server/azure-arc/overview.md b/docs/sql-server/azure-arc/overview.md
@@ -44,7 +44,11 @@ You can optimize the configuration of your SQL Server instances for best perform
 
 [!INCLUDE [entra-id](../../includes/entra-id.md)]
 
-Starting with [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)], Azure Arc enabled SQL Servers can utilize Microsoft Entra ID for authentication, bringing a modern centralized identity and access management solution to SQL Server. Microsoft Entra authentication provides greatly enhanced security over traditional username and password-based authentication, which is **not recommended**. For more information about the risks and challenges passwords pose, refer to ["What’s the solution to the growing problem of passwords?"](https://news.microsoft.com/features/whats-solution-growing-problem-passwords-says-microsoft/). Microsoft Entra authentication removes the need for self-managed secrets entirely when communicating with Azure resources, through managed identity authentication. For user-based authentication, Microsoft Entra ID supports enhanced security measures including multifactor authentication (MFA), single sign-on (SSO), and modern identity practices.
+Azure Arc enabled SQL Servers can utilize Microsoft Entra ID for authentication. This feature brings a modern centralized identity and access management solution to SQL Server. This feature requires [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] or later.
+
+Microsoft Entra authentication provides greatly enhanced security over traditional username and password-based authentication, which is **not recommended**. For more information about the risks and challenges passwords pose, refer to ["What’s the solution to the growing problem of passwords?"](https://news.microsoft.com/features/whats-solution-growing-problem-passwords-says-microsoft/).
+
+Microsoft Entra authentication removes the need for self-managed secrets entirely when communicating with Azure resources, through managed identity authentication. For user-based authentication, Microsoft Entra ID supports enhanced security measures including multifactor authentication (MFA), single sign-on (SSO), and modern identity practices.
 
 ## Microsoft Defender for Cloud
 
@@ -120,13 +124,9 @@ The following diagram illustrates the architecture of [!INCLUDE [ssazurearc](../
 
 [!INCLUDE [features-edition](includes/features-edition.md)]
 
-[!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] provides inventory and pay-as-you-go billing for the following services:
-
-- SQL Server Analysis Services
-- SQL Server Reporting Services
-- SQL Server Integration Services
+## Feature availability by service type
 
-Currently, Azure Arc does not provide additional management capabilities for these services.
+[!INCLUDE [features-service-type](includes/features-service-type.md)]
 
 [!INCLUDE [supported-configurations](includes/supported-configurations.md)]
 
diff --git a/docs/sql-server/azure-arc/release-notes.md b/docs/sql-server/azure-arc/release-notes.md
@@ -31,14 +31,13 @@ This release introduces:
 
 - Support for Windows 10 and Windows 11.
 
-- Pay-as-you go billing for the following services:
+- Support for SQL Server pay-as-you-go subscriptions and Extended Security Updates subscriptions for the following services:
 
-  - [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Analysis Services](../../includes/ssasnoversion-md.md)]
-  - [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Integration Services](../../includes/ssisnoversion-md.md)]
-  - [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Reporting Services](../../includes/ssrsnoversion-md.md)]
-  - Power BI Report Server
+  [!INCLUDE [sql-server-associated-services](includes/sql-server-associated-services.md)]
 
-In addition new documentation to describe how to connect without routing through the Internet: [Connect to Azure with a private path for SQL Server enabled by Azure Arc](configure-private-path.md).
+  Review [Manage licensing of SQL Server associated services](manage-license-billing.md#manage-ssxs) and [Manage SQL Server ESU subscriptions for the associated services](extended-security-updates.md#esu-subscription-ssxs)
+
+- New documentation that describes how to connect without routing through the Internet: [Connect to Azure with a private path for SQL Server enabled by Azure Arc](configure-private-path.md).
 
 ## January 29, 2025
 
@@ -64,10 +63,7 @@ Minor bug fixes. This release does not enable or introduce new features.
 
 Inventory additional service resources in portal (preview):
 
-- [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Analysis Services](../../includes/ssasnoversion-md.md)]
-- [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Integration Services](../../includes/ssisnoversion-md.md)]
-- [!INCLUDE [SQL Server](../../includes/ssnoversion-md.md)] [!INCLUDE [Reporting Services](../../includes/ssrsnoversion-md.md)]
-- Power BI Report Server
+[!INCLUDE [sql-server-associated-services](includes/sql-server-associated-services.md)]
 
 ### ESU update to bill-back calculation
 
