Skip to content

docs: simplify MC packaging to two prerequisites and three steps #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Amir Bredy (ABMFST) merged 1 commit into from
Oct 28, 2026
Merged

docs: simplify MC packaging to two prerequisites and three steps #148

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,10 @@

### Documentation

- Make Machine Configuration setup self-contained: include the platform-specific
DSC prerequisites, verify module versions and commands, prepare the export
folder first, and restore variables explicitly in the elevated audit session.
Keep Azure tools and publishing optional, and reject missing files and
accidental package overwrites before continuing.
- Simplify Machine Configuration packaging to two module prerequisites and
three steps: export, resolve the resource-module version, and create an Audit
ZIP. Remove the separate DSC-module installation from the Windows
precompiled-MOF path; link testing and Azure deployment as optional follow-ups.

## [0.3.104] - 2026-10-28

Expand Down
7 changes: 4 additions & 3 deletions docs/src/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,10 @@ foundational work by theme.

## Unreleased

- **Copy-and-paste packaging setup:** Include the DSC prerequisite and readiness
checks, explicit export/package paths, and a self-contained elevated Audit
step that saves its results. Keep Azure publishing separate and optional.
- **Simpler packaging:** State the two module prerequisites and provide three
steps to create an Audit ZIP. No separate DSC-module installation is needed
for the Windows precompiled-MOF path. Testing and Azure deployment are linked
as optional follow-ups.

## v0.3.104 - 2026-10-28

Expand Down
6 changes: 3 additions & 3 deletions docs/src/quick-start/authoring-vs-deploying.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,11 +82,11 @@ To draft a Linux baseline on Windows or macOS:
## Azure Machine Configuration is a separate path

For Azure Policy evaluation, export **MOF** and follow
[Deploy through Azure Machine Configuration](../user-guide/machine-configuration.md).
[Create a Machine Configuration package](../user-guide/machine-configuration.md).
Package creation requires **PowerShell 7**, the **GuestConfiguration** toolkit,
and the **Microsoft.OSConfig PowerShell module 1.4.10 or later** on the
packaging machine. Version 1.4.10 refers to the module, not the runtime.

The guide binds the MOF to an exact installed module version, creates an
Audit-first ZIP, tests it, and then covers hosting and policy assignment.
The guide binds the MOF to an exact installed module version and creates an
Audit-first ZIP. Testing, hosting, and policy assignment are optional follow-ups.
None of those steps is required for authoring or Audit Pack export.
Loading
Loading