Announcing Dome Managed Agents.

Try it now

Microsoft Entra ID and Dome

Entra already knows your people, and now your agents act as them. An agent sends the user's Entra access token with each call. Dome verifies it against your tenant, and rules decide on that person's app roles. Audit records the agent and the person, every time.

Dome provides verified identity andaccess control with Microsoft Entra ID.

Verified against your tenant

Dome checks each token's signature, its issuer and its expiry. A token from another tenant fails the issuer check.

Rules read app roles

Entra puts the user's app roles in the roles claim by name, and rules match on them directly.

Groups when you need them

Security groups arrive as object IDs in the groups claim. Rules can match an ID as written.

Entra IDin three steps.

Register your tenant with Dome, put roles in your app's access token, and have the agent pass the token on. Dome needs no Entra credentials of its own.
  1. Register your tenant as a verification provider

    Use the v2.0 issuer for your tenant ID. Pin the audience to your app's client ID.

    shell
    dome verification-providers create \  --name corporate-entra \  --method oidc \  --oidc-url https://login.microsoftonline.com/<tenant-id>/v2.0 \  --oidc-expected-audience <client-id>
  2. Issue v2 tokens with roles

    Set requestedAccessTokenVersion to 2 in your app's manifest, or tokens carry the v1 issuer and are refused. Define app roles and assign them; add the groups and email claims under Token configuration if rules need them.

  3. Pass the user's token with each call

    The agent keeps its own Dome key and adds the person's access token for your app as a header.

    python
    from openai import OpenAI
    client = OpenAI(    base_url=f"{GATEWAY_URL}/v1",    api_key=DOME_AGENT_KEY,    default_headers={"X-Dome-Act-As": user_entra_token},)

A ruleon an Entra app role.

Only people with the Repo.Maintainer app role may have an agent merge a pull request. Everyone else can still use the agent for the rest.
cedar
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "github" &&  resource.tool_name == "merge_pull_request"}unless {  principal has act_as &&  principal.act_as.roles.contains("Repo.Maintainer")};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Acting for

agent release-agent · acting as a.okafor
github/merge_pull_request(owner: "acme", repo: "web", pullNumber: 482)
  1. CallerToken verified against corporate-entra
  2. RolesRepo.Maintainer
  3. RuleMerges are open to Repo.Maintainer
DecisionAllowed

Bringing it alltogether.

Connecting Microsoft Entra ID to registered agents, tools, and models in Dome completes a governed agent application.
Dome

Acting for

Microsoft Entra IDIdentity

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Common questionsabout Microsoft Entra ID.

Can Dome read Entra group names?
No. Entra puts group object IDs in the groups claim, so rules match the ID or use app roles, which arrive by name.
What happens when a user is in too many groups?
Above 200 groups, Entra leaves the groups claim out of the token. Rules on app roles keep working.
Which Entra token should the agent send?
A v2 access token issued for your own app. Tokens issued for Microsoft Graph don't verify outside Microsoft.
Does Dome need SCIM provisioning from Entra?
No. Dome has no SCIM endpoint and reads identity from each verified token as the call arrives.

More of whatDome works with.

Model

Claude Fable

Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider

Anthropic

The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server

Atlassian

The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Runtime

OpenAI Agents SDK

OpenAI Agents SDK agents with their models on the Model Broker and their MCP tools on the Tool Gateway.
Client

Claude Code

Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service

TinyFish

TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.

Talk with ourFDE team.

Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.

Identity providers for AI agents: a verified person on every call

Your identity provider already knows your people. Dome verifies that identity on every agent call, so rules and audit name the person an agent acted for.

Every agent you run, under one system of control.