> ## Documentation Index
> Fetch the complete documentation index at: https://oximy.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect provider, application, agent-runtime, and developer data to Oximy.

Integrations bring official account, seat, usage, billing, model, and runtime data into the shared platform.

## Integration families

<AccordionGroup>
  <Accordion title="Employee AI applications" icon="users" defaultOpen>
    Oximy includes connection flows for Microsoft 365 Copilot, GitHub Copilot, Cursor, Codex and ChatGPT Enterprise, and Claude usage.
  </Accordion>

  <Accordion title="Microsoft agent platforms" icon="bot">
    Agent integrations cover Microsoft Copilot Studio, Azure AI Foundry, and Microsoft 365 declarative agents.
  </Accordion>

  <Accordion title="Custom agent runtimes" icon="activity">
    OpenTelemetry ingestion connects runtime traces from supported custom agent platforms.
  </Accordion>

  <Accordion title="Sidekick tools" icon="plug">
    Sidekick connectors and MCP servers give threads controlled access to company systems. These execution integrations are governed separately from Visibility data integrations.
  </Accordion>
</AccordionGroup>

## Connection lifecycle

<Steps>
  <Step title="Authorize the source">
    An administrator supplies the provider-specific credentials or completes the relevant authorization flow.
  </Step>

  <Step title="Verify access">
    Oximy checks the connection and records its current status.
  </Step>

  <Step title="Synchronize data">
    The integration imports the source data available through the granted permissions.
  </Step>

  <Step title="Resolve identity">
    Provider accounts and principals are connected to people, agents, applications, and departments through the identity graph.
  </Step>
</Steps>

<Info>
  Integration availability depends on the selected products, deployment, provider configuration, and permissions granted by the customer.
</Info>