Open kochi-shunsuke opened 11 months ago
Could you try to compile your configuration manually to gather additional information about the issue?
Compiling the configuration manually did not show any errors. The command executed and the result are:
PS C:\test> .\M365DSC-Test-Config-SC-20240122.ps1 -Credential $Credential
Directory: C:\test\M365DSC-Test-Config-SC-20240122
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 1/22/2024 12:30 AM 516262 localhost.mof
However, the error in the build pipeline continue when running from AzureDevOps.
What should I do next?
This looks strange. Any chance to run Import-Module .... -Verbose on the psd1 file for the security compliance configuration?
OK, I tried it. And I attached the result as a file. result_import-module_verbose.txt
This looks like an encoding issue. Could you please get the file encoding of this file?
I get the encoding of the psd1 and psm1 files for the security compliance configuration. They are UTF-8.
Are there any other files that I should get the encoding?
@andikrueger Is there a recommended encoding? Also, are there any languages not available in M365 DSC?
The new version of the whitepaper has been published this morning! It took a little bit longer due to some other improvements and bugs we encountered during testing. My apologies for that!
You can find the announcement here and the new version of the whitepaper here.
Please try again with the new scripts and let us know the results. Many improvements have been made, including an encoding check.
Description of the issue
I built my environment according to the devops whitepaper I also rewritten SecurityCompliance.schema.psm1 with the tenant settings exported by M365DSC. This causes the following error in the build pipeline:
[error]The module 'SecurityCompliance' could not be loaded. For more information, run 'Import-Module SecurityCompliance'.
Commenting out some LocaleSettings prevents errors. How do I need to modify LocaleSettings?
Microsoft 365 DSC Version
V1.23.1101.1
Which workloads are affected
Security & Compliance Center
The DSC configuration
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response