O365OrgSettings issue with V1.24.626.1 about microsoft365dsc HOT 3 CLOSED

No logic changes have been made to that resource in close to 2 months. Something else must have changed. What was the previous version of M365DSC you were using that worked?

from microsoft365dsc.

The export is failing on New-MgServicePrincipal this is code for service principals that might be not yet created on the tenant, which they should, the reason why it's failing it's due to lacking Application.ReadWrite.All to create those service principals, even during export.

from microsoft365dsc.

No logic changes have been made to that resource in close to 2 months. Something else must have changed. What was the previous version of M365DSC you were using that worked?

It seems that you are right. I finally found that the issue was not affecting all tenants but mainly the new ones and that it was due to this part of the resource code:

    _$OfficeOnlineId = 'c1f33bc0-bdb4-4248-ba9b-096807ddb43e'
    $M365WebEnableUsersToOpenFilesFrom3PStorageValue = Get-MgServicePrincipal -Filter "appId eq '$OfficeOnlineId'" -Property 'AccountEnabled' -ErrorAction SilentlyContinue
    if ($null -eq $M365WebEnableUsersToOpenFilesFrom3PStorageValue)
    {
        Write-Verbose -Message "Registering the Office on the web Service Principal"
        New-MgServicePrincipal -AppId 'c1f33bc0-bdb4-4248-ba9b-096807ddb43e' -ErrorAction Stop | Out-Null
        $M365WebEnableUsersToOpenFilesFrom3PStorageValue = Get-MgServicePrincipal -Filter "appId eq '$OfficeOnlineId'" -Property 'AccountEnabled' -ErrorAction SilentlyContinue
    }_

If the Office on the web Service Principal does not exist, the script tries to create it. As we are not allowed to have write permissions on the tenant that we audit I will do this upfront on my script that create the Entra ID app required for M365DSC.

from microsoft365dsc.