Microsoft Entra ID + FleetERP
SAML and OIDC single sign-on with SCIM user provisioning.
How it works
FleetERP federates with Microsoft Entra ID (formerly Azure AD) for single sign-on, and supports SCIM so joiners, movers and leavers are provisioned and de-provisioned automatically by your IT team.
Enterprise application registration with SAML or OIDC and SCIM endpoint.
FleetERP has no commercial relationship with hardware vendors and earns nothing on devices. If you later switch away from Microsoft Entra ID, your history, reports and workflows stay exactly where they are.
What flows across
What Microsoft Entra ID data lights up in FleetERP
Integration data is not stored in a separate silo — it feeds directly into the operational modules that use it.
Microsoft Entra ID integration FAQ
Do we need to replace our Microsoft Entra ID setup to use FleetERP?
No. FleetERP is device-agnostic and does not sell hardware. Your existing Microsoft Entra ID deployment stays exactly as it is — enterprise application registration with SAML or OIDC and SCIM endpoint.
What data does FleetERP receive from Microsoft Entra ID?
SAML 2.0 and OIDC authentication; SCIM user and group provisioning; Group-to-role mapping; Conditional access enforcement.
How long does the Microsoft Entra ID integration take to set up?
Standard integrations are connected during week three of a normal 30-day rollout, alongside device onboarding. Most take a few hours of configuration rather than a project.
Communication & identity
Where alerts land and how your people sign in — on the tools your organisation already uses.
Already running Microsoft Entra ID? You're most of the way there.
Book a demo and we will show you your own device data flowing into the platform during the call.
No per-user pricing · No hardware to buy · Deploy on your VPS or ours
Prefer to write? sales@fleeterp.in