Tools And Solution Packs

Candidate catalog

These projects are being considered for future lab scenarios. None is bundled, installed, or otherwise integrated today. A listing records interest and gives upstream maintainers visible credit; it is not an endorsement and does not transfer ownership, support, or licensing to Azure Data Lab Toolkit.

Candidate and home	Maintainer or publisher	License or terms	Possible lab use
dbatools (code)	Created by Chrissy LeMaire; maintained by the dbatools core team and contributors	MIT	SQL Server administration, migration, and restore exercises
SQL Server First Responder Kit (code)	Brent Ozar, Brent Ozar Unlimited, and contributors	MIT	SQL Server health and performance exercises, including the sp_Blitz family
Tabular Editor	Created by Daniel Otykier	Tabular Editor 2 is MIT; Tabular Editor 3 is a commercial product	Semantic-model development
pbi-tools (code)	Created and maintained by Mathias Thierbach, with contributors	AGPL-3.0	Source control and automation for Power BI artifacts
Tabular Model Definition Language	Microsoft	TMDL is a Microsoft language and specification, not an installable open-source tool	Text-based semantic-model definitions and source-control exercises
Fabric Unified Admin Monitoring	A community accelerator in Microsoft Fabric Toolbox; Gellért Gintli, Kevin Thomas, and other contributors are associated with its development	Fabric Toolbox is MIT licensed; its assets are examples supported on a best-effort basis, not an officially supported Microsoft product	Fabric administration and monitoring
Rayfin	Microsoft and contributors	The repository is MIT licensed; any separate service terms and current service availability still require verification	Code-first Fabric backend demonstrations
Measure Killer	Gregor Brunner and Brunner BI	Commercial software with free and paid editions; exact terms must be reviewed before automation or redistribution	Semantic-model analysis, cleanup, and governance
SQL Server Maintenance Solution (code)	Ola Hallengren and contributors	MIT	Backup, integrity, index, and statistics maintenance
SQL Server Management Studio	Microsoft	Proprietary Microsoft software; the current Microsoft download and installer terms are definitive	Windows-based SQL Server administration

FUAM contributor wording is intentionally cautious: the canonical repository and its history are the authority for authorship. TMDL is listed because it can shape a lab scenario, not because it is a downloadable application.

Catalog contract

A catalog record will not make upstream software a toolkit dependency. It will describe how the toolkit may acquire, verify, run, validate, and remove an independently owned artifact.

Every record must include:

• the canonical project, code, and acquisition sources;
• upstream owner or maintainer, license or terms, required attribution, and redistribution limits;
• a pinned, immutable version or digest and an update policy;
• supported platforms, target providers, and compatibility constraints;
• checksum or signature details when upstream publishes them;
• authentication by secret reference, never a credential embedded in a URL;
• required execution identity, privileges, network access, and expected side effects;
• installation or invocation arguments, post-install verification, and removal behavior;
• data-sensitivity classification and report-redaction requirements.

The default policy is deliberately strict:

• A public catalog entry requires known license or usage terms before it can be accepted.
• An automated download requires an immutable version. When upstream publishes a checksum or signature, the catalog must verify it.
• A mutable URL such as a latest download is not a reproducible source. It may be used only through an explicit policy exception that records the resolved version and integrity evidence.
• A user-provided private URL may proceed only after explicit provenance acknowledgement. A checksum is optional for this user-controlled route, but an absent checksum must produce a warning and be recorded in the plan and run evidence.
• URLs must never contain embedded credentials. Private authentication must use Key Vault or another approved secret reference.
• Downloaded code is not trusted merely because it appears in the catalog. Its execution identity, privilege level, verification, and cleanup must be visible before approval.

Solution packs

A future solution pack may combine cataloged data, tools, configuration, probes, and learning outcomes into one reproducible scenario. It must reference catalog records rather than hide downloads or commands inside scripts.

Open-source maintainers and commercial or private project owners can start with Suggest A Project.