Open raandree opened 1 year ago
This seems to be caused by a bug in MSCloudLoginAssistant
. I have created the issue Microsoft/MSCloudLoginAssistant#172. As nobody else seem to have the problem I am wondering if this is really a bug or of just nobody uses Microsoft365DSC to configure EXO.
Description of the issue
Using the EXOTransportConfig resource with managed identity throws
Insufficient access rights to perform the operation
even if all required permissions are available. When setting the transport config manually using the cmdletSet-TransportConfig
after creating a connection in the context of the managed identity (Connect-ExchangeOnline -ManagedIdentity
), things are working fine.It seems that the issue is here in the MSCloudLoginAssistant module. When connecting to Exchange Online by providing the organization's "flat name" (
$Global:MSCloudLoginConnectionProfile.OrganizationName
), we are running into the issue. When providing the full domain name ($Global:MSCloudLoginConnectionProfile.ExchangeOnline.TenantId
), things work.What do you think about this? Would using the full domain name cause other things to fail?
Microsoft 365 DSC Version
1.23.830.1
Which workloads are affected
Exchange Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version