If you run Microsoft Identity Manager (MIM), or its predecessor Forefront Identity Manager (FIM), the question on the table in 2026 is no longer should we replace this, it is when and with what. This post collects what is publicly known about MIM's support timeline as at May 2026, where Microsoft is steering customers next, and what realistic replacement paths look like for organisations on Microsoft Entra ID.
Is MIM still supported by Microsoft?
Yes, but with the runway narrowing.
- Mainstream support for MIM 2016 has ended. There are no further feature releases planned.
- Extended support is currently scheduled to end in January 2029. During this window Microsoft provides security and high-severity bug fixes only.
- Microsoft has consistently signalled in its product guidance and Microsoft Learn documentation that Entra ID Governance is the strategic direction for cloud-first customers replacing MIM workloads.
- Custom rules-extensions, PowerShell workflows and the on-premises FIM Service / FIM Sync infrastructure all remain in scope for customer-side support obligations: i.e. Microsoft will fix the product, but your customisations remain yours to maintain.
The practical reading: if your renewal cycle reaches January 2029, you are running unsupported software. Any migration program that takes 18–24 months from kick-off to cut-over needs to start in 2026 to be safe.
Why Microsoft is steering customers to Entra ID Governance
Microsoft's own framing positions Entra ID Governance as the cloud-native successor for the MIM use cases organisations actually rely on:
- Joiner-Mover-Leaver (JML) automation for workforce and guest accounts.
- Access reviews and access certifications mapped to controls like ISO 27001 Annex A.5.18.
- Entitlement management and access packages for self-service.
- Lifecycle workflows that approximate MIM's rules-extensions in declarative form.
For organisations already paying Entra ID P2, layering Entra ID Governance can feel like the path of least resistance. The challenge (and the reason this market is not yet settled) is that Entra ID Governance is licensed per user per month, which inverts the economics for organisations with a large workforce, a large guest population, or a constrained Entra ID Governance budget.
What the realistic replacement options look like in 2026
Three patterns are visible across Australian customers we work with:
- Lift to Entra ID Governance: works well where every user already has Entra ID P2 and the workforce count is modest. Cost scales linearly with seats; behaviour gaps versus MIM still need bespoke logic.
- Lift to a third-party IGA suite (SailPoint, Saviynt, Omada and similar): features-rich but typically a multi-year program with consulting cost that dwarfs the licence cost.
- Lift to a flat-fee, Entra-native platform like Apporetum: fixed monthly subscription, deployed from Azure Marketplace directly into your tenant, with an Insight mode that lets it run alongside MIM during migration. Designed to extend Entra ID rather than parallel it.
Apporetum supports a phased migration off MIM/FIM with three stages (Insight mode, Coexistence, Cutover), so each workload moves on its own schedule and is reversible.
What to do in 2026
A pragmatic checklist if MIM is in your estate:
- Catalogue every MIM-driven flow (HR → AD, secondary accounts, Entra provisioning, custom workflows) and tag the business owner.
- Establish what fails if MIM stops on January 1, 2029, and decide which of those failures is acceptable.
- Run a 6–8 week Insight-mode trial of a replacement platform to surface the gap list before you commit to a migration strategy.
- Build a TCO model that compares per-user IGA licensing against flat-fee alternatives at your real seat count, not the salesperson's seat count.
If you want help shaping that plan against Microsoft's published support dates, book a demo or read our overview of replacing MIM with Apporetum.
Sources and verification: Microsoft's current MIM 2016 lifecycle entry on Microsoft Learn is the authoritative reference for support dates. Always verify the published dates against learn.microsoft.com before sharing internally. Microsoft has the right to adjust the lifecycle policy.