AADTenantDetail: Set-TargetResource silently fails

[AlexJPawlak]

Details of the scenario you tried and the problem that is occurring

Getting started with Microsoft 365 DSC, tried to follow simple "getting started" resource. Replaced my values with placeholders. Phone number in format: +{country code}{myphoneNumber} -

Verbose logs showing the problem

VERBOSE: [WINSRV-M365DSCH]: [[AADTenantDetails]TenantDetailsg] Target-Values: ApplicationId=redacted; CertificateThumbprint=redacted; IsSingleInstance=Yes; MarketingNotificationEmails=([email protected]); SecurityComplianceNotificationMails=([email protected]); SecurityComplianceNotificationPhones=(+CCDDDDDDDDD); TechnicalNotificationMails=([email protected]); TenantId=redacted; Verbose=True VERBOSE: [WINSRV-M365DSCH]: [[AADTenantDetails]TenantDetailsg] Test-TargetResource returned False VERBOSE: [WINSRV-M365DSCH]: LCM: [ End Test ] [[AADTenantDetails]TenantDetailsg] in 13.9020 seconds. VERBOSE: [WINSRV-M365DSCH]: LCM: [ Start Set ] [[AADTenantDetails]TenantDetailsg] VERBOSE: [WINSRV-M365DSCH]: [[AADTenantDetails]TenantDetailsg] Setting configuration of AzureAD Tenant Details VERBOSE: [WINSRV-M365DSCH]: [[AADTenantDetails]TenantDetailsg] Cannot Set AzureAD Tenant Details

Suggested solution to the issue

When running the command manually, "Set-AzureADTenantDetail" - works just fine, with the same service principal and certificate.

The DSC configuration that is used to reproduce the issue (as detailed as possible)

# insert configuration here

Node Localhost
{
    AADTenantDetails TenantDetailsg {
        TechnicalNotificationMails           = "[email protected]"
        SecurityComplianceNotificationPhones = "+CCDDDDDDDDD"
        SecurityComplianceNotificationMails  = "[email protected]"
        MarketingNotificationEmails          = "[email protected]"
        IsSingleInstance                     = 'Yes'
        CertificateThumbprint                = $CertificateThumbprint
        TenantId                             = $TenantId
        ApplicationId                        = $ApplicationId
        
    }
}

The operating system the target node is running

Fresh installation of Windows Server 2019 Standard, Core Edition, **running Powershell 7.1 ** does not produce verbose output, only 5.1 does.
OsName : Microsoft Windows Server 2019 Standard OsOperatingSystemSKU : StandardServerEdition OsArchitecture : 64-bit WindowsVersion : 1809 WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434 OsLanguage : en-US OsMuiLanguages : {en-US}

Version of the DSC module that was used ('dev' if using current dev branch)

Dev

Happy to share more details as needed on private channel. Otherwise, thank you for promising tool! :-)