Evaluate your JML scenarios against Microsoft Entra ID Governance native capabilities. Find out what's covered natively, what needs a custom extension, and what falls outside scope — in under 5 minutes.
01 Scenario Inventory
→
02 Topology & HR
→
03 Worker Types
→
04 Coverage Report
Step 1 of 4 — JML Scenarios
Which JML scenarios do you need to automate?
Select all that apply to your organisation. This determines which Lifecycle Workflow templates are relevant.
Select at least one scenario to continue
Step 2 of 4 — Identity Topology & HR System
What is your identity topology?
This determines which tasks require additional infrastructure (e.g. Provisioning Agent) and what limitations apply.
☁️
Cloud-only
All identities live in Microsoft Entra ID only. No on-premises Active Directory.
🔗
Hybrid (AD + Entra Connect)
Users synced from on-premises AD via Entra Connect Sync or Cloud Sync.
🌲
Multi-forest AD
Multiple on-premises AD forests synced to a single Entra ID tenant.
⚡
Mixed (some cloud, some AD)
Combination of cloud-only and hybrid users in the same tenant.
What is your HR system?
Native connectors exist for some HR systems. Others require API-driven provisioning or custom integration.
🏢
Workday
Native connector. Inbound provisioning to AD and/or Entra ID. Email/UPN writeback supported.
📊
SAP SuccessFactors
Native connector via Employee Central OData API. Email/UPN writeback supported.
🔷
SAP HCM (on-premises)
No direct connector. Requires SAP Integration Suite bridge or API-driven provisioning.
🔴
Oracle HCM / PeopleSoft
API-driven inbound provisioning. Oracle can push via HTTP or scheduled CSV extract.
🔀
Multiple HR systems
Different HR systems for different worker populations (e.g. FTE vs contractors).
📝
No central HR system
Manual process today, or HR data in spreadsheets / ticketing systems.
Step 3 of 4 — Worker Types & Requirements
Which worker types are in scope?
Select all populations your JML process must cover. Each adds complexity to the coverage assessment.
Any of these additional requirements?
These requirements influence whether native tasks cover your scenario or custom extensions are needed.
HR writeback requirements
In an HR-driven model, the HR system is the system of record — but identity provisioning generates attributes the HR record doesn't know about. Which of the following need to flow back from Entra ID to your HR system to keep records accurate and complete?
💡 Why writeback matters: When an admin assigns a phone number in Entra or a licence is provisioned, the HR record becomes stale immediately. Without writeback, HR administrators work with incomplete data — leading to inaccurate org directories, wrong emergency contacts, and broken cost-centre chargeback. A complete HR-driven JML strategy treats writeback as a first-class requirement, not an afterthought.
