v0.3.0-preview0001

[v0.3.0-preview0001]

Added

• Function Test-M365DSCPowershellDataFile added as replacement for Test-M365PowershellDataFile

v0.2.12

[v0.2.12]

Fixed

• Fixed issue in Convert-M365DSCExportToPowerShellDataFile where the created data file
  was in ASCII format, causing special characters to be displayed incorrectly.

v0.2.12-preview0001

[v0.2.12-preview0001]

Fixed

• Fixed issue in Convert-M365DSCExportToPowerShellDataFile where the created data file
  was in ASCII format, causing special characters to be displayed incorrectly.

v0.2.11

[v0.2.11]

Changed

• Updated Test-M365MandatoryPowershellDataFile to filter key parameters for testing.
  This is to make sure you can specify some properties of an object without tests
  failing because the key parameter exists
• Updated Test-M365PowershellDataFile to make sure warning are suppressed from Get-ChildNode
• Updated Set-ADOEnvironment to skip configuring checks on environments that are not
  specified in the TargetEnvironments parameter

v0.2.11-preview0002

[v0.2.11-preview0002]

Changed

• Updated Test-M365MandatoryPowershellDataFile to filter key parameters for testing.
  This is to make sure you can specify some properties of an object without tests
  failing because the key parameter exists
• Updated Test-M365PowershellDataFile to make sure warning are suppressed from Get-ChildNode
• Updated Set-ADOEnvironment to skip configuring checks on environments that are not
  specified in the TargetEnvironments parameter

v0.2.11-preview0001

[v0.2.11-preview0001]

Changed

• Updated Test-M365MandatoryPowershellDataFile to filter key parameters for testing.
  This is to make sure you can specify some properties of an object without tests
  failing because the key parameter exists

v0.2.10

[v0.2.10]

Fixed

• Fixed several issues in Test-M365MandatoryPowershellDataFile, which caused the NotAllowedMandatory
  parameter not to work

v0.2.10-preview0001

[v0.2.10-preview0001]

Fixed

• Fixed several issues in Test-M365MandatoryPowershellDataFile, which caused the NotAllowedMandatory
  parameter not to work

v0.2.9

[v0.2.9]

Added

• New Test-IfModulesInBlobStorage that tests if a package exists in the Azure Blob
  Storage for the specified Microsoft365DSC version
• New Test-M365MandatoryPowershellDataFile function to test a data object for
  mandatory values

Changed

• Updated the Test-M365PowerShellDataFile function to allow specifying to disable checking
  for Required parameters. This is specifically useful for individual, not yet merged, data
  files. There required parameters could not exist, because they are coming from a different file.
• Optimized unit tests for Test-M365PowershellDataFile

Fixed

• Fixed issue in Convert-M365DSCExportToPowerShellDataFile where parameter in ConvertTo-Expression
  has been removed
• Corrected pipeline yaml output where the file was encoded as UTF8 instead of UTF8 with BOM. Now
  code always outputs UTF8 with BOM

v0.2.9-preview0004

[v0.2.9-preview0004]

Added

• New Test-IfModulesInBlobStorage that tests if a package exists in the Azure Blob
  Storage for the specified Microsoft365DSC version
• New Test-M365MandatoryPowershellDataFile function to test a data object for
  mandatory values

Changed

• Updated the Test-M365PowerShellDataFile function to allow specifying to disable checking
  for Required parameters. This is specifically useful for individual, not yet merged, data
  files. There required parameters could not exist, because they are coming from a different file.
• Optimized unit tests for Test-M365PowershellDataFile

Fixed

• Fixed issue in Convert-M365DSCExportToPowerShellDataFile where parameter in ConvertTo-Expression
  has been removed
• Corrected pipeline yaml output where the file was encoded as UTF8 instead of UTF8 with BOM. Now
  code always outputs UTF8 with BOM