3.10.1

BREAKING CHANGE
Permission requirements has changed on script policies. DeviceManagementScripts.ReadWrite.All is now required and Consent Request might be required to add the permissions

New features

• Official PowerShell 7 Support

  • PowerShell 7 is now supported
    This is now the recommended way of using the tool.
    PowerShell 7 has full support for WAM authentication which is required for strong authentication like FIDO2 etc.

• Authentication

  • Added documentation on how to create a custom Entra app in MSAL Info
  • Changed permission requiremnt to DeviceManagementScripts.ReadWrite.All for
    • Compliance Scripts
    • Custom Attributes
    • Health Scripts
    • Scripts (PowerShell)
    • Scripts (Shell)

Fixes

• Generic

  • Cannot rename Settings Catalog
    Based on Issue 344

• Compare

  • Compare added letter N to the string output
    Based on Issue 320
  • Wrong Category when comparing Settings Catalog objects
    Based on Issue 317

• Import/Export

  • Basline Security Policy not imported
    Based on Issue 241
  • Fixed import of old exported Compliance Policies
    DeviceSettings property support removed and cause import failure
  • Custom Compliance Scripts were not imported befor the Compliance Policy
    Based on Issue 353
  • Added support for BIOS Configurations
    Based on Issue 350
  • Set default Conditional Access state in Settings
    Based on Issue 298

• Documentation

  • "Not configured" valued added when Uncofigured settings was selected
    Based on Issue 342
  • Add file content to documentation e.g. Custom Configuration profiles for MacOS
    Based on Issue 329
  • Output type for Word export - PDF is now supported
    Based on Discussion 329
  • Skip date in documentation output
    Based on Issue 336
  • Added support for Compliance Policies for Linux
  • Language files re-generated
  • AppTypes file re-generated

• ADMX Tool

  • Failed to import settings for some ADMX files
    Based on Issue 338