Our services/SCIM gateway · Entra ID
Your Odoo access,driven by Entra ID.
Cellenza’s SCIM 2.0 gateway creates, updates and archives Odoo users from Microsoft Entra ID, and makes Odoo employees the HR source of Entra ID. Odoo Online included.
Microsoft Entra IDAccounts, groups and rights
SCIM 2.0
Cellenza SCIM gatewayOn Azure, multi-tenant
Odoo API
OdooUsers and employees
Automatic onboardingAccounts and rights created from Entra ID
Both directionsOdoo employees feed Entra ID
Microsoft sign-inSSO, no invitation e-mail
Controlled leaversArchived, never deleted
FEATURES
The access lifecycle,automated at last.
Six building blocks so that every employee has the right access to Odoo, on the day they join as on the day they leave.
01
Users
- Creation and updates from Entra ID
- Matching of existing Odoo accounts
- Licence cap per database
- Archived on departure, never deleted
02
Groups and rights
- Odoo rights computed from Entra ID groups
- Companies and portal access managed
- Only mapped groups are changed
- Interrupted updates completed later
03
Employees
- Employee records created and linked
- Odoo employees as the HR source of Entra ID
- Incremental and nightly synchronisation
- One master per attribute
04
Microsoft sign-in
- SSO link set automatically
- No password and no invitation e-mail
- Technical and administrator accounts protected
- Identity conflicts reported, never blocking
05
Security
- Secrets in Azure Key Vault
- Tokens stored as hashes
- Audit log of every operation
- Safeguards against mass departures
06
Operations
- Multi-tenant service on Azure
- Admin console with Microsoft sign-in
- Database diagnostics and reconciliation
- Monitoring with Application Insights
DAY TO DAY
Entra ID decides,Odoo follows.
HR and IT teams work in their usual tools, the gateway does the rest.
Joiner
The employee added in Entra ID gets an Odoo account and rights, then signs in with their Microsoft account.
Mover
A group change in Entra ID updates their rights and companies in Odoo.
Leaver
The account is archived in Odoo and history stays intact. A mass disappearance is held until confirmed.
FOR WHOM
Built for your IT,integrated with the Microsoft cloud.
Who it is for
Organisations that manage identities in Microsoft Entra ID and want to automate access to Odoo, on Odoo Online, Odoo.sh or on-premise.
Requirements
Odoo 20 Online on the Custom plan (external API), or Odoo.sh and on-premise with the dedicated module. Entra ID P1 at least, Entra ID Governance for large volumes in the return direction.
FREQUENTLY ASKED QUESTIONS
Your questions,our answers.
Can’t find your answer? A Cellenza expert replies within 24 working hours.
Ask a questionWhy a gateway rather than an Odoo module?
Odoo Online does not accept Python modules. The gateway exposes the SCIM 2.0 API to Entra ID and talks to Odoo only through its external API, with the key of a dedicated technical user. For Odoo.sh and on-premise, a dedicated module does the same job.
What happens when an employee leaves?
Nothing is ever deleted in Odoo: the account is archived and history stays intact. An empty read or a mass disappearance (more than 10 % of employees) is held until confirmed.
Do users get an Odoo password?
No. Accounts are created without an invitation e-mail and sign-in goes through Odoo’s Microsoft provider.
What are the requirements?
Odoo 20 Online on the Custom plan (for the external API), or Odoo.sh and on-premise with the dedicated module. Entra ID P1 at least, Entra ID Governance for large volumes in the return direction.
OUR OTHER SOLUTIONS
Furtherwith Odoo.
SEE IT IN A DEMO
Access granted,no tickets, nothing forgotten.
30 minutes to watch the gateway provision an Odoo database from Entra ID, with a Cellenza expert.