Discovery Sources overview

Agents reach your organization in more ways than the gateway sees: a developer's coding agent spends tokens on a personal setup, and an app registration in your directory holds a secret nobody has reviewed. Discovery Sources connects the systems that already know about these agents, so they show up in Agent Authority before you put any of them behind a gateway.

In the console, Setup › Discovery Sources has one tab for each kind of source.

Agent TelemetryCopy Anchor Link

Coding agents such as Claude Code, Codex, GitHub Copilot, and Gemini CLI send OpenTelemetry data about their model usage: tokens, sessions, and requests. Point that telemetry at the gateway with an ingest key, and it feeds the per-user and per-model token trends in LLM analytics and the Cost and adoption page.

Start with Telemetry (OpenTelemetry), then follow the page for each agent you run. Managing ingest keys needs the manage_ingest_keys permission.

NHI SourcesCopy Anchor Link

A non-human identity (NHI) is any identity that software signs in with instead of a person, such as an app registration or an agent identity. Connect a directory, and SecureAuth reads its non-human identities every hour without changing anything. What it finds lands in two places: risky identities on the Findings tab of Anomalies and Findings, and the directory's agents on the NHI Agents tab of Agents & NHIs.

Microsoft Entra is the provider today. See Microsoft Entra to connect a tenant, and Non-human identities for what the findings mean. Viewing NHI tabs needs the view_nhi permission, and connecting a source needs manage_nhi.

Next stepsCopy Anchor Link

You now know which source answers which question: telemetry for what coding agents spend, a directory for which identities agents hold. Connect the one you need first, then review what it reports on the screen named above.

• Telemetry (OpenTelemetry) – create an ingest key and connect a coding agent
• Microsoft Entra – connect a tenant as an NHI source