Must connect to ExchangeOnlineManagement 3.8.0-preview before graph SDK

[gwgaston]

Just updated to ExchangeOnlineManagement 3.8.0-Preview1 and Graph SDK 2.26.1 and now find that if I connect to Exchange first, then Graph SDK it works fine, but if I reverse that and connect to Graph first then on my connection attempt to Exchange I get an .NET related error:

Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder
Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker(Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'.
At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.8.0\netFramework\ExchangeOnlineManagementBeta.psm1:764 char:21

•                 throw $_.Exception.InnerException;
  

•                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : OperationStopped: (:) [], MissingMethodException
  • FullyQualifiedErrorId : Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker
    (Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'.

[ColomJa]

I have the same issue with v3.8.0 (GA release).

I'm required to load ExchangeOnlineManagement before loading MS Graph Authentication.

This is becoming a real issue... I've noticed this with MSGraph, SQLServer, and now ExchangeOnlineManagement.
Some sort of compatibility testing should really be part of the process.

Using:

• Microsoft.Graph 2.28.0
• ExchangeOnlineManagement 3.8.0

[mark3grahams]

Connect-ExchangeOnline

OperationStopped: Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder
Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker(Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'.




[System.AppDomain]::CurrentDomain.GetAssemblies() | Where-Object { $_.FullName -like "*Microsoft.Identity.Client*" }

CodeBase               : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.Extensions.Msal.dll
EntryPoint             : 
EscapedCodeBase        : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.Extensions.Msal.dll
FullName               : Microsoft.Identity.Client.Extensions.Msal, Version=4.65.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae
GlobalAssemblyCache    : False
HostContext            : 0
ImageFileMachine       : 
ImageRuntimeVersion    : v4.0.30319
Location               : D:\PowerShell\Modules\Az.Accounts\5.0.1\StartupScripts\..\lib\netstandard2.0\Microsoft.Identity.Client.Extensions.Msal.dll
ManifestModule         : Microsoft.Identity.Client.Extensions.Msal.dll
MetadataToken          : 
PortableExecutableKind : 
ReflectionOnly         : False

CodeBase               : file:///D:/PowerShell/Modules/ExchangeOnlineManagement/3.8.0/netCore/Microsoft.Identity.Client.dll
EntryPoint             : 
EscapedCodeBase        : file:///D:/PowerShell/Modules/ExchangeOnlineManagement/3.8.0/netCore/Microsoft.Identity.Client.dll
FullName               : Microsoft.Identity.Client, Version=4.66.1.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae
GlobalAssemblyCache    : False
HostContext            : 0
ImageFileMachine       : 
ImageRuntimeVersion    : v4.0.30319
Location               : D:\PowerShell\Modules\ExchangeOnlineManagement\3.7.2\netCore\Microsoft.Identity.Client.dll
ManifestModule         : Microsoft.Identity.Client.dll
MetadataToken          : 
PortableExecutableKind : 
ReflectionOnly         : False

CodeBase               : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.Broker.dll
EntryPoint             : 
EscapedCodeBase        : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.Broker.dll
FullName               : Microsoft.Identity.Client.Broker, Version=4.65.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae
GlobalAssemblyCache    : False
HostContext            : 0
ImageFileMachine       : 
ImageRuntimeVersion    : v4.0.30319
Location               : D:\PowerShell\Modules\Az.Accounts\5.0.1\StartupScripts\..\lib\netstandard2.0\Microsoft.Identity.Client.Broker.dll
ManifestModule         : Microsoft.Identity.Client.Broker.dll
MetadataToken          : 
PortableExecutableKind : 
ReflectionOnly         : False

CodeBase               : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.dll
EntryPoint             : 
EscapedCodeBase        : file:///D:/PowerShell/Modules/Az.Accounts/5.0.1/StartupScripts/../lib/netstandard2.0/Microsoft.Identity.Client.dll
FullName               : Microsoft.Identity.Client, Version=4.65.0.0, Culture=neutral, PublicKeyToken=0a613f4dd989e8ae
GlobalAssemblyCache    : False
HostContext            : 0
ImageFileMachine       : 
ImageRuntimeVersion    : v4.0.30319
Location               : D:\PowerShell\Modules\Az.Accounts\5.0.1\StartupScripts\..\lib\netstandard2.0\Microsoft.Identity.Client.dll
ManifestModule         : Microsoft.Identity.Client.dll
MetadataToken          : 
PortableExecutableKind : 
ReflectionOnly         : False

[NZLostboy]

I am having the same issue with the GA release using PowerShell 7.5.1. I rolled back to a few versions previous and it is working fine.

[raandree]

I am getting the same issue with 3.7.2 and 3.8.0. Downgrading to 3.7.1 solves the issue but is not an option as as Microsoft365DSC has a dependency on 3.7.2.

The workaround that works for me is:

$dummyCred = [pscredential]::new('dummy', (New-Object System.Security.SecureString))
Import-Module -Name ExchangeOnlineManagement
try
{
    Connect-ExchangeOnline -UserPrincipalName dummy@contoso.com -Credential $dummyCred | Out-Null
}
catch
{
    # Exception is expected
}

Important

Connect-ExchangeOnline must be called with the UserPrincipalName parameter, otherwise the workaround does not work.

There seems to be an interference with some other modules, in my case very likely with Az.Accounts and / or Az.Resources. Loading the ExchangeOnlineManagement first AND calling Connect-ExchangeOnline makes PowerShell loading the needed types and then the cnnecting to Exchange works. However, I am not sure if this breaks something else in the Az.* modules.

I will create an issue for that.

[SamErde]

HOW did you figure out that a fake credential would work?! 🤯 I’ve been using a real UPN to get through this but that’s not always a desirable option so I’m excited to try this workaround.

EDIT: This didn't work for me.

[jsheehan14]

The Exchange Online Management module V3.8 is definitely unstable. The fix for me was also to downgrade to V3.7. Will be interested if the issue that raandree raised gets a response out of Microsoft.

[raandree]

@jsheehan14, right, all versions above 3.7.0 caused some issues.

@SamErde, the fake credentials don't connect you to Exchange Online of course, but doing that makes PowerShell load the right DLLs and Types so things work. However, as expected, after that there are issues with the Az* modules. It is such a big mess...

[SamErde]

OK, now I feel a little less crazy. 😅

[SamErde]

I have found that the dependency conflict can usually be avoided if modules get imported in this order:

1. Microsoft.Graph
2. MicrosoftTeams
3. ExchangeOnlineManagement (EXO)
4. ExchangeOnlineManagement (IPPSSession)
5. Az.Account

Currently working on a script to dynamically determine the order in which to import these, based on the version of Microsoft.Identity.Client.dll that is included in each of these modules.

[stukey]

We are also experiencing this issue when loading the Graph PowerShell SDK modules in our scripts prior to the ExchangeOnlineManagement module using the #Requires statement (can be repo’d interactively using Import-Module cmdlet). There was a similar issue last year (see: #2803) and until Microsoft fixed it in ExchangeOnlineManagement module version 3.6.0, the workaround was to load the Graph modules before ExchangeOnlineManagement. Now the workaround for this new issue has been to load ExchangeOnlineManagement before the Graph modules. It’s ridiculous that Microsoft keeps introducing these bugs. Where is the regression and compatibility testing for these modules.

Example:

Windows 11
PowerShell 5.1
ExchangeOnlineManagement version 3.8.0
Microsoft.Graph version 2.28.0

Import-Module Microsoft.Graph.Authentication
Import-Module Microsoft.Graph.Users
Import-Module ExchangeOnlineManagement
  
Connect-ExchangeOnline -Credential $EXO_Cred -Verbose
 
VERBOSE: Computed version info: 3.8.0
VERBOSE: ModuleVersion: 3.8.0
VERBOSE: ConnectionContext Removed
 
Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder
Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker(Microsoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'.
At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.8.0\netFramework\ExchangeOnlineManagement.psm1:754 char:21
+                     throw $_.Exception.InnerException;
+                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], MissingMethodException
    + FullyQualifiedErrorId : Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Identity.Client.Broker.BrokerExtension.WithBroker(Mic
   rosoft.Identity.Client.PublicClientApplicationBuilder, Microsoft.Identity.Client.BrokerOptions)'.