# Integrations

> The Microsoft, Jamf, cloud and alerting integrations in Holistic AI EndLayer, what each one adds, the credential it needs, and what is planned next.

The Layer 1 Agent sees the device. Integrations in Holistic AI EndLayer, the Guardian Agent Platform, see what a device cannot: managed devices that never enrolled, the people behind them, and AI that runs in your cloud accounts and Microsoft tenant. Each reads **your own** account, with a credential you provide, and each one is optional.

## Microsoft Intune and Entra ID

For most organisations this is the first integration to set up, because it gives a number before a single device is enrolled: **how many devices you manage that EndLayer cannot yet see.**

| Feature | What it gives you |
|---|---|
| **The inventory gap** | Your Intune records set against what has enrolled, by operating system and ownership, with Defender's threat state per device |
| **Rollout from the console** | Pick Entra device groups and push the agent, with no script to copy. The result is read back per device. |
| **Fleet lifecycle** | Update, uninstall or reinstall the agent by group, or for one device |
| **The directory** | Devices matched to people and departments, and leaver alerts when a disabled account's device still reports |
| **App access** | Each application your tenant has granted access, ranked by what it could reach |
| **Phones and tablets** | Listed from Intune alongside computers |

**Connecting:** sign in with Microsoft, or use your own app registration. Granting the permissions needs an administrator with rights to give tenant-wide consent; if that is somebody else, the console creates a consent link you can send them. Each permission is checked on its own, and a figure a missing permission hides reads "not available", never zero.

Intune reaches Windows computers and Macs. Windows Server and Linux use the [fleet rollout](https://www.endlayer.ai/docs/deployment), so a mixed fleet usually uses both.

## Device management

| Integration | What it adds |
|---|---|
| **Jamf** | Your Macs as Jamf holds them, and pushing the agent and both macOS profiles to computer groups |
| **SCCM** | Packages for rolling the agent out to Windows devices |

## Microsoft AI

| Integration | What it adds |
|---|---|
| **Microsoft 365 Copilot** | Seats against use, and each licensed person's prompts checked against your DLP policy, kept only as counts |
| **Copilot Studio** | Your agents, their owners and access; runtime protection before tool calls; tool-description scanning; and drift when an agent changes |
| **Agent 365** | Your tenant's agent registry, across vendors |
| **Microsoft Foundry** | Deployments, content filters, access, usage and cost, read-only |
| **Defender and Purview** | Their security and DLP alerts, on the Events page |

## Cloud

| Integration | What it adds |
|---|---|
| **Google Cloud and Vertex AI** | Model deployments and agents, graded for exposure, with the option to stop one |
| **Amazon Bedrock AgentCore** | Runtimes and gateways, their posture and activity, runtime protection for gateway tool calls, and drift. Connected through a role you create in your account. |

## Alerts and workflow

| Integration | What it does |
|---|---|
| **Slack** | Risk alerts to a channel, the weekly Briefing, and a direct message to each person about their own devices |
| **Microsoft Teams** | Alert cards in a channel |
| **ServiceNow** | Both ways: EndLayer events create incidents, and ServiceNow alerts arrive as events |
| **Zscaler** | Its alerts, on the Events page |
| **Email** | Event alerts, scheduled reports and the weekly Briefing |

## Sign-in

Single sign-on works with Microsoft Entra ID, Okta, Google, and any SAML or OIDC provider.

## Switched on for your organisation on request

Some integrations are available and switched on for your organisation on request: a REST API for your organisation, an MCP server for your own agents, and billing connections for Anthropic, OpenAI and Cursor that show a vendor's own bill beside the cost EndLayer derives. Ask your account team or [contact us](https://www.endlayer.ai/contact).

## Planned

- **SIEM:** Splunk, Microsoft Sentinel and Datadog.
- **Ticketing and paging:** Jira, PagerDuty and Opsgenie.
- **Directory sync:** Okta and Google.
- **SDKs:** Python, TypeScript, Rust and Go.

The [roadmap](https://www.endlayer.ai/roadmap) lists each one.

## Disconnecting

Disconnecting an integration deletes the data copied in through it. For Intune, the scripts EndLayer created in your tenant are removed too. Enrolled devices keep reporting, because each one holds a credential of its own.

  - [Deployment](https://www.endlayer.ai/docs/deployment): Roll the agent out to one device or a fleet.
  - [Agents](https://www.endlayer.ai/agents): The AI agents EndLayer recognises.

Source: https://www.endlayer.ai/docs/connections · Updated 2026-11-20
