Version: v1.2025.12
Last updated: 2025-12-16
Extend Azure management to SQL Server instances running anywhere—on-premises, edge, or other clouds.
| Task | Link |
|---|---|
| Onboard a server to Azure Arc | Hands-on lab Module 2 |
| Change license type (PAYG ↔ Paid) | License management |
| Enable Best Practices Assessment | BPA setup |
| Troubleshoot connectivity | Connectivity guide |
Use the links below to find the right documentation for your task.
Prerequisites – What you need before onboarding
Module 2: Arc onboarding – Connect on-premises servers to Azure Arc
Module 3: SQL extension – Deploy the Azure extension for SQL Server
License management – Manage license types and billing
BPA guide – Run and review SQL best practices
Monitoring – Enable advanced monitoring and feature flags
Extension status report – Generate reports
Full lab – End-to-end guided lab (~2 hours)
Connectivity – Diagnose and fix connectivity issues
Azure Arc extends Azure management capabilities to SQL Server instances running anywhere. Explore the value proposition →
Key benefits:
- Unified management – Single control plane for your entire SQL Server estate
- Flexible licensing – Pay-as-you-go billing and license mobility options
- Enhanced security – Microsoft Defender, Microsoft Entra ID authentication, unified governance
- Modernization path – Migration assessment and ESU coverage for end-of-support versions
Before you begin, ensure you have:
- Azure subscription – Create a free account
- SQL Server 2012 or later – 64-bit only
- Supported OS – Windows Server 2012+ or Windows 10/11; Linux (Ubuntu 20.04, RHEL 8, SLES 15)
- .NET Framework 4.7.2+ – Windows only (extension 1.1.2504.99+)
- PowerShell 7.0+ – For automation scripts
- Network – Outbound HTTPS (TCP 443) to
*.<region>.arcdataservices.com - Azure RBAC – Azure Connected Machine Onboarding role (minimum)
For full details, see Prerequisites on Microsoft Learn.
The following are not supported:
- SQL Server running in containers
- SQL Server 2008 / 2008 R2 or older
- SQL Server in Azure VMs (use native Azure management)
- Instance names containing
# - Multiple instances with the same name on the same host
For the complete list, see Unsupported configurations.
| Folder | Description |
|---|---|
| arc-sql-best-practice-assessment | SQL Best Practices Assessment |
| arc-sql-connectivity | Network connectivity validation tools |
| arc-sql-data-collection | Data collection categories and privacy info |
| arc-sql-faq | Frequently asked questions |
| arc-sql-hands-on-lab | End-to-end hands-on lab with Bicep templates |
| arc-sql-modify-license-type | Modify license type, P-Core, and ESU settings |
| arc-sql-monitoring | Configure monitoring and feature flags |
| arc-sql-presentation-files | Slide decks and presentation materials |
| arc-sql-report-reclass-extension-status | Extension status reports |
| arc-sql-value-proposition | Business case and security benefits |
| arc-sql-videos | Instructional videos |
- Best practices assessment
- Migration assessment
- Monitoring (preview)
- Microsoft Entra authentication
- Extended Security Updates
- Follow the principle of least privilege when assigning permissions
- Use Managed Identity for authentication when possible
- Keep Azure Arc agents updated to the latest versions
- Review security recommendations in Microsoft Defender for Cloud
- Never commit credentials or secrets – See TEMPLATE-FILES.md
This project welcomes contributions and suggestions. Please follow the standard GitHub pull request process.
© Microsoft Corporation. Licensed under the Apache License, Version 2.0.