Description of the issue

The EXOAcceptedDomain resource reports false configuration drift and executes unnecessary Set operations due to error suppression in Test.

Evidence

LCM execution log:

Drift event payload:

<M365DSCEvent> <ConfigurationDrift Source="MSFT_EXOAcceptedDomain" TenantId="contoso.onmicrosoft.com" LCMState="ConsistencyCheck"> <ParametersNotInDesiredState> <Param Name="Ensure"> <CurrentValue>Absent</CurrentValue> <DesiredValue>Present</DesiredValue> </Param> </ParametersNotInDesiredState> </ConfigurationDrift> <DesiredValues> <Param Name ="Ensure">Present</Param> <Param Name ="Identity">contoso.com</Param> <!-- Redacted --> </DesiredValues> <CurrentValues> <Param Name ="Ensure">Absent</Param> <Param Name ="Identity">contoso.com</Param> <!-- Redacted --> </CurrentValues> </M365DSCEvent>

Analysis

Successful consistency checks complete in <1 second, but failed executions take >60 seconds, indicating a timeout. The error is suppressed, causing the resource to incorrectly proceed to Set. When Test encounters failures, Set must not be executed. The resource should handle errors properly and throw a non-terminating error instead of reporting drift.

We have dozens of EXOAcceptedDomain resource instances that are executed in sequence. This issue typically occurs to a random instance, which can also indicate that throttling is involved. We suggest looking into implementing an exponential backoff mechanism.

Root Cause

The culprit seems to be error suppression in this call:

$AcceptedDomain = Get-AcceptedDomain -Identity $Identity -ErrorAction SilentlyContinue if ($null -eq $AcceptedDomain) { Write-Verbose -Message "AcceptedDomain configuration for {$($Identity)} does not exist." return $nullReturn }

Permalink

Microsoft 365 DSC Version

1.25.1203.2

Which workloads are affected

Exchange Online

The DSC configuration

Verbose logs showing the problem

Environment Information + PowerShell Version