Describe the bug
Configuration names must begin with a letter in order to be imported into an Automation Account. If VM names begin with a number (example: "2019-WindowsServer"). The Export-AzDscConfiguration function currently names configuration scripts based on the VM name
To Reproduce
Steps to reproduce the behavior:
Run New-AzSystemData against a resource group with VMs with names that begin in a number.
Run Export-AzDscConfigurations and see that the configuration scripts will be named the same as the VM Name
Running Import-AzDscConfigurations will fail because the configuration name does not begin in a letter.
Expected behavior
AzDscConfiguration scripts are imported into the Azure Automation Account successfully.
Screenshots
Additional context
Export-AzDscConfigurations should name the config to begin with "STIG_" to remediate the issue.
Describe the bug Configuration names must begin with a letter in order to be imported into an Automation Account. If VM names begin with a number (example: "2019-WindowsServer"). The Export-AzDscConfiguration function currently names configuration scripts based on the VM name
To Reproduce Steps to reproduce the behavior:
Expected behavior AzDscConfiguration scripts are imported into the Azure Automation Account successfully.
Screenshots
Additional context Export-AzDscConfigurations should name the config to begin with "STIG_" to remediate the issue.