Course Content

Building custom Bicep Local Deploy extensions From fundamentals to publishing your first custom-ready extension 4 Lessons

Introduction to Bicep Local Deploy extensions 20 min
Creating your first Bicep Local Deploy extension 45 min
Testing your Bicep Local Deploy extension 60 min
Documentation and publishing Bicep Local Deploy extension 35 min

Course content

This course takes you from Bicep Local Deploy fundamentals to publishing custom extensions that are production-ready. The getting started module starts with an introduction to the Bicep Local Deploy framework and its architecture. It covers how custom extensions work within Bicep's ecosystem. You'll set up your development environment and verify your installation using a quick-start project.

Next, you'll be building your first complete extension, expanding on the quick-start project. From looking at the project structure to defining type models with attributes, and lastly, implementing handlers that manage the resource lifecycle.

The advanced module lessons dive deeper into testing and documentation. You'll be using the bicep-local-docgen CLI tool to validate your documentation.

Prerequisites

Before starting this course, you should have:

C# programming: Be familiar with C# syntax, classes, and properties.
PowerShell basics: Understand PowerShell commands and scripting for running build scripts and tests.
REST APIs: Basic understanding of HTTP methods (GET, POST, PUT, DELETE) and JSON.
Command-line tools: Be comfortable running CLI utilities.

Don't worry if you're missing some recommended knowledge. The course provides explanations along the way. The required knowledge is mainly for following the code examples and completing the exercises.

What you'll learn

Understand Bicep Local Deploy architecture: Learn what custom extensions are, how they extend Bicep's capabilities, and the role of Azure.Bicep.Local.Extension framework and documentation attributes.
Build complete custom extensions: Create type models with documentation attributes, implement resource handlers, and test with Bicep files and Pester.
Generate and publish documentation: Use bicep-local-docgen CLI to generate markdown documentation and validation.

By the end of this course, you'll have a production-ready Bicep Local Deploy extension, including:

Documentation
End-to-end tests
Publishing workflow

You'll understand the complete lifecycle from initial concept to a published extension that users can consume in their Bicep templates.

Plan your migration Inventory your PowerShell DSC estate and choose a path for every artifact 7 Lessons

Introduction to migrating from PowerShell DSC 4 min
Why migrate, and when not to 8 min
Inventory what you have 12 min
Build and inventory the Bindery estate 20 min
Choose a migration path 10 min
Knowledge check 5 min
Summary 3 min

Migrate configurations and resources Walk all four migration paths against one legacy estate 10 Lessons

Introduction to migrating configurations and resources 3 min
Path A: Adapt in place 12 min
Adapt the legacy configuration 15 min
Path B: Import your compiled MOFs 12 min
Convert a MOF file 15 min
Path C: From script-based to class-based 15 min
Rewrite AppEnvironment as a class 20 min
Path D: Going native 8 min
Knowledge check 5 min
Summary 3 min

Replace the LCM Own the enforcement schedule, handle reboots, and migrate credentials 9 Lessons

Introduction to replacing the LCM 3 min
Map LCM features to Microsoft DSC 12 min
Own the enforcement schedule 10 min
Reboots and cross-node coordination 10 min
Migrate credentials 10 min
Prove equivalence end to end 20 min
Pitfalls from the field 8 min
Knowledge check 5 min
Summary and next steps 5 min

Course content

This course takes you from a working PowerShell DSC estate to a Microsoft DSC estate, without a rewrite weekend and without breaking production. The planning module starts where every real migration starts: with an honest look at what you already own. You'll learn why the trajectory points to Microsoft DSC, build an inventory that classifies every resource on a machine, and use that inventory to assign each artifact to one of four migration paths.

Next, you'll walk all four paths against the same small legacy estate. You'll adapt a Configuration script into a configuration document with the resource code untouched, rescue a compiled MOF file whose source script is long gone, rewrite a script-based resource as a class-based one that runs on PowerShell 7, and learn the signals that justify a full native rewrite.

The final module deals with the part of PowerShell DSC that isn't a file: the Local Configuration Manager. You'll map every LCM behavior your estate might depend on to its Microsoft DSC equivalent, replace scheduled enforcement with something you own, move credentials out of MOF files, and run an end-to-end equivalence check that proves all three migration routes converge on the same machine state.

Prerequisites

Before starting this course, you should have:

PowerShell DSC experience: You've written Configuration blocks, compiled MOF files, and run Start-DscConfiguration at least a few times.
Microsoft DSC fundamentals: You can read a configuration document, and you've run dsc config get, dsc config test, and dsc config set against one.
PowerShell scripting: Functions, modules, module manifests, and enough class syntax to read a [DscResource()] class.
A Windows machine: With both Windows PowerShell 5.1 and PowerShell 7+ installed, plus the dsc CLI on your path. Administrator rights are needed for the machine-level environment variable used in the exercises.

Don't worry if you're rusty on the Microsoft DSC side. Each unit explains the construct before using it, and every command in the exercises is shown in full. The PowerShell DSC knowledge is the part that's hard to substitute, because this course is about translating something you already own.

[!TIP]
If you've never applied a configuration document with Microsoft DSC, work through the getting-started chapters of The Microsoft DSC Handbook or The Fundamentals of Microsoft DSC first. This course assumes the mechanics and focuses entirely on the translation.

What you'll learn

Inventory a PowerShell DSC estate: Classify configurations, compiled MOFs, script-based resources, and class-based resources, and check what each Microsoft DSC adapter can already see.
Choose a migration path per artifact: Apply a four-path decision framework — adapt in place, import MOFs, rewrite as class-based, rewrite as native — and defend the choice with cost and payoff, not preference.
Execute each path hands-on: Translate Configuration scripts into configuration documents, convert MOF files with an import extension, and port Get/Set/Test-TargetResource trios into class-based resources.
Replace the LCM: Map enforcement modes, refresh intervals, reboot policy, partial configurations, and cross-node coordination to explicit Microsoft DSC replacements that you schedule and own.
Migrate credentials safely: Retire PSDscAllowPlainTextPassword and MOF encryption certificates in favor of secureString parameters and secret extensions.

By the end of this course, you'll have migrated a complete (if small) estate end to end, including:

A migration inventory report you can run against any machine
A configuration document that replaces a Configuration script
A class-based resource ported from a script-based one
A scheduled enforcement replacement for the LCM
An equivalence check that proves the migration didn't change behavior

You'll understand the full lifecycle from "we have hundreds of MOFs and nobody remembers who wrote them" to a reviewed, tested, version-controlled Microsoft DSC estate.

The running example

Every unit uses the same fictional estate, owned by a company called Bindery. A bindery is a workshop where loose sheets are fastened together into books, which is a fair description of what a migration does: fasten an old estate to a new engine without tearing any pages.

Bindery's operations team owns:

BinderyOps, a PowerShell module containing a script-based resource named AppEnvironment that manages a machine-level environment variable.
LegacyWebServer.ps1, a Configuration script that uses AppEnvironment alongside the built-in File resource.
output\localhost.mof, the compiled artifact that the LCM actually applies.

It's small enough to follow in a single sitting and structurally identical to the thousand-line resources in your production estate.

Getting started Learn the fundamentals and set up your development environment 4 Lessons

Introduction to Microsoft Desired State Configuration (DSC) 5 min
Installing Microsoft Desired State Configuration (DSC) 10 min
Your first resource invocation 10 min
Practicing and exploring 20 min

Course content

This course takes you from the Microsoft DSC fundamentals to practical implementation. The getting started module introduces Microsoft's Desired State Configuration (DSC) cross-platform command-line tool for declarative configuration management. You'll learn the core concepts that differentiate DSC from traditional configuration management approaches, install Microsoft DSC on your system, and get hands-on experience by invoking your first DSC resource. At the end, there's room for practical exercises and a knowledge check.

What you'll learn

Understand Microsoft's DSC architecture: Learn what Desired State Configuration is, how it's different from imperative tools, and why idempotency matters.
Install and configure Microsoft DSC: Set up Microsoft DSC on Windows, Linux, or macOS, including PATH configuration and installation.
Work with DSC resources: Discover how to explore resource schemas, understand property requirements, and invoke the core resource operations (get, set, test, and delete).
Configure your registry: Gain practical experience with the Microsoft.Windows/Registry DSC resource.

-/-

Why migrate, and when not to

Before touching a single file, it's worth being honest about the motivation. PowerShell DSC still works. Windows PowerShell 5.1 ships with Windows, the LCM still enforces configurations, and Start-DscConfiguration still does what it always did. Nobody is going to reach into your servers and delete it.

A migration you can't justify is a migration that stalls halfway, which is the worst possible place to stop. So start with the trajectory.

The case for migrating

Windows PowerShell 5.1 is in maintenance mode

Windows PowerShell 5.1 receives security fixes, not features. The PSDesiredStateConfiguration module that ships with it, version 1.1, is frozen in time. The resources in it today are the resources it will have forever.

Microsoft may drop the Windows PowerShell 5.1 adapter in a future release, which would complete the move away from script-based resources. Microsoft hasn't announced this, so don't base a migration schedule on it. The direction is clear, though, and it should decide whether you treat "adapt in place" as a waypoint or a destination.

The LCM is not coming to PowerShell 7

The DSC platform in PowerShell 7 (the PSDesiredStateConfiguration v2 module) dropped the LCM, and Microsoft DSC kept that decision. This is the biggest architectural change in the migration, and Module 3 of this course covers it.

If your estate genuinely depends on LCM-style behavior (pull mode, scheduled enforcement, central reporting), the project positioned to take over that role today is OpenDSC, acting as the enforcement and orchestration layer above the new engine.

[!IMPORTANT]
OpenDSC is community-driven open source. It's not officially supported by Microsoft. If your organization requires vendor support for the enforcement layer, factor that into the plan before you decommission a pull server.

New investment happens in Microsoft DSC

New resources, the extension model, what-if support, and the MCP server that lets AI agents drive configuration: all of it lands in the new engine. Every quarter you stay on PowerShell DSC is a quarter of new capability you can't reach.

Cross-platform is table stakes

If any part of your estate runs Linux or macOS, PowerShell DSC was always an awkward fit — you needed the Linux OMI-based agent, a different resource ecosystem, and a different mental model. Microsoft DSC treats those platforms as first-class citizens running the same engine and the same documents.

State is no longer hidden

There's a subtler reason that doesn't fit on a slide. PowerShell DSC's architecture hid state inside the LCM: pending MOFs, current MOFs, backup MOFs, all in C:\Windows\System32\Configuration. Troubleshooting meant spelunking through that hidden state and hoping Get-DscConfigurationStatus told you the truth.

Microsoft DSC is stateless. A document goes in, a result comes out. That's easier to reason about, easier to log, and dramatically easier to automate around, as you'll see when you build the equivalence check in Module 3.

Figure 1: Where the state lives

The case for waiting

An honest planning unit names the reasons to hold off, too:

Situation	Why waiting is reasonable
Your estate is entirely Windows, entirely stable, and rarely changes	The payoff of a migration is proportional to how often you touch the thing. A frozen estate earns little.
You depend on pull mode with vendor support	Microsoft DSC has no in-box pull server. Until your organization accepts a community-supported layer or an orchestrator you build, part of the story is missing.
Your team has no PowerShell 7 footprint at all	Path C and Path D both assume PowerShell 7+ is deployable. If it isn't, you're limited to Path A and B, which is fine — but plan for that ceiling deliberately.
A compliance audit is in flight	Changing the enforcement engine mid-audit invites questions you don't want to answer twice. Migrate after.

[!TIP]
Migration isn't all-or-nothing. The adapters exist precisely so that you can move the orchestration layer first and leave the resources alone. Many organizations run in this hybrid state for years, and that's a valid end state, not a failure.

Frame the decision for your stakeholders

When leadership asks "why now?", "because 5.1 is in maintenance mode" won't convince them. Translate the technical trajectory into operational terms:

Risk: Every script-based resource depends on a runtime that gets security fixes and nothing else.
Reach: Today a separate toolchain manages your Linux and macOS workloads. One engine replaces both.
Speed: Drift detection that returns structured results becomes a pipeline gate. Drift detection that returns a MOF status object becomes a support ticket.
Cost of delay: The inventory you're about to build grows every quarter you put it off.

> EOF