Skip to content
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

Update overview.md #126066

Closed
wants to merge 1 commit into from
Closed

Update overview.md #126066

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
2 changes: 2 additions & 0 deletions ...cles/governance/machine-configuration/how-to/develop-custom-package/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ ms.topic: how-to
---
# How to develop a custom machine configuration package

Can we add a note in here about creating a custom policy based on a policy that already exists? This is a very common scenario and we get tons of CRIs from customers who have tried to do this and done it incorrectly. They often think they can directly copy an existing assignment and paste it into a new one, but the data that appears in the portal for an existing assignment is not the same as what needs to be included in a new assignment. I think putting a note about this in this doc as well as a link to instructions on how to succesfully duplicate an assignment correctly (and test it) would really help.

Before you begin, it's a good idea to read the overview page for [machine configuration][01].

Machine configuration uses [Desired State Configuration][02] (DSC) when auditing and configuring
Expand Down