SailPoint, Saviynt or Entra ID Governance? Start with where your apps live
SailPoint, Saviynt and Microsoft Entra ID Governance all run access reviews and joiner-leaver automation, but they reach very different parts of an estate. Here's how they compare on price, connectors, SAP, on-premises apps and migration effort, and how to pick.
part 7 of 9 · Before you sign an identity contractthe ideaEntra covers the Microsoft side; SailPoint and Saviynt reach further
after reading, you can- Spot which apps each platform covers out of the box. Anything else is custom work someone pays for
- Spot the documented limits that change a design, like AD-synced groups in Entra
- Set up a pilot that tests the awkward apps, not the ones vendors like to demo
You'll live with an identity governancedefinitionThe tools and process that decide who should have what access, grant and remove it as people join, move and leave, and prove it to auditors. Often shortened to IGA. platform for years, and the three names on most shortlists do different jobs well. Start from where your applications sign in and how much of your estate is on-premises or SAP, then price the full scope before you compare features.
What identity governance is, in everyday words
Somebody has to decide who gets access to what, and then keep checking. That's identity governance. A new hire gets what the job needs on day one, a team move takes away what they don't need anymore, and a leaver loses everything the day they go. Every few months managers get asked whether people still need what they hold, and the answers go to the auditors. SailPoint and Saviynt sell specialist products for this. Entra ID Governance does it inside Microsoft's identity service, which plenty of companies already pay for.
Think of an office building's key office. Handing out keys is the easy part. The key office's real job is knowing who holds which key, getting keys back when people leave, and showing the landlord a list that matches the doors.
- CIOs and CISOs choosing an IGA tool
- Identity teams on IdentityIQ or MIM
- Companies with SAP or Oracle ERP
- Microsoft 365 shops weighing Entra
- Auditors and compliance leads
Why this choice matters now
Microsoft Identity Manager still runs on-premises in plenty of Microsoft shops, and for customers with Entra ID P1 or P2 its support now ends in January 2029. IdentityIQ customers have a choice to weigh between the announced 9.0 release and a move to SailPoint's cloud. Meanwhile every vendor is pushing governance for AI agents, often licensed separately. Any one of those puts the platform question back on someone's desk.
Getting it wrong is expensive in a quiet way. A tool that can't reach half your applications leaves someone reconciling spreadsheets before every audit, and the licence keeps billing anyway. Moving off an IGA platform later means rebuilding roles, rules and connectors, which is often the biggest cost.
-
01 List every app in audit scope
Pull the list your auditors test, with who owns each app and how many people use it.
-
02 Mark how each app connects
Is it in Entra already, a SaaS app with an API, an on-premises app, or SAP? That one column narrows the field fast.
-
03 Find the hard parts
Separation-of-duties rules for finance, AD groups that guard file shares, contractors outside HR, and any custom code in your current tool.
-
04 Price the full scope
Count everyone the licence has to cover, guests and agents too. Then add the work to connect each app, which often costs more.
-
05 Pilot on three hard apps
Give each vendor the apps that worry you most, like an on-premises app or the ERP. If the pilot only covers what they demo, you've learned nothing.
-
06 Decide and plan the move
Pick the tool, then plan the migration in waves so certifications keep running the whole time.
For engineers, the column that matters most is the connector model. Entra reaches on-premises apps through a provisioning agent and the ECMA Connector HostdefinitionThe piece Microsoft uses to provision from Entra into on-premises apps. It runs next to a provisioning agent, and you can load the connectors you built for Microsoft Identity Manager into it., which can import the ECMA2 connectors you built for MIM. SailPoint and Saviynt each sell a catalogue of their own connectors and let you build more for the apps they don't cover.
SailPoint, Saviynt and Entra side by side
We kept to what each vendor's documentation and pricing pages say today. Neither SailPoint nor Saviynt publishes prices, so the cost row says what drives the number, and the Entra figures are Microsoft's list prices before any discount.
| What you need | SailPoint | Saviynt | Entra ID Governance |
|---|---|---|---|
| How it's delivered | Identity Security Cloud (SaaS, on Atlas). IdentityIQ for on-premises | Identity Platform: SaaS in Saviynt's cloud, or deployed in your own AWS, Azure or GCP | Part of Microsoft Entra ID, SaaS only |
| Price | Not published. Suites: Standard, Agentic Business, Agentic Business Plus | Not published. Essentials, Pro and Premium, priced by identities | $7 per user per month list, on top of Entra ID P1 ($7). P2 tenants can buy a separate Step Up product |
| Connectors | 546 entries in the catalogue; IdentityIQ 9.0 docs cite 100+ built in | Vendor claims 300+ prebuilt, included in tier pricing | Entra-connected apps, SCIM, and on-premises apps via ECMA Connector Host |
| Joiner, mover, leaver | Lifecycle states, transforms and workflows | Lifecycle from onboarding to departure | Lifecycle Workflows (Governance or Entra Suite licence) |
| Access reviews | Certifications; AI can auto-certify low-risk access | Certifications; vendor claims up to 75% of decisions automated | Access reviews; ML-assisted reviews need the Governance licence |
| Roles | Role discovery in Access Modeling | Role-based access policies; no role-mining detail in public docs | Roles modelled as access packages; no role-mining tool found in docs |
| Separation of duties | Up to 500 SoD policies per tenant | Prebuilt rulesets for SAP, Workday and Oracle | Access packages or groups marked incompatible; finer SAP rules via SAP or partner tools |
| SAP | Connectors in the catalogue | Application Access Governance with SAP rulesets | Connectors to SAP ECC, Cloud Identity Services and SuccessFactors |
| Privileged access | Privileged Task Automation, which SailPoint says complements a PAM tool | PAM in the same platform, with just-in-time access | PIM for Entra and Azure roles (P2 or Governance) |
| AI agents | Agentic Fabric; agentic suites include non-human identities | Zuma (Insights, Access, Governance), launched July 2026 | Agent ID governance needs Microsoft 365 E7 or Agent 365 |
| US government | FedRAMP Moderate (since June 2024) | FedRAMP Moderate (since 2019); High listing (as of Oct 2026) shows no agency authorizations | Available in GCC, GCC High and DoD clouds |
| Moving from older tools | Free IdentityIQ assessment; Agentic Acceleration at no extra cost | Migration Workbench for IdentityIQ and Oracle Identity Manager | Microsoft guide for MIM and SAP IDM, one scenario at a time |
What changed in the last two years
SailPoint closed the deal in June. Entro works on non-human identities and secrets, the same area SailPoint's newer suites target.
SailPoint now sells Agentic Business and Agentic Business Plus next to Standard. Each comes with a one-time allotment of five non-human identities per human. SailPoint says that ratio may change before GA but won't drop below five.
A major on-premises release with time-bound access and an automated upgrade tool. SailPoint calls it a longer runway for IdentityIQ but hasn't published support dates.
KKR led the round, at roughly a $3 billion valuation. Saviynt later said it had passed $300 million in annual recurring revenue, which is worth knowing when you weigh a long contract.
Zuma is Saviynt's answer for AI identities, split into Insights, Access and Governance. Saviynt lists it on its platform page next to IGA and PAM. Ask which package it comes in before you budget.
A built-in tool for moving off IdentityIQ and Oracle Identity Manager. Saviynt says 60 to 70 percent of objects usually map straight across, so plan for the rest.
For customers with Entra ID P1 or P2, Microsoft moved MIM 2016's end of support from January 2026 to January 9, 2029. That buys time, and Microsoft still calls 2029 the end of life.
Microsoft says P2's current governance features stay, but new ones go into ID Governance only. Lifecycle Workflows already sit there.
How the three got here
- Mar 2019Saviynt cloud gets FedRAMP Moderate
- Jun 2024SailPoint ISC gets FedRAMP Moderate
- Feb 2025SailPoint IPO on Nasdaq (SAIL)
- Dec 2025Saviynt raises $700M led by KKR
- Jan 2026Entra guest governance billing enforced
- Jun 2026SailPoint closes Entro deal
- Jul 2026Saviynt launches Zuma for AI identities
- Oct 6, 2026IdentityIQ 9.0 announced
- Jan 9, 2029MIM 2016 end of support
Microsoft's own migration guide treats this as MIM's end of life.
Where each one wins, and the catch
Big, mixed estates usually lean toward SailPoint. Its catalogue lists more than 500 connectors and integrations, and if you can't move to SaaS yet, IdentityIQ still runs on your own servers. When reviewers face thousands of entitlements they can't judge, role discovery and AI-assisted certifications take some of the load off.
The catch is the road between its two products. Practitioners on SailPoint's developer forum keep saying IdentityIQ to the cloud is a rebuild. They report that plugins aren't available in Identity Security Cloud, and one forum member counted under 20 rule types in the cloud against about 200 in IdentityIQ, back in 2025. The more custom code you carry, the longer that move takes.
Saviynt fits teams that want governance, ERP access controls and PAM from one vendor. Its Application Access Governance ships separation-of-duties rulesets for SAP, Workday and Oracle, and Saviynt-built connectors are included in the tier price instead of sold one by one. You can host it in Saviynt's cloud or in your own AWS, Azure or GCP account, which some regulated buyers want.
Check two things before you sign. Test Saviynt's PAM against your privileged-access needs on its own, and ask whether you'll still keep a dedicated PAM tool next to it. Its migration tooling names IdentityIQ and Oracle Identity Manager, so if you're coming from something else, ask what it actually covers.
Entra ID Governance fits Microsoft-first companies whose apps already sign in through Entra. There's no new platform to run and the list price is public. Lifecycle Workflows, access packages and access reviews work on the same groups and apps your admins already manage, and API-driven inbound provisioning can take HR data from any system of record.
The catch is reach. Access reviewdefinitionA campaign where managers or app owners confirm whether each person still needs their access. Microsoft calls it an access review; SailPoint and Saviynt call it a certification. decisions can't change a group synced from on-premises Active Directory, so someone downloads the results and fixes AD by hand. The ECMA Connector Host only handles user objects today. On its own, Entra handles separation of dutiesdefinitionRules that stop one person holding two conflicting permissions, such as creating a supplier and approving its payments. Usually shortened to SoD. by marking access packages or groups as incompatible, and finer SAP rules need SAP's access governance or a partner product connected to it. Teams with heavy SAP rules or a big on-premises estate often end up adding a dedicated tool on top.
- One identity platform and one admin portal
- Public list price, licensed per user in scope
- Strong on Entra groups, Microsoft 365 and SaaS apps
- AD-managed groups need manual clean-up or a move to the cloud
- Basic SoD built in; finer rules need a partner tool
- Another platform and contract to run
- Price negotiated, driven by identities and scope
- Large connector catalogues for non-Microsoft apps
- Connected apps lose access when a review says so. Apps without a connector still need a person.
- Fine-grained SoD policies, with prebuilt ERP rulesets in Saviynt
The limits each vendor documents
Each of these comes from vendor documentation, the FedRAMP Marketplace or practitioners on vendor forums. They rarely make the sales deck, and each one can change your design.
- Entra: you need enough Governance licences for every member user in scope of a feature. Licensing only the IT team that builds the workflows doesn't cover it, as an answer on Microsoft Q&A confirms.
- Entra: when a review denies someone in a group synced from on-premises AD, the result isn't applied. Microsoft tells you to download the results and change the group in AD yourself.
- Entra: an accepted answer on Microsoft Q&A says Workday inbound provisioning can't run scheduled full syncs, so rules like enabling an account the day before hire may not fire on time.
- Entra: the provisioning agent doesn't update itself for on-premises app provisioning. Somebody has to own patching it.
- SailPoint: Identity Security Cloud tenants start with default limits of 3,000 access profiles and 800 roles, per practitioners on SailPoint's forum. SailPoint raises them on request, so ask early if your catalogue is big.
- SailPoint: forum members report that some IdentityIQ certification types, such as account group permissions, have no direct equivalent in the cloud yet.
- SailPoint: a practitioner on the forum advises against running IdentityIQ and the cloud side by side for long, especially with attribute sync on in both, because of data integrity problems.
- Saviynt: its FedRAMP High listing showed no agency authorizations in October 2026, and its own blog uses both 'achieved' and 'pursuing'. Federal buyers should confirm status directly.
What a move actually takes
Most of the cost of a governance project sits in the applications, the HR data and the roles, and that stays true whichever product you pick. The migration effort depends a lot on where you start.
From IdentityIQ to SailPoint's cloud. SailPoint offers a free assessment tool, and its Agentic Acceleration offer comes at no extra cost. Treat it as a re-design anyway. Practitioners say custom rules have to be redesigned as workflows, API calls or external services, and forum members report that plugins aren't supported and custom objects don't migrate directly.
From IdentityIQ or Oracle Identity Manager to Saviynt. Saviynt's Migration Workbench reads the old configuration and maps what it can. Saviynt says 60 to 70 percent of objects usually map directly. The rest needs specialists, with the tool's help, so budget for that part rather than the headline.
From MIM or SAP Identity Management to Entra. Microsoft publishes migration guides for both and recommends moving one scenario at a time. On-premises provisioning goes through the ECMA Connector Host, and you can bring over the configuration of custom MIM connectors. S/4HANA is reached through SAP Cloud Identity Services, so users have to exist in Entra first.
What to do now
What to do now, by role
- Ask for the list of apps your auditors test and how each one gets access granted and removed today.
- Decide whether one vendor for governance and PAM matters to you, or best-of-breed with integration work.
- Get every vendor to quote on the same identity count, guests and AI agents included. Otherwise the cheapest quote is usually the smallest scope.
- Tag every in-scope app: already in Entra, SaaS with an API, on-premises, or SAP.
- Count the AD groups that guard file shares and apps, since Entra reviews can't change those unless the group moves to the cloud.
- On IdentityIQ, export your custom rules, plugins and workflows and count them before any vendor does.
- Write down which separation-of-duties rules you must enforce at request time, not just report on.
- Check which FedRAMP level your contracts need, if any, or whether it has to be a US government cloud. Get each vendor's status in writing, since listings change.
- Agree what evidence an access review must produce so the pilot can be judged against it.
- Say which HR system owns start dates and leaving dates. Contractors are usually the gap, so check where they live.
- Sit in on the SoD ruleset work for ERP access; finance owns those rules, not IT.
Set it up so the next migration is easier
Choices that keep you portable
- 01Keep HR as the single source
Feed joiners, movers and leavers from one HR source. Then the logic sits in attribute mappings you can read and carry to another tool, instead of in scripts nobody wrote down.
- 02Model roles as data
Keep role definitions and their owners in a list you can export. Entra models roles as access packages, and SailPoint and Saviynt both import role data, so a clean list moves with you.
- 03Prefer standard connectors
Use SCIM or the vendor's standard connector before writing custom code. Every custom connector is something you rebuild or re-test at the next upgrade.
- 04Write SoD rules in plain words first
Agree each conflict with finance in a spreadsheet before encoding it. The rule set then survives a change of tool, and auditors can read it.
- 05Keep review evidence outside the tool
Export certification results to your own storage after each campaign. If you switch platforms mid-year, the audit trail doesn't go with the old licence.
Before: governance split across scripts, MIM and spreadsheets
HR changes reach some systems through MIM and scripts. On-premises groups and SAP roles are reviewed in spreadsheets, and someone reconciles them by hand before each audit.
After: one governance platform fed by HR and wired to every target
HR drives joiners, movers and leavers through one governance platform. It provisions to Entra, Active Directory, SAP and SaaS apps, runs the reviews, and checks SoD rules when access is requested.
If the project goes wrong
If the rollout stalls or the pick turns out wrong
Use this when go-live slips, connectors don't behave, or an audit finds gaps after the switch. The aim is to keep access reviews and leaver processing working while you fix it.
- 01Stabilisefirst week
- Keep the old tool or process running for leavers until the new one has handled a full month without misses.
- Freeze new app onboarding and fix the waves already live first.
- 02Find the causefirst two weeks
- Sort open issues into connector, HR data, role design and licence gaps. Each one has a different owner.
- Check whether the stuck apps are the ones the pilot skipped. If they are, re-test them with the vendor.
- 03Cover the auditbefore the next review
- Run any overdue certification manually from exported data so there's no gap in evidence.
- Tell the auditors what changed before they find it. Show them the compensating control in writing.
- 04Decidethis quarter
- Choose between fixing in place, adding a second tool for the gap (often on-premises or SAP), or switching.
- When you price a switch, start from the apps, roles and rules you'd rebuild. Add the licence after that.
- 05Learnafter recovery
- Add the apps that broke to the next vendor pilot, so the same gap can't hide twice.
- Write up which assumption failed and keep it with the decision record.
What this looks like in typical estates
Three typical situations
- the setup
- A mid-size insurer runs Microsoft 365 and Entra ID P1, with MIM provisioning to Active Directory and two SQL-based apps. Most other apps use Entra single sign-on.
- what happens
- Entra ID Governance covers the cloud apps quickly. Access reviews on AD-synced groups show results that can't be applied, and the MIM connectors for the SQL apps need moving to the ECMA Connector Host.
- what to do
- Move scenarios one at a time per Microsoft's guide. Plan to convert key AD groups to cloud groups or handle their clean-up in AD, and keep MIM for anything not yet moved.
- the setup
- A manufacturer runs IdentityIQ 8.4 with years of custom rules, plus SAP ECC and S/4HANA with finance separation-of-duties rules checked at request time.
- what happens
- The team weighs IdentityIQ 9.0, SailPoint's cloud and Saviynt. Each cloud option means rebuilding custom rules, and the SoD rules have to keep working on day one.
- what to do
- Count custom rules and plugins first, then run free assessments from both vendors. Pilot the SAP SoD checks on real role combinations before choosing.
- the setup
- A contractor that supports civilian agencies has Entra ID in a government cloud and needs governance for about 40 apps, some on-premises.
- what happens
- Entra ID Governance is available in its cloud. A dedicated tool would need the right FedRAMP level, and one vendor's High listing still shows no agency authorizations.
- what to do
- Confirm the authorization level each contract requires, then compare Entra alone with Entra plus a FedRAMP-authorized IGA for the on-premises apps.
How Cohash helps
We start with your application list and audit scope, then tell you plainly which tool fits and where you'd need a second one. Our identity engineers work on SailPoint, Saviynt and Microsoft Entra, including IdentityIQ upgrades and moves off MIM. Read about our identity governance practice, or start with an assessment.
What to take from this
- 01
Start from your app list. Where each app signs in, and how much is on-premises or SAP, decides most of this.
- 02
Entra ID Governance fits Microsoft-first estates. It can't apply review results to groups still managed in AD, and deeper SoD needs a partner tool.
- 03
SailPoint has a big connector catalogue and still sells an on-premises product. Practitioners describe moving IdentityIQ custom code to the cloud as a rebuild.
- 04
Saviynt puts IGA, ERP access rules and PAM in one SaaS platform. Test the PAM side on its own merits.
- 05
Get quotes for every identity in scope, guests and agents too. Then pilot on the apps that usually break things.
01Is Entra ID Governance enough, or do we still need SailPoint or Saviynt?
If most of your in-scope apps sign in through Entra and you have little on-premises or SAP, Entra ID Governance is often enough. Teams with many AD-guarded file shares, heavy SAP rules or apps without modern APIs usually add a dedicated IGA tool for that part.
02How much does Entra ID Governance cost?
Microsoft lists it at $7 per user per month, paid yearly, and it sits on top of Entra ID P1. P2 tenants can buy a separate Step Up product, so ask for that price. You need enough licences for every member user in scope. Guests are billed separately, per month, when a Governance-only feature acts on them, and governing AI agents needs Microsoft 365 E7 or Agent 365.
03How much do SailPoint and Saviynt cost?
Neither publishes prices. SailPoint sells Standard, Agentic Business and Agentic Business Plus suites, and Saviynt sells Essentials, Pro and Premium priced by the number and types of identities. Get quotes against the same identity count and app list so they compare fairly.
04Should we upgrade to IdentityIQ 9.0 or move to SailPoint's cloud?
It depends on how much custom code you run and whether you can move to SaaS at all. SailPoint describes 9.0 as a longer runway for on-premises customers, and offers a free assessment for the cloud move. Count your rules and plugins first, because that number drives the effort either way.
05Can we move from SailPoint IdentityIQ to Saviynt, and how much carries over?
Yes. Saviynt's Migration Workbench reads IdentityIQ and Oracle Identity Manager configuration and maps what it can. Saviynt says 60 to 70 percent of objects usually map directly, so plan manual work for the rest.
06Which of the three is FedRAMP authorized?
SailPoint Identity Security Cloud and Saviynt's Enterprise Identity Cloud hold FedRAMP Moderate. Saviynt's High listing shows it as FedRAMP Certified, with no certification date and no agency authorizations as of October 2026. Entra ID Governance runs in Microsoft's GCC, GCC High and DoD clouds. Check what your contract asks for, then get each vendor's status in writing.
Three questions, about a minute
Pick an answer and we'll tell you if it's right, and why it is or isn't. The score stays in this browser.
-
Q1An Entra access review says a user should lose a group that's synced from on-premises AD. What actually happens in AD?
show the answer
B. Nothing changes in AD; someone has to apply the result there Entra can't manage a group that comes from on-premises AD, so the result isn't applied. You download the results and change the group in AD yourself.
-
Q2Your IdentityIQ install has hundreds of custom rules and several plugins. Which cost will probably dominate a move to SailPoint's cloud?
show the answer
B. Redoing custom logic as workflows and API calls, rule by rule Forum members report that plugins aren't supported in the cloud and far fewer rule types exist, so custom logic gets redesigned. Practitioners call that the biggest piece of the move.
-
Q3Finance wants SAP access checked for conflicts before anyone gets it. Which of these matches the vendor docs?
show the answer
C. Saviynt has SoD rulesets for SAP, Workday and Oracle out of the box Look in Saviynt's Application Access Governance and you'll find rulesets for SAP, Workday and Oracle already built. Entra marks access packages incompatible on its own and relies on SAP or partner tools for finer rules. SailPoint has you write policies, up to 500 per tenant.