Skip to content

Releases: ykuijs/M365DSC_Data

v3.2

15 Jul 08:42
@ykuijs ykuijs
3.2
4ad5bf8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.2 Latest
Latest

Whitepaper release v3.2

Changes:

  • Fixed Test Compliancy pipeline
    • This pipeline was not updated correctly in the previous v3.x releases. This is now corrected.
    • Added possibility to change to a List view report. You can activate this by adding '-ReportView List' to the arguments in the 'Check configuration deviations' task in the 'testcompliancy-template.yaml' pipeline.
  • Generic code fixes/improvements:
    • Added code to remove all versions of the dependencies. The new Azure DevOps agents contained newer versions of the PowerShell modules, which was causing issues. The code now ensures only the correct versions are installed on the agent.
    • Added additional error handling for ModuleFast, so a proper error is displayed when Modulefast cannot download a module.
    • Updated the "Prepare Agent" step in the Deploy pipeline to use the normal PowerShell task instead of the Azure PowerShell task.
    • Remove the deployed configuration after deployment. This to make sure self-hosted agents will not run into issues when deploying a different configuration.
    • Fixed issue where creating log artifacts failed when using multiple environments due to naming conflict.
    • Updated code to support ObjectGraphTools v0.3.
    • Added test to ValidateSecrets to also test for the correct certificate thumbprint.
Assets 2
Loading

v3.1

15 Jul 08:37
@ykuijs ykuijs
3.1
a82d4bd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.1

Whitepaper release v3.1

Changes:

  • Improved troubleshooting information collection
    • Configured the PR Validation pipeline to also upload the merged data files to the pipeline, so it can be used for troubleshooting.
    • Configured the Deployment pipeline to save the "M365DSC", "Microsoft-Windows-DSC/Operational" and "MSCloudLoginAssistant" event logs and upload that to the pipeline, so it can be used for troubleshooting.
  • Changed prerequisite modules pre-staging to an Azure Blob Storage to using the ModuleFast module.
    • This removes the requirement for an Azure Blob Storage and improves the performance even more.
  • Optimized the CIM memory configuration
    • Some deployments ran into memory issues. These optimizations reduces the chance of experiencing these issues.
  • Added troubleshooting information to chapter 6 of the whitepaper.
    • Document some steps that can be used to troubleshoot the solution.
  • Implemented the default code page configuration to UTF8
    • In some cases data files contain Unicode characters, which result in issues during compliancy testing or deployment of configurations. This is resolved when the default code page in Windows is set to UTF8. The script now automatically changes this with each run.
  • [BREAKING CHANGE] Reverted resource naming in the Composite Resource Generator (CRG) from plural to singular.
    • To improve readability, the CRG converted the names of the Microsoft365DSC resources into plural variants if they allowed multiple objects to be inserted. For example: "ConditionalAccessPolicy" would become "ConditionalAccessPolicies" because you can configure multiple policies. As a result, the code in other places became much more complex, since the resource naming was not predictable and consistent. For example: In "IntunePolicySets" the word "Policy" should not be converted because "Sets" is the plural word here. That meant we had to implement exception on exception, etc.
    • So we decided to revert back to the original Microsoft365DSC resource naming in whatever form they are created. Important: This means you have to change the resource names in the data file structure as well, changing the resource names to their original form. This change goes into effect with the release of Microsoft365DSC v1.25.402.1 (the Breaking Change release of April 2025)!
  • Fixed issues in the whitepaper
    • Corrected hardcoded password into the required variable in the script mentioned in paragraph 4.1.3.
    • Updated steps in paragraph 4.7.4.1 to clarify that the creation of data files (paragraph 5.1.3 is required).
Loading

v3.0

03 Dec 18:41
@ykuijs ykuijs
3.0
b675757

Choose a tag to compare

View all tags
v3.0

Whitepaper release v3.0

Changes:

  • Separate Data and Scripts Azure DevOps projects
  • Multiple levels of data files: Basic (Generic) and Tenant specific
  • Mandatory settings check
  • Split data files into workloads
  • Quality Assurance tests
  • Microsoft Hosted Agent support
  • Tokenizing
  • Replacing Credentials with Certificate Thumbprint
  • Generated Composite Resources module that support all workloads
  • Generic functions are implemented via a public module called M365DSCTools, which is available in the PowerShell Gallery
  • Improved troubleshooting information

Download link: https://aka.ms/m365dscwhitepaper

Loading