Open ykuijs opened 3 weeks ago
I would be more inclined to the 3rd option because the issue could affect more than a single resource so implementing the fix in DSC Parser will ensure the problem doesn't reoccur on any resource and would also work for any location/regional settings
Apologies for bombing this thread, but obviously someone is able to use this resource properly. 😉
Can I ask y'all to take a quick glance at https://github.com/microsoft/Microsoft365DSC/issues/4809 please? We REALLY need some help. thanks!
Description of the issue
When exporting the SCSensitivityLabel resource, the Comment (and a few others) property sometimes contains Unicode characters: For example "-" (Unicode 0x2013) or '”' (Unicode 0x201c/0x201d). This can cause issues with the DSC Parser.
Note: The Comment and Tooltip field in the below example contain the incorrect dash.
I am now looking at a possible solution to add a function to test for Unicode characters and convert these to known ASCII characters. Currently I am wondering where to implement this function:
@NikCharlebois, @andikrueger, @ricmestre, @William-Francillette What is your opinion?
Microsoft 365 DSC Version
Dev
Which workloads are affected
Security & Compliance Center
The DSC configuration
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response