Hands-on Lab — DP-600 Microsoft Fabric Analytics Engineer Associate

Overview

Prerequisites

Steps

1. 1.Provider, Resource Group, naming primitives

   Standard Azure opener. Fabric capacities are region-bound — pick a region your data sources are in to avoid cross-region transfer charges (Fabric reads from OneLake, which physically lives in the capacity's region).

   Copy

   terraform {
     required_version = ">= 1.5"
   
     required_providers {
       azurerm = { source = "hashicorp/azurerm", version = "~> 4.0" }
       random  = { source = "hashicorp/random",  version = "~> 3.6" }
     }
   }
   
   provider "azurerm" {
     features {}
   }
   
   resource "random_id" "suffix" {
     byte_length = 3
   }
   
   data "azurerm_client_config" "current" {}
   
   locals {
     tags = {
       Project   = "certlabpro-dp-600"
       ManagedBy = "terraform"
     }
   }
   
   resource "azurerm_resource_group" "main" {
     name     = "certlabpro-dp-600-rg"
     location = "eastus"
     tags     = local.tags
   }

2. 2.Provision an ADLS Gen2 storage account for OneLake shortcut targets

   Provisions:

   • Azure Storage

   Microsoft Fabric's OneLake feature provides a unified data lake across Fabric workspaces. Fabric items (Lakehouses, Warehouses) physically store their data in OneLake — but Fabric also supports shortcuts that reference data in external storage (ADLS Gen2, S3, GCS, Dataverse) as if it lived in OneLake. The shortcut pattern is the DP-600 hot topic for Implement and manage a data analytics solution — federate without copying.

   We provision an ADLS Gen2 account here with hierarchical namespace enabled (the required setting for OneLake shortcuts). You'd create the actual shortcut inside the Fabric portal pointing at this account once it exists.

   Copy

   resource "azurerm_storage_account" "lake" {
     name                            = "dp600lake${random_id.suffix.hex}"
     resource_group_name             = azurerm_resource_group.main.name
     location                        = azurerm_resource_group.main.location
     account_tier                    = "Standard"
     account_replication_type        = "LRS"
     account_kind                    = "StorageV2"
     is_hns_enabled                  = true # required for OneLake shortcuts
   
     https_traffic_only_enabled      = true
     min_tls_version                 = "TLS1_2"
     allow_nested_items_to_be_public = false
   
     tags = local.tags
   }
   
   resource "azurerm_storage_container" "bronze" {
     name                  = "bronze"
     storage_account_id    = azurerm_storage_account.lake.id
     container_access_type = "private"
   }
   
   resource "azurerm_storage_container" "silver" {
     name                  = "silver"
     storage_account_id    = azurerm_storage_account.lake.id
     container_access_type = "private"
   }
   
   resource "azurerm_storage_container" "gold" {
     name                  = "gold"
     storage_account_id    = azurerm_storage_account.lake.id
     container_access_type = "private"
   }

3. 3.Stand up the Fabric capacity itself

   Provisions:

   • Microsoft Fabric

   The Fabric capacity is the billing unit for all Fabric workloads. Workspaces in the Fabric portal get associated with a capacity, and that's what determines pricing and quota.

   We provision the smallest production-grade capacity (F2). The administration_members list names who can administer the capacity in the Fabric admin portal — for the lab we use the current Terraform principal. The administrator role is separate from workspace-level permissions; capacity admins control billing, capacity-wide settings, and which workspaces can use it.

   DP-600 tests capacity sizing as a cost-optimization theme: choose the smallest SKU that meets your workload's RU/s needs, scale up for peak, scale down or pause off-hours. F-SKUs are pay-as-you-go (per-hour billing); the older P-SKUs from Power BI Premium are reserved-capacity (yearly commitment).

   Copy

   resource "azurerm_fabric_capacity" "main" {
     name                = "fab-dp600-${random_id.suffix.hex}"
     resource_group_name = azurerm_resource_group.main.name
     location            = azurerm_resource_group.main.location
   
     administration_members = [
       data.azurerm_client_config.current.object_id,
     ]
   
     sku {
       name = "F2" # smallest Fabric SKU; F-series is pay-as-you-go
       tier = "Fabric"
     }
   
     tags = local.tags
   }

4. 4.Wire capacity diagnostics to Log Analytics

   Provisions:

   • Azure Monitor

   DP-600's Maintain and optimize analytics solutions domain tests capacity health monitoring as the primary diagnostic surface — capacity throttling, query duration spikes, refresh failures all surface as Log Analytics signals. We provision the workspace and a Diagnostic Setting on the Fabric capacity that ships every metric and log category into it.

   With this final piece, the Fabric foundation is complete: capacity sized for the workload, ADLS Gen2 ready as a shortcut target, capacity diagnostics flowing to Log Analytics. Fabric workspaces, Lakehouses, Warehouses, semantic models, and notebooks are all created inside the capacity via the Fabric portal or REST API — that's the application layer this lab doesn't try to do in Terraform.

   Copy

   resource "azurerm_log_analytics_workspace" "main" {
     name                = "log-dp600"
     resource_group_name = azurerm_resource_group.main.name
     location            = azurerm_resource_group.main.location
     sku                 = "PerGB2018"
     retention_in_days   = 30
   
     tags = local.tags
   }
   
   resource "azurerm_monitor_diagnostic_setting" "fabric" {
     name                       = "diag"
     target_resource_id         = azurerm_fabric_capacity.main.id
     log_analytics_workspace_id = azurerm_log_analytics_workspace.main.id
   
     metric {
       category = "AllMetrics"
       enabled  = true
     }
   }

Cleanup