Merge pull request #37035 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-09 22:30 UTC

Author: learn-build-service-prod[bot]

azure-sql/database/hyperscale-automated-backups-overview.md

@@ -96,8 +96,12 @@ Deleted Hyperscale databases incur backup costs to support recovery to a point i
 
 Data storage size is included in the formula because allocated database storage isn't billed separately for a deleted database. For a deleted database, data is stored after deletion to enable recovery during the configured backup retention period.
 
+> [!NOTE]
+> The data backup storage size metric only reflects billable backup storage consumed beyond the free allowance of one full database size. The data backup storage size metric only emits a value *after* backup storage consumption exceeds the free allowance.
+
 Billable backup storage for a deleted database reduces gradually over time after it's deleted. It becomes zero when backups are no longer retained, and then recovery is no longer possible. If it's a permanent deletion and you no longer need backups, you can optimize costs by reducing retention before deleting the database.
 
+
 ### Monitor backup costs
 
 To understand backup storage costs:

azure-sql/managed-instance/restore-sample-database-quickstart.md

@@ -20,11 +20,9 @@ ms.custom:
 
 In this quickstart, you'll use SQL Server Management Studio (SSMS) to restore a database from Azure Blob Storage to [Azure SQL Managed Instance](sql-managed-instance-paas-overview.md). The quickstart restores the Wide World Importers sample database from a publicly available backup file using a Shared Access Signature (SAS) key.
 
-> [!NOTE]  
->
-> - For a video tutorial, see [Azure SQL Managed Instance- restore database backup](https://www.youtube.com/embed/RxWYojo_Y3Q).
-> - For more information on migration using Azure Database Migration Service, see [Tutorial: Migrate SQL Server to an Azure SQL Managed Instance using Database Migration Service](/azure/dms/tutorial-sql-server-to-managed-instance).
-> - For more information on various migration methods, see [SQL Server to Azure SQL Managed Instance guide](../migration-guides/managed-instance/sql-server-to-managed-instance-guide.md).
+> [!NOTE]
+> This quickstart is to restore a database that has been manually backed up to Azure Blob Storage. If you're looking to restore from an automated backup, see [Restore a database from an automated backup](recovery-using-backups.md).
+
 
 ## Prerequisites
 
@@ -36,11 +34,9 @@ This quickstart:
   - [Enable a public endpoint](public-endpoint-configure.md) on SQL Managed Instance. This approach is recommended for this quickstart.
   - [Connect to SQL Managed Instance from an Azure VM](connect-vm-instance-configure.md).
   - [Configure a point-to-site connection to SQL Managed Instance from on-premises](point-to-site-p2s-configure.md).
+- Requires a backup file stored in Azure Blob Storage. This quickstart uses a publicly available backup file for the Wide World Importers sample database, but you can also use your own backup file stored in your Azure Blob Storage account. For information on how to create a backup file and store it in Azure Blob Storage, see [Back up SQL Server databases to Azure Blob Storage](/sql/relational-databases/backup-restore/sql-server-backup-to-url).
 
-> [!NOTE]  
-> For more information on backing up and restoring a SQL Server database by using Blob Storage and a [shared access signature key](/azure/storage/common/storage-sas-overview), see [SQL Server Backup to URL](/sql/relational-databases/backup-restore/sql-server-backup-to-url).
-
-## Use the Restore wizard to restore from a backup file
+## Use SSMS to restore from a backup file
 
 In SSMS, take the steps in the following sections to restore the Wide World Importers database to SQL Managed Instance by using the **Restore** wizard. The database backup file is stored in a preconfigured Blob Storage account.
 
@@ -204,3 +200,5 @@ As an alternative to the **Restore** wizard, you can use T-SQL statements to res
 - [SQL Server Backup to URL best practices and troubleshooting](/sql/relational-databases/backup-restore/sql-server-backup-to-url-best-practices-and-troubleshooting)
 - [Connect your application to Azure SQL Managed Instance](connect-application-instance.md)
 - [Azure SQL Database and Azure SQL Managed Instance connect and query articles](../database/connect-query-content-reference-guide.md)
+- [Tutorial: Migrate SQL Server to an Azure SQL Managed Instance using Database Migration Service](/azure/dms/tutorial-sql-server-to-managed-instance).
+- [SQL Server to Azure SQL Managed Instance guide](../migration-guides/managed-instance/sql-server-to-managed-instance-guide.md).

docs/sql-server/azure-arc/delete-from-azure-arc.md

@@ -100,6 +100,8 @@ If your instance (*SQL Server - Azure Arc* resource) has dependent Azure resourc
 
 To disconnect all the Azure Arc-enabled SQL Server instances in a larger scope (such as a resource group, a subscription, or multiple subscriptions) with a single command, use the [script to uninstall Azure Extension for SQL Server](https://github.com/microsoft/sql-server-samples/tree/master/samples/manage/azure-arc-enabled-sql-server/uninstall-azure-extension-for-sql-server). The script is as an open-source SQL Server sample and includes step-by-step instructions.
 
+[!INCLUDE [resource-caching-after-deletion](includes/resource-caching-after-deletion.md)]
+
 ## Residual files and accounts
 
 After you uninstall Azure Extension for SQL Server, some files and database objects stay.

docs/sql-server/azure-arc/faq.yml

@@ -3,7 +3,8 @@ metadata:
   title: Frequently asked questions
   description: Provides questions and answers frequently asked about SQL Server enabled by Azure Arc.
   ms.topic: faq
-  ms.date: 02/25/2025
+  ms.date: 04/01/2026
+  ai-usage: ai-assisted
   ms.author: mikeray
   author: MikeRayMSFT
 title: Frequently asked questions - SQL Server enabled by Azure Arc
@@ -39,7 +40,7 @@ sections:
         answer: No. The usage data collection requires an active SQL Server instance. Therefore, you'll not be charged for the time the SQL Server instance was stopped.  
 
       - question: Do I get charged if my SQL Server instance was running for less than an hour?
-        answer: The billing granularity is one hour. If your instance was active for less than an hour, you are billed for the full hour. 
+        answer: The billing granularity is one hour. If your instance was active for less than an hour, you're billed for the full hour. 
 
       - question: Is there a minimum number of cores with pay-as-you-go billing?
         answer: Pay-as-you-go billing doesn't change the licensing terms of SQL Server. Therefore, it's subject to the four-core limit as defined in the [SQL Server licensing terms](https://www.microsoft.com/licensing/terms/productoffering/SQLServer/EAEAS). 
@@ -54,7 +55,7 @@ sections:
         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?
+      - question: How do I ensure that my VM and SQL server aren't billed when it's 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.
 
@@ -63,23 +64,35 @@ sections:
           - 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?
+      - question: How can I be notified about when a given machine doesn't 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).
+          - Subscribe to Activity Log events for when usage records aren't 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).
+
+      - question: Does pay-as-you-go billing work on Linux?
+        answer: |
+          Yes. PAYG billing is supported for SQL Server on Linux with limitations. Passive instance detection, connected user verification, and Database Engine-level core visibility aren't available on Linux. All SQL Server instances on Linux are billed as active. For details, see [Manage licensing and billing](manage-license-billing.md).
+
+      - question: Why are my passive SQL Server instances on Linux billed as active with pay-as-you-go?
+        answer: |
+          Passive instance detection isn't available on Linux. Without this capability, the free passive billing benefit can't be applied. All instances are billed based on the OS-reported core count. If you need free passive instance billing, consider using volume licensing instead of PAYG, or use [PAYG physical cores with unlimited virtualization](manage-license-billing.md#unlimited-virtualization).
+
+      - question: How does core detection work for PAYG on Linux?
+        answer: |
+          On Linux, core count is reported based on the operating system environment (virtual or physical cores visible to the OS). Database Engine-level core verification isn't available. Billing is based on the OS-reported core count, subject to the four-core minimum per OSE.
 
   - name: Security
     questions:
       - question: What are the best practices for security?
         answer: Review and implement [SQL Server enabled by Azure Arc best practices](security-overview.md#best-practices).
 
       - question: Is TDE with Azure Key Vault supported?
-        answer: No. TDE with Azure Key Vault is not supported today SQL Server enabled by Azure Arc. You can manually set up TDE for your own instances.
+        answer: No. TDE with Azure Key Vault isn't supported today SQL Server enabled by Azure Arc. You can manually set up TDE for your own instances.
 
       - question: Is there key vault support?
-        answer: Yes, there is key vault support today for SQL Server enabled by Azure Arc for storing the Microsoft Entra ID certificate.
+        answer: Yes, there's key vault support today for SQL Server enabled by Azure Arc for storing the Microsoft Entra ID certificate.
 
       - question: Does SQL Server enabled by Azure Arc support Private Link?
         answer: |
@@ -92,14 +105,14 @@ sections:
         answer: You need to open up the endpoint at `*.<region>.arcdataservices.com`. For specific information, review [Prerequisites - Connect to Azure Arc data processing service](prerequisites.md#connect-to-azure-arc-data-processing-service).
 
       - question: Does TLS inspection work with Azure Extension for SQL Server? 
-        answer: If your organization uses TLS inspection, the Azure Extension for SQL Server does not use certificate pinning and will continue to work, so long as your machine trusts the certificate presented by the TLS inspection service. For information on TLS inspection with Azure Arc-enabled server extension, see [Network Security](/azure/azure-arc/servers/security-networking#general-networking).
+        answer: If your organization uses TLS inspection, the Azure Extension for SQL Server doesn't use certificate pinning and will continue to work, so long as your machine trusts the certificate presented by the TLS inspection service. For information on TLS inspection with Azure Arc-enabled server extension, see [Network Security](/azure/azure-arc/servers/security-networking#general-networking).
 
 
       - question: What are the details on the permissions assigned?
         answer: Review [Configure Windows service accounts and permissions for Azure extension for SQL Server](configure-windows-accounts-agent.md).
 
       - question: What user is the Microsoft SQL Server extension service running as?
-        answer: When the least privileges mode is enabled, then it runs as the NT Service\SQLServerExtension account. When it is disabled, it runs as Local System. To enable least privilege mode, review [Least privilege mode](configure-least-privilege.md).
+        answer: When the least privileges mode is enabled, then it runs as the NT Service\SQLServerExtension account. When it's disabled, it runs as Local System. To enable least privilege mode, review [Least privilege mode](configure-least-privilege.md).
 
       - question: Is least privilege mode supported for SQL Server enabled by Azure Arc?
         answer: Yes, least privilege mode is supported for SQL Server enabled by Azure Arc. Existing servers with extension version `1.1.2859.223` or greater will eventually have the least privileged configuration applied. This extension was released in November, 2024. To prevent the automatic application of least privilege, block extension upgrades after `1.1.2859.223`. Learn more about the permission assigned at [Configure Windows service accounts and permissions for Azure extension for SQL Server](configure-windows-accounts-agent.md).
@@ -110,24 +123,24 @@ sections:
   - name: Associated services
     questions:
       - 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. 
+        answer: The associated services are represented as SQL Server instances in Azure Resource Manager (ARM) with a service_type property reflecting if it's 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 pay-as-you-go billing is enabled and required in the CSP-managed subscriptions. It is not available with other subscription offers.
+          No. At this point, recurring pay-as-you-go billing is enabled and required in the CSP-managed subscriptions. It's not available with other subscription offers.
 
-      - question: How do I ensure that my VM and SQL server are not billed when it is disconnected or turned off intentionally?
+      - question: How do I ensure that my VM and SQL server aren't billed when it's 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 plan to keep it offline for longer than 30 days, you should disconnect the Arc-enabled SQL Server. For steps, review [Disconnect SQL Server instances from Azure Arc](delete-from-azure-arc.md). Then reconnect using one of [the supported deployments options](deployment-options.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?
+      - question: How can I be notified about when a given machine doesn't 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.
+          - Subscribe to Activity Log events for when usage records aren't 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. 
 
   - name: VMware

docs/sql-server/azure-arc/includes/features-operating-system.md

@@ -2,7 +2,7 @@
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: randolphwest
-ms.date: 05/10/2023
+ms.date: 04/01/2026
 ms.topic: include
 ms.custom: ignite-2023
 ---
@@ -11,7 +11,7 @@ The following table identifies features available by operating system:
 | Feature | Windows | Linux |
 | --- | --- | --- |
 | [Discover and register SQL Server instances in Azure](../prerequisites.md) | Yes | Yes |
-| [Azure pay-as-you-go billing](../manage-configuration.md) | Yes | Yes |
+| [Azure pay-as-you-go billing](../manage-configuration.md) | Yes | Yes <sup>2</sup> |
 | [Install Azure extension for SQL Server during setup](../../../database-engine/install-windows/install-sql-server-from-the-installation-wizard-setup.md#install-sql-server-2022) <sup>1</sup> | Yes | No |
 | [Best practices assessment](../assess.md) | Yes | No |
 | [Migration assessment](../migration-assessment.md) | Yes | No |
@@ -31,3 +31,5 @@ The following table identifies features available by operating system:
 | [Operate with least privilege](../configure-least-privilege.md)| Yes | No |
 
 <sup>1</sup> [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] only.
+
+<sup>2</sup> PAYG billing is supported on Linux with limitations. Passive instance detection, connected user verification, and Database Engine-level core visibility aren't available. All instances are billed as active. For details, see [Manage licensing and billing](../manage-license-billing.md).

docs/sql-server/azure-arc/includes/resource-caching-after-deletion.md

@@ -0,0 +1,10 @@
+---
+author: MikeRayMSFT
+ms.author: mikeray
+ms.date: 04/01/2026
+ms.service: azure-arc
+ms.topic: include
+---
+
+> [!NOTE]
+> After you [delete](../delete-from-azure-arc.md) a *SQL Server - Azure Arc* resource, the resource might continue to appear in the Azure portal for a period of time. This behavior is expected and is caused by Azure Resource Manager caching. The resource typically disappears after the cache refreshes. If the resource still appears after several hours, you can verify that it was successfully deleted by querying Azure Resource Graph or by using the Azure CLI. No further action is required — the resource isn't functional and doesn't incur charges after deletion.

docs/sql-server/azure-arc/manage-configuration.md

@@ -4,7 +4,8 @@ description: Learn how to manage configuration options for SQL Server enabled by
 author: anosov1960
 ms.author: sashan
 ms.reviewer: mikeray, randolphwest
-ms.date: 07/03/2025
+ms.date: 04/01/2026
+ai-usage: ai-assisted
 ms.topic: how-to
 ms.custom: sfi-image-nochange
 ---
@@ -87,6 +88,9 @@ There are two ways to configure the SQL Server host in the Azure portal:
 
 Choose one of the license types. For descriptions, see [License types](manage-license-billing.md#license-types).
 
+> [!NOTE]
+> On Linux, certain configuration features aren't available, including passive instance detection and connected user verification. When you configure PAYG billing on Linux, all instances are billed as active regardless of their HA/DR role. For details, see [Manage licensing and billing](manage-license-billing.md).
+
 <a id="use-physical-core-license"></a>
 
 #### Use a physical core license