Skip to content

Commit b36d1b7

Browse files
authored
Update migrating-from-dsc-extension.md
1 parent 005fe1b commit b36d1b7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/governance/machine-configuration/whats-new/migrating-from-dsc-extension.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ Before you begin, it's a good idea to read the conceptual overview information a
2222

2323
## Major differences
2424

25-
Machine configuration uses DSC version `2`. DSC Extension uses
26-
DSC version `1`. The implementations are separate. However, there's no
25+
Machine configuration uses DSC version 2. DSC Extension uses
26+
DSC version 1. The implementations are separate. However, there's no
2727
conflict detection. Using both platforms to manage the same configuration isn't advised.
2828

2929
Configurations are deployed through the DSC extension in a "push" model, where the
@@ -41,8 +41,8 @@ The DSC extension included **privateSettings** where secrets could be passed to
4141
such as passwords or shared keys. Secrets management hasn't yet been implemented for machine
4242
configuration.
4343

44-
Machine configuration runs in PowerShell version `7.x`, while the DSC Extension runs in Windows
45-
PowerShell `5.1`. While most resources are expected to work because of [implicit remoting][02]
44+
Machine configuration runs in PowerShell version 7.2, while the DSC Extension runs in Windows
45+
PowerShell 5.1. While most resources are expected to work because of [implicit remoting][02]
4646
it is a good idea to test existing resources before use.
4747

4848
Because DSC Extension manages Local Configuration Manager service in Windows, control over whether

0 commit comments

Comments
 (0)