Frequently asked questions - SQL Server enabled by Azure Arc

Yes, you can use the excludedInstances setting in the Azure Policy to indicate the SQL Server instances that you don't want to include in the onboarding process.

For example, if you have any standby instances, you might not want to view them in the portal. When you use Azure Policy to onboard, you can exclude such instances based using pattern matching of the instance names.

1. Create a copy of the definition that we provide in Azure to create a custom definition.
2. Set the value for excluded instances in the custom definition.
3. Target the subscription and resource group.

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.

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.

No. When the VM is stopped, the usage data isn't collected. Therefore, you'll not be charged for the time the VM was stopped.

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.

The billing granularity is one hour. If your instance was active for less than an hour, you are billed for the full hour.

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.

No. When you run your SQL Server instance on a virtual or physical machine, you're required to license the full set of cores that the machine can access. Therefore, your pay-as-you-go charges are based on the full core count even if you use the affinity mask to limit your SQL Server's usage of these cores. See SQL Server licensing guide for details.

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.

No. At this point, recurring billing is only enabled in the cloud solution provider (CSP) managed Azure subscriptions.

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.

• 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.

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.

Review and implement SQL Server enabled by Azure Arc best practices.

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.

Yes, there is key vault support today for SQL Server enabled by Azure Arc for storing the Microsoft Entra ID certificate.

Yes. SQL Server enabled by Azure Arc supports Private Link for most endpoints, but some endpoints don't require Private Link and some endpoints aren't supported. For specific information, see Connected Machine agent network requirements.

You can find details on the roles created by the Azure extension for SQL Server at Roles created by Azure extension for SQL Server installation.

You need to open up the endpoint at *.<region>.arcdataservices.com. For specific information, review Prerequisites - Connect to Azure Arc data processing service.

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.

Review Configure Windows service accounts and permissions for Azure extension for SQL Server.

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 (preview).

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.

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.

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 and Extended Security Updates for details.

No. At this point, recurring billing is only offered to cloud solution provider (CSP) managed customers.

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.

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 for details.

No. Recurring billing is a feature of pay-as-you-go subscriptions.

Related content

• SQL Server enabled by Azure Arc - Overview
• SQL Server enabled by Azure Arc deployment options
• Azure Arc-enabled data services FAQ