Microsoft.Entra interoperability/conflict with Microsoft.Graph

[hmhackmaster]

Before I go down the line of creating a bug for this, I figured I would start a discussion to help sanity-check what I am (repeatedly) experiencing.

Microsoft.Entra (version 1.0.4; released 2025-03-14) attempts to install the following modules
Install-Module -Name Microsoft.Entra -WhatIf

Module Name	Module Version
Microsoft.Entra	1.0.4
Microsoft.Entra.Applications	1.0.4
Microsoft.Entra.Authentication	1.0.4
Microsoft.Entra.DirectoryManagement	1.0.4
Microsoft.Entra.Governance	1.0.4
Microsoft.Entra.Groups	1.0.4
Microsoft.Entra.Reports	1.0.4
Microsoft.Entra.SignIns	1.0.4
Microsoft.Entra.Users	1.0.4
Microsoft.Graph.Applications	2.25.0
Microsoft.Graph.Authentication	2.25.0
Microsoft.Graph.Groups	2.25.0
Microsoft.Graph.Identity.DirectoryManagement	2.25.0
Microsoft.Graph.Identity.Governance	2.25.0
Microsoft.Graph.Identity.SignIns	2.25.0
Microsoft.Graph.Reports	2.25.0
Microsoft.Graph.Users	2.25.0
Microsoft.Graph.Users.Actions	2.25.0
Microsoft.Graph.Users.Functions	2.25.0

Microsoft.Graph (version 2.26.1; released 2025-02-25) attempts to install the following modules:
Install-Module -Name Microsoft.Graph -WhatIf

Module Name	Module Version
Microsoft.Graph	2.26.1
Microsoft.Graph.Authentication	2.26.1
Microsoft.Graph.Applications	2.26.1
Microsoft.Graph.Bookings	2.26.1
Microsoft.Graph.BackupRestore	2.26.1
Microsoft.Graph.Calendar	2.26.1
Microsoft.Graph.ChangeNotifications	2.26.1
Microsoft.Graph.CloudCommunications	2.26.1
Microsoft.Graph.Compliance	2.26.1
Microsoft.Graph.CrossDeviceExperiences	2.26.1
Microsoft.Graph.Devices.CloudPrint	2.26.1
Microsoft.Graph.Devices.CorporateManagement	2.26.1
Microsoft.Graph.Devices.ServiceAnnouncement	2.26.1
Microsoft.Graph.DeviceManagement	2.26.1
Microsoft.Graph.DeviceManagement.Administration	2.26.1
Microsoft.Graph.DeviceManagement.Enrollment	2.26.1
Microsoft.Graph.DeviceManagement.Functions	2.26.1
Microsoft.Graph.DirectoryObjects	2.26.1
Microsoft.Graph.Education	2.26.1
Microsoft.Graph.Files	2.26.1
Microsoft.Graph.Groups	2.26.1
Microsoft.Graph.Identity.DirectoryManagement	2.26.1
Microsoft.Graph.Identity.Governance	2.26.1
Microsoft.Graph.Identity.SignIns	2.26.1
Microsoft.Graph.Identity.Partner	2.26.1
Microsoft.Graph.Mail	2.26.1
Microsoft.Graph.Notes	2.26.1
Microsoft.Graph.People	2.26.1
Microsoft.Graph.PersonalContacts	2.26.1
Microsoft.Graph.Planner	2.26.1
Microsoft.Graph.Reports	2.26.1
Microsoft.Graph.SchemaExtensions	2.26.1
Microsoft.Graph.Search	2.26.1
Microsoft.Graph.Security	2.26.1
Microsoft.Graph.Sites	2.26.1
Microsoft.Graph.Teams	2.26.1
Microsoft.Graph.Users	2.26.1
Microsoft.Graph.Users.Actions	2.26.1
Microsoft.Graph.Users.Functions	2.26.1

Since Microsoft.Entra installs the older version of the various Microsoft.Graph modules (2.25.0; released 2024-11-21), this causes a direct conflict between the two different module packages.

Now I would typically end it there, facing the unfortunate situation that the two modules cannot exist on the same machine at the same time (something I see as not-uncommon situation since Microsoft.Entra extends the Graph modules and use them both as I do fun things with the Graph while also developing scripts for my service desk and other groups who greatly benefit from "scenario-optimized Microsoft Entra resource management" modules).

Except, this incompatibility seems to be contrary to the documentation:

What is the difference between Microsoft Graph PowerShell SDK and Microsoft Entra PowerShell modules?

...As the module builds on the Microsoft Graph PowerShell SDK, it's interoperable.

Is the Microsoft Entra PowerShell module compatible with Microsoft Graph PowerShell?

Both modules work together, and whether you use Microsoft Entra PowerShell module cmdlets or Microsoft Graph PowerShell SDK cmdlets to manage Microsoft Entra resources is a matter of preference.

I can certainly think of several ways to mitigate/resolve these issues, but before I go down that road I wanted to see if I am simply doing something wrong or expecting something that's outside the scope of what is supported.

Thanks!

[SamErde]

Good questions! Hopefully this will help clarify things a little:

The good news (generally speaking) is that you can indeed have multiple versions of a PowerShell module installed at the same time. Here is an example of what versions I have installed for the Graph modules:

# Get-Module -ListAvailable -Name "Microsoft.Graph*" | Sort-Object -Property Name,Version | Format-Table Version,Name -AutoSize

Version Name
------- ----
2.15.0  Microsoft.Graph.Applications
2.24.0  Microsoft.Graph.Applications
2.25.0  Microsoft.Graph.Applications
2.26.0  Microsoft.Graph.Applications
2.26.1  Microsoft.Graph.Applications
2.9.1   Microsoft.Graph.Authentication
2.15.0  Microsoft.Graph.Authentication
2.24.0  Microsoft.Graph.Authentication
2.25.0  Microsoft.Graph.Authentication
2.26.0  Microsoft.Graph.Authentication
2.26.1  Microsoft.Graph.Authentication
2.25.0  Microsoft.Graph.Beta.Applications
2.26.1  Microsoft.Graph.Beta.Applications
2.25.0  Microsoft.Graph.Beta.DirectoryObjects
2.26.1  Microsoft.Graph.Beta.DirectoryObjects
2.25.0  Microsoft.Graph.Beta.Groups
2.26.1  Microsoft.Graph.Beta.Groups
2.25.0  Microsoft.Graph.Beta.Identity.DirectoryManagement
2.26.1  Microsoft.Graph.Beta.Identity.DirectoryManagement
2.25.0  Microsoft.Graph.Beta.Identity.SignIns
2.26.1  Microsoft.Graph.Beta.Identity.SignIns
2.25.0  Microsoft.Graph.Beta.Users
2.26.1  Microsoft.Graph.Beta.Users
2.15.0  Microsoft.Graph.DirectoryObjects
2.24.0  Microsoft.Graph.DirectoryObjects
2.25.0  Microsoft.Graph.DirectoryObjects
2.26.0  Microsoft.Graph.DirectoryObjects
2.26.1  Microsoft.Graph.DirectoryObjects
2.15.0  Microsoft.Graph.Groups
2.24.0  Microsoft.Graph.Groups
2.25.0  Microsoft.Graph.Groups
2.26.0  Microsoft.Graph.Groups
2.26.1  Microsoft.Graph.Groups
2.15.0  Microsoft.Graph.Identity.DirectoryManagement
2.24.0  Microsoft.Graph.Identity.DirectoryManagement
2.25.0  Microsoft.Graph.Identity.DirectoryManagement
2.26.0  Microsoft.Graph.Identity.DirectoryManagement
2.26.1  Microsoft.Graph.Identity.DirectoryManagement
2.15.0  Microsoft.Graph.Identity.Governance
2.24.0  Microsoft.Graph.Identity.Governance
2.25.0  Microsoft.Graph.Identity.Governance
2.26.0  Microsoft.Graph.Identity.Governance
2.26.1  Microsoft.Graph.Identity.Governance
2.15.0  Microsoft.Graph.Identity.SignIns
2.24.0  Microsoft.Graph.Identity.SignIns
2.25.0  Microsoft.Graph.Identity.SignIns
2.26.0  Microsoft.Graph.Identity.SignIns
2.26.1  Microsoft.Graph.Identity.SignIns
2.15.0  Microsoft.Graph.Reports
2.24.0  Microsoft.Graph.Reports
2.25.0  Microsoft.Graph.Reports
2.26.0  Microsoft.Graph.Reports
2.26.1  Microsoft.Graph.Reports
2.15.0  Microsoft.Graph.Users
2.24.0  Microsoft.Graph.Users
2.25.0  Microsoft.Graph.Users
2.26.0  Microsoft.Graph.Users
2.26.1  Microsoft.Graph.Users
2.15.0  Microsoft.Graph.Users.Actions
2.24.0  Microsoft.Graph.Users.Actions
2.25.0  Microsoft.Graph.Users.Actions
2.26.0  Microsoft.Graph.Users.Actions
2.26.1  Microsoft.Graph.Users.Actions
2.15.0  Microsoft.Graph.Users.Functions
2.24.0  Microsoft.Graph.Users.Functions
2.25.0  Microsoft.Graph.Users.Functions
2.26.0  Microsoft.Graph.Users.Functions
2.26.1  Microsoft.Graph.Users.Functions

This is supported by design to help avoid the kind of compatibility problems that you described.

This allows module authors to import a specific version of another module dependency. For example: Import-Module -Name Microsoft.Graph.Authentication -RequiredVersion 2.25.0.

Yes, there are still potential issues. While multiple versions can exist on the same machine, if you try to import a specific version after another one has already been imported, you will get an error.

(Import-Module: Could not load file or assembly 'Microsoft.Graph.Authentication, Version=2.26.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Assembly with same name is already loaded)

I haven't needed to delve into solutions for this yet but have a hunch that run spaces might be the way to work around it.