Topic starter
08/07/2026 7:04 pm
TL;DR: SAP IDM reaches end of mainstream maintenance in December 2027, and after that SAP will no longer issue security patches, bug fixes, or compliance updates, according to OpenIAM. The real issue is not whether to migrate, but whether identity governance teams use the next renewal cycle to choose a controlled path before unsupported infrastructure becomes an audit and operational liability.
Editorial analysis by NHI Mgmt Group, based on content published by OpenIAM: “SAP IDM is being retired — what manufacturing companies need to do before their next renewal”.
Key questions
Q: What breaks when SAP IDM is retired before its governance workflows are replaced?
A: The main failure is not authentication, it is lifecycle control.
Q: Why does an unsupported identity platform become a compliance problem?
A: Because auditors do not only assess whether access exists, they assess whether the system enforcing access is supported, patched, and change-controlled.
Q: How should teams choose between SAP IAS and a third-party IGA platform?
A: Choose IAS and IPS when the governance problem is mostly SAP-bound and the organisation wants the narrowest viable migration.
Practitioner guidance
- Document the current SAP IDM control surface Inventory every joiner-mover-leaver flow, approval route, certification cycle, and HR integration that SAP IDM currently runs so the replacement scope is grounded in real governance dependency.
- Separate SAP-only governance from enterprise-wide governance Determine which access processes live only inside SAP and which already extend into Microsoft, ServiceNow, Salesforce, or other non-SAP systems before deciding on IAS, IPS, or a broader IGA platform.
- Treat support dates as control deadlines Map the December 2025 and December 2027 milestones to your renewal calendar, audit calendar, and change window so the programme is tracked as a lifecycle risk rather than a vendor event.
Bottom line: SAP IDM retirement matters because lifecycle governance, not just access software, depends on a supported control environment.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
08/07/2026 7:27 pm
Support sunsets are identity governance events, not procurement notes: When a core lifecycle platform loses mainstream maintenance, the control environment changes even if the workflow screens look the same. The problem is not just patch availability but the loss of a vendor-backed evidence trail that auditors and governance teams rely on. Manufacturing organisations should treat product retirement as a governance transition with control-owner accountability attached.
A question worth separating out:
Q: What should manufacturing IAM teams do before the next renewal cycle?
A: They should document current workflows, identify the true dependency scope, and align the migration decision to the next renewal window rather than the final deadline. That keeps the programme in control, preserves budget leverage, and avoids a forced choice under time pressure.
👉 Read our full editorial: SAP IDM retirement raises urgent renewal choices for manufacturers