Chris H

The Exchange PowerShell team probably aren't considering PS 5.1 compatibility a priority?

It's an issue with Exchange PowerShell. In the original example above, Microsoft365DSC is sending AutoExpandingArchive as a Boolean parameter ([which is the correct type](https://learn.microsoft.com/en-us/powershell/module/exchangepowershell/set-organizationconfig?view=exchange-ps)), but Set-OrganizationConfig is still failing. Take...

@FabienTschanz Is it worth proposing switching EXOOrganizationConfig to internally use PowerShell 7 with the work you did under #5433? Just that although Windows PowerShell 5.1 is [supposed](https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#windows) to be supported...

@FabienTschanz I presume you’re aware the LCM (which provides the ‘configuration engine’ for Microsoft365DSC and is triggered by the Start/Test/Set-DscConfiguration cmdlets) is a Windows PowerShell 5.1 feature as yet unsupported...

@FabienTschanz P.S. If prerequisite modules are only installed in C:\Program Files\PowerShell\7\Modules (not C:\Program Files\WindowsPowerShell\Modules) I suspect any functionality relying on the LCM will no longer work.

@FabienTschanz Sure. As I understand it: - In DSC 2.0 / PowerShell Core you can [use Invoke-DscResource](https://learn.microsoft.com/en-us/powershell/dsc/concepts/get-test-set?view=dsc-2.0) to run the Get/Test/Set functions on individual resources at will - In DSC...

- Also - it looks like Export-TargetResource, may not depend on or use the LCM in any way. It is a [Reverse-DSC specific extension](https://microsoft365dsc.com/contributing/develop-new-resource/) to the normal DSC resource schema....

In terms of making use of PowerShell Core and PnP.PowerShell 2.x, has any thought been given to using syntax like this in the relevant modules? ``` $codetorun = { Write-Output...

@FabienTschanz Sorry, not quite sure about the details of what you're saying here? Are you saying that you want to run all the internals of Microsoft 365 DSC in PowerShell...

@FabienGilbert Ah, understood. I guess I can see advantages and disadvantages to moving everything to a PowerShell Core layer: **Pros** - More consistency, predictable behaviour between modules - Ability to...