Architecture and roadmap

Azure Data Lab Toolkit

Define a data lab once, review its security and cost implications, deploy it consistently, prove that it works, and remove it cleanly.

Early architecture scaffold. No deployable cmdlets exist yet. SQL Server on Azure VM is the first implementation target.

Explore the architecture Open pitch deck Read the documentation

YAML and templates flow through the toolkit core, providers, and deployment engines to data targets and evidence outputs — Core contracts coordinate distinct extension types without turning storage, Git, data, or software into deployment targets.

A lab lifecycle, not a provisioning shortcut

The architecture treats assessment, licensing, identity, data provenance, validation, cost, and teardown as part of the same reviewable system.

First target

SQL Server on Azure VM

The reference provider will exercise networking, Key Vault, Bastion, guest setup, storage, restore, software, probes, and cleanup.

Architecture

Contracts before engines

Core, target providers, capability modules, catalogs, solution packs, probes, and engines meet through a normalized plan and versioned evidence.

Community

Governed catalogs

Sample data and tools retain visible ownership, licensing, provenance, versions, checksums, compatibility, and sensitivity metadata.

Follow the decisions as they become real

The roadmap starts with a complete SQL VM lifecycle, then extends the tested core to Azure SQL, managed and self-hosted PostgreSQL, Bicep, Terraform, general Git and CI/CD integrations, Microsoft Fabric, and later Kubernetes.

Read architecture View roadmap Suggest a project