Study guide
2.2 Automated Deployment, Azure Arc, and SQL Database in Microsoft Fabric
DP-300: Administering Microsoft Azure SQL Solutions Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current DP-300 Exam Facts 1.2 Skills Outline and Domain Weights 1.3 Study Strategy and Official Resources
2 Planning and Deploying Azure SQL Solutions
2.1 Choosing and Deploying Azure SQL Database Offerings 2.2 Automated Deployment, Azure Arc, and SQL Database in Microsoft Fabric 2.3 Table Partitioning and Sharding Strategy 2.4 Hybrid SQL Server and IaaS Patching
3 Configuring Resources for Scale and Performance
3.1 Configuring Azure SQL Database for Scale and Performance 3.2 Configuring Azure SQL Managed Instance for Scale and Performance 3.3 Configuring SQL Server on Azure VMs for Scale and Performance 3.4 Configuring Table Partitioning and Data Compression
4 Planning and Implementing a Migration Strategy
4.1 Evaluating Migration Requirements and Strategies 4.2 Implementing Online, Offline, and Azure Migrations 4.3 Migrating Between Azure SQL Services and Troubleshooting
5 Configuring Database Authentication and Authorization
5.1 Microsoft Entra ID Authentication for Azure SQL 5.2 Authentication for SQL on Azure VMs and Managed Instance; Troubleshooting 5.3 Security Principals and Entra-Backed Users 5.4 Permissions, Least Privilege, and T-SQL Management
6 Implementing Security for Data at Rest and in Transit
6.1 Transparent Data Encryption and Object-Level Encryption 6.2 Always Encrypted and VBS Enclaves 6.3 Firewall Rules, Private Links, and Service Endpoints
7 Implementing Compliance Controls for Sensitive Data
7.1 Data Classification and Server/Database Auditing 7.2 Change Data Tracking and Dynamic Data Masking 7.3 Row-Level Security and Ledger in Azure SQL
8 Monitoring Resource Activity and Performance
8.1 Operational Baselines and Performance Metric Sources 8.2 Interpreting Metrics and Configuring Activity Monitoring 8.3 Monitoring with Database Watcher (Preview) 8.4 Monitoring with Extended Events
9 Monitoring and Optimizing Query Performance
9.1 Configuring and Monitoring with Query Store 9.2 Session Blocking and Dynamic Management Views 9.3 Index Changes and Execution Plan Review 9.4 Query Construct Modifications and Intelligent Insights
10 Configuring Database Solutions for Optimal Performance
10.1 Index, Statistics, and Integrity Maintenance 10.2 Automatic Tuning and Database-Scoped Configuration 10.3 Server Settings and Resource Governor 10.4 Compute/Storage Scaling and Intelligent Query Processing
11 Creating and Managing SQL Server Agent Jobs
11.1 Schedules for Regular Maintenance Jobs 11.2 Job Alerts, Notifications, and Agent Troubleshooting 11.3 Automating Deployment with ARM and Bicep Templates
12 Automating Deployments and Database Tasks in Azure
12.1 Azure PowerShell, Azure CLI, and Deployment Monitoring 12.2 Elastic Jobs for Cross-Database Automation 12.3 Azure Automation Runbooks, Alerts, and Troubleshooting Automated Tasks
13 Planning an HA/DR Strategy and Backup and Restore
13.1 Recommending HA/DR Strategy from RPO and RTO 13.2 Hybrid and Azure-Specific HA/DR Solutions and Testing 13.3 Backup and Restore Strategy with Native Tools 13.4 Point-in-Time Restore and Recovery Operations
14 Configuring HA/DR: Long-Term Retention, Geo-Replication, and Failover Groups
14.1 Long-Term Retention, T-SQL Backup/Restore, and Cloud Storage 14.2 Active Geo-Replication 14.3 Failover Groups
15 Advanced HA/DR: Availability Groups, FCIs, Log Shipping, and Troubleshooting
15.1 Always On Availability Groups on SQL Managed Instance and Azure VMs 15.2 Always On Failover Cluster Instances and Log Shipping 15.3 Monitoring and Troubleshooting HA/DR Solutions
2.2 Automated Deployment, Azure Arc, and SQL Database in Microsoft Fabric
Key Takeaways Explain This Topic AI
For repeatable, source-controlled, multi-environment deployments choose declarative templates (Bicep or ARM); the Azure portal suits one-off manual work, and Azure PowerShell or the Azure CLI suit scripted imperative automation in existing pipelines.
Bicep is a domain-specific language that transpiles to Azure Resource Manager (ARM) JSON, so it supports every Azure resource and requires no state file.
Azure Arc-enabled SQL Server projects on-premises and multi-cloud instances into Azure as resources for central inventory, Microsoft Entra authentication, Microsoft Defender, and pay-as-you-go billing — without moving any data.
Pay-as-you-go billing through Azure Arc lets you pay per core-hour for SQL Server instead of buying licenses, which suits dev/test, seasonal, or short-lived workloads.
SQL database in Microsoft Fabric is an autonomous SaaS database that mirrors data into OneLake in near real time; pick it when operational data must feed Fabric analytics, and pick Azure SQL Database when you need explicit control over tiers, pools, networking, and configuration.
Last updated: August 2026
Choosing an Automated Deployment Method
Quick Answer: For repeatable, auditable, multi-environment deployments choose Bicep or ARM templates because they are declarative and idempotent. Use the Azure portal for one-off manual deployments, Azure PowerShell or the Azure CLI for scripted imperative automation, and reserve deep pipeline design for the dedicated automation chapter.
Every Azure SQL resource — logical servers, databases, elastic pools, managed instances, firewall rules — can be deployed through the Azure Resource Manager (ARM) control plane. The deployment methods differ in how you express intent:
Azure portal — a guided wizard for single, manual deployments. It is the right answer for quick proof-of-concept work or learning, and it can export the equivalent template at the review step. It is never the right answer for repeatable production deployment.
ARM templates — declarative JSON describing the desired end state. Deployments are idempotent : applying the same template repeatedly converges to the same result rather than failing on existing resources. Templates live in source control, support parameters for per-environment values, and integrate with what-if to preview changes before applying them.
Bicep — a concise domain-specific language (DSL) that transpiles directly to ARM JSON. It offers modules for reuse, strong typing, and vastly less boilerplate than raw JSON, with no separate state file to manage because Azure itself is the source of truth. Anything ARM can deploy, Bicep can deploy.
Azure PowerShell — imperative cmdlets such as New-AzSqlServer and New-AzSqlDatabase . A natural fit when the team already automates in PowerShell or on Windows-centric pipelines.
Azure CLI — imperative commands such as az sql server create and az sql db create . Cross-platform and the common choice in Linux-based continuous integration and continuous delivery (CI/CD) pipelines.
REST API, SDKs, and third-party tools such as Terraform — used when you need programmatic control or multi-cloud tooling, though Terraform maintains its own state file, unlike Bicep and ARM.
The exam frames these as scenario picks: existing Bash-based CI/CD pipeline points to the Azure CLI; a requirement for repeatable, versioned infrastructure across dev, test, and prod points to Bicep or ARM; a single quick sandbox database points to the portal.
Azure Arc-Enabled SQL Server
Azure Arc extends the Azure control plane to resources running outside Azure — on-premises, at the edge, or in other clouds. For SQL Server, you install the Azure Connected Machine agent on the host and the Azure extension for SQL Server , which registers each instance as an Azure resource with a resource ID, tags, Azure role-based access control (RBAC), and policy scope. No data moves to Azure; only management metadata flows.
The use cases the exam emphasizes are:
Central inventory at scale — one Azure view of every SQL Server instance in the estate, with version, edition, and patch level, queryable through Azure Resource Graph.
Microsoft Entra authentication — SQL Server 2022 and later instances can accept Microsoft Entra ID (formerly Azure Active Directory) identities when Arc-connected, unifying identity management across cloud and on-premises.
Security and governance — Microsoft Defender for SQL, Azure Policy guest configuration, best practices assessment, and migration readiness assessments.
Pay-as-you-go billing — instead of purchasing licenses, you can pay for SQL Server per core-hour through Azure, activated via Arc. This is attractive for dev/test, seasonal workloads, or instances without Software Assurance, and it can be turned off when the workload ends.
Backup and management services — automated backup to Azure and Purview governance integration for supported configurations.
A frequent trap: Azure Arc manages and inventories SQL Server — it is not a replication or migration technology, and it does not convert the instance into azure SQL Managed Instance.
SQL Database in Microsoft Fabric
SQL database in Microsoft Fabric is a software-as-a-service (SaaS) database built on the Azure SQL Database engine but operated as a native Fabric workload. Its defining traits:
Autonomous by default — it provisions in seconds, auto-scales, and self-manages indexes and performance; there are no service tiers, elastic pools, or DTU/vCore decisions to make.
Capacity-based billing — consumption is measured in Fabric capacity units (CUs) against your Fabric capacity rather than per-database charges.
Automatic OneLake mirroring — data replicates into OneLake as Delta tables in near real time, making operational data immediately available to Power BI DirectLake reports, Spark notebooks, and data engineering workloads without extract-transform-load (ETL) pipelines.
Choose Fabric SQL database when the workload lives in the analytics ecosystem: an operational store whose data must feed Fabric analytics with zero ETL, rapid prototyping, or teams that want a database with essentially no knobs. Choose Azure SQL Database instead when you need explicit control — specific service tiers, elastic pools, Hyperscale, granular networking such as private endpoints configured independently, advanced T-SQL surface area, or when the organization has no Fabric capacity investment. The exam contrast is autonomy and analytics integration (Fabric) versus configurability and standalone operation (Azure SQL Database).