Connector
Your directory, the key to the breakdown by team.
An AI cost without an org chart stays a global number. Synced daily, your Entra ID directory attaches every expense to a team, a department, a subsidiary.
Connection through the official admin API, read-only: optidome never modifies the configuration of your tools.
What optidome measures
The data collected, as is.
| Data | Detail |
|---|---|
| Employees synced daily | Work identity, department, role, team: selected fields, reduced to the useful minimum. |
| Cost breakdown | Dashboards read by team, department or subsidiary, and dormant licenses attach to the right teams. |
| Non-destructive enrichment | An empty field on the directory side never overwrites a manual entry: your enrichments survive the daily sync. |
Setup
What to prepare.
- Who, on your side
- Someone who can create an App registration (the same one as for M365 Copilot).
- Prerequisites
- A Microsoft Entra ID tenant.
- What to provide
- The three Azure values (Client ID, Client Secret, Tenant ID), reused without re-entry if the M365 Copilot connector is already configured.
- Where to get it
- Application permission User.Read.All on the App registration, with admin consent.
Frequently asked questions
Before you start.
- Which personal data is read?
- The minimum useful for the breakdown: work identity, department, role, team. The field selection is reduced at query level, and configurable.
- And without Entra ID?
- The employee CSV import does the same thing manually: an export from your HRIS or AD is enough, and remains the enrichment channel (teams, tags).
Private beta. Access is by application, and the setup of your first connector is assisted: shared screen, until the first data lands.