EXOCASMailboxPlan

[NikCharlebois]

Description of the issue

Mentioning the CAS Mailbox Plan by name instead of ID should work. Currently the resource is forcing the user to pass in the GUID part of the config to get a match, but this will differ between tenants and is blocking the resource's to be used in cloning scenarios.

Microsoft 365 DSC Version

1.23.1108.3

Which workloads are affected

Exchange Online

The DSC configuration

EXOCASMailboxPlan "EXOCASMailboxPlan-ExchangeOnlineDeskless"
{
    ActiveSyncEnabled    = $True;
    Credential           = $Credscredential;
    Identity             = "ExchangeOnlineDeskless";
    ImapEnabled          = $False;
    OwaMailboxPolicy     = "OwaMailboxPolicy-Default";
    PopEnabled           = $false;
}

Verbose logs showing the problem

PowerShell DSC resource MSFT_EXOCASMailboxPlan  failed to execute Set-TargetResource functionality with error message:
The specified CAS Mailbox Plan {ExchangeOnlineDeskless} doesn't exist

Environment Information + PowerShell Version

OsName               : Microsoft Windows 11 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 
OsLanguage           : en-US
OsMuiLanguages       : {en-US}



PS C:\dsc>
PS C:\dsc> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1