Skip to content

Latest commit

 

History

History
146 lines (93 loc) · 5.79 KB

prerequisites.md

File metadata and controls

146 lines (93 loc) · 5.79 KB
title description author ms.author ms.reviewer ms.date ms.topic ms.custom
Prerequisites
Describes prerequisites required for SQL Server enabled by Azure Arc.
anosov1960
sashan
mikeray, randolphwest
01/24/2024
conceptual
references_regions

Prerequisites - SQL Server enabled by Azure Arc

[!INCLUDE sqlserver]

An Azure Arc-enabled instance of [!INCLUDE ssnoversion-md] is an instance on-premises or in a cloud provider that is connected to Azure Arc. This article explains those prerequisites.

If your SQL Server VMs are on VMware clusters, review Support on VMware.

Before you deploy

Before you can Arc-enable an instance of [!INCLUDE ssnoversion-md], you need to:

Installation account permissions

The user or service principal requires:

  • Read permission on the subscription
  • Local administrator permission on the operating system to install and configure the agent
    • For Linux, use the root account
    • For Windows, use an account that is a member of the Local Administrators group

Before enabling SQL Servers with Arc, the installation script checks:

  • The region where the Arc-enabled SQL Server is supported
  • Microsoft.AzureArcData resource provider is registered

These checks require read permission on the subscription for the user.

The user or service principal requires the following permissions in the Azure resource group to complete the task. Specifically:

  • Azure Connected Machine Onboarding role
  • Microsoft.AzureArcData/register/action
  • Microsoft.HybridCompute/machines/extensions/read
  • Microsoft.HybridCompute/machines/extensions/write
  • Microsoft.Resources/deployments/validate/action

Users can be assigned to built-in roles that have these permissions, for example:

For more information, see Assign Azure roles using the Azure portal.

Service account permissions

The SQL Server service account must be a member of the sysadmin fixed server role on each SQL Server instance.

Set proxy exclusions

Note

The exclusion in this section is required for the March, 2024 release and before.

Beginning with the release in April, 2024 this exclusion is not required.

If a proxy server is used, set the NO_PROXY environment variable to exclude proxy traffic for:

  • localhost
  • 127.0.0.1

Connect to Azure Arc data processing service

[!INCLUDE data-processing-service-permission]

Note

You can't use Azure Private Link connections to the Azure Arc data processing service. See Unsupported configurations.

Supported SQL Server versions and environments

[!INCLUDE supported-configurations]

Unsupported configurations

[!INCLUDE unsupported-configurations]

Register resource providers

To register the resource providers, use one of the following methods:

Azure portal

  1. Select Subscriptions.
  2. Choose your subscription.
  3. Under Settings, select Resource providers.
  4. Search for Microsoft.AzureArcData and Microsoft.HybridCompute and select Register.

PowerShell

Run:

Register-AzResourceProvider -ProviderNamespace Microsoft.HybridCompute
Register-AzResourceProvider -ProviderNamespace Microsoft.AzureArcData

Azure CLI

Run:

az provider register --namespace 'Microsoft.HybridCompute'
az provider register --namespace 'Microsoft.AzureArcData'

Azure subscription and service limits

Before configuring your [!INCLUDE ssnoversion-md] instances and machines with Azure Arc, review the Azure Resource Manager subscription limits and resource group limits to plan for the number of machines to be connected.

Supported regions

[!INCLUDE azure-arc-data-regions]

Install Azure extension for SQL Server

The [!INCLUDE sssql22-md] Setup Installation Wizard doesn't support installation of the Azure extension for SQL Server. There are two ways to install this component. Do one of the following:

For VMware clusters, review Support on VMware.

Related content