You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the subtitle "Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Automanage's machine configuration feature." but few months ago the solution change the name from Azure Automanage's machine configuration to Azure Machine Configuration, currently there is another solution call Azure Automanage that is in deprecatoin path and that can be easily confuse by showing the name Automanage when is been refer to Azure Machine Configuration
Suggestion changes the line from:
"Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Automanage's machine configuration feature."
To
"Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Machine Configuration feature."
Type of issue
Outdated article
Feedback
Under the subtitle "Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Automanage's machine configuration feature." but few months ago the solution change the name from Azure Automanage's machine configuration to Azure Machine Configuration, currently there is another solution call Azure Automanage that is in deprecatoin path and that can be easily confuse by showing the name Automanage when is been refer to Azure Machine Configuration
Suggestion changes the line from:
"Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Automanage's machine configuration feature."
To
"Use Case for DSC 2.0" it explains this "DSC 2.0 is supported for use with Azure Machine Configuration feature."
Page URL
https://learn.microsoft.com/en-us/powershell/dsc/overview?view=dsc-2.0
Content source URL
https://github.com/MicrosoftDocs/PowerShell-Docs-DSC/blob/main/dsc/docs-conceptual/dsc-2.0/overview.md
Author
@sdwheeler
Document Id
7befffa4-ef78-f531-1a36-ecce7355978c
The text was updated successfully, but these errors were encountered: