Yes. MX11 can run most MX10 Marketplace modules via the backward-compatibility layer, but Graph/OIDC-related connectors are a common exception because they often ship bundled Java libs (for example, older Jackson / Apache HttpClient) that can clash with MX11’s runtime and cause Java compile/runtime issues.
Recommended path in MX11 (practical workaround):
Use the latest official Microsoft Graph Connector and the latest OIDC module, then fix any Java conflicts by cleaning up duplicated/old JARs.
• Install/upgrade Microsoft Graph Connector (official) to the newest version.
• Upgrade OIDC to a recent version compatible with MX11.
• If you need the OIDC “bridge” behavior: Microsoft Graph Commons (Siemens) explicitly supports using OIDC Token objects (with Microsoft as IdP).
If you hit Java compile errors in MX11:
It’s usually caused by duplicate/outdated JARs sitting in userlib/vendorlib (especially Jackson). Clean them up and let Mendix re-resolve dependencies (remove the older duplicates, then re-import/update the module). This is a very typical cause of MX11 compilation failures after upgrades.