Connectors¶
The connectors screen answers two questions: what feeds your compliance controls (evidence sources) and where your alerts go (destinations). It only lists what the tenant has already configured; everything you could add instead lives in the catalog.
Who uses it¶
An admin role on the tenant configures it (a tenant admin, an organization admin, or an equivalent
write-capable role). Everyone else feels its effects indirectly — a ciso or a compliance
analyst reads the alerts these destinations deliver, without touching the configuration.
Where to find it¶
/connectors— what the tenant already has configured, with two measured figures in the header (sources observing, destinations sending) and the time they were measured./connectors/catalog— everything that can be added, searchable and filterable by category, type, and availability./connectors/catalog/<slug>/setup— the setup wizard for one specific entry.
What alert destinations exist today¶
Nine, one per destination type in the catalog,
all marked available: ServiceNow, Jira, Slack, Microsoft Teams, Email, a custom webhook, SIEM
(CEF format), PagerDuty, and Opsgenie. Each declares its own capabilities — Jira opens
remediation issues, Slack and Teams carry weekly posture summaries, the custom webhook forwards
every alert as JSON to an HTTPS endpoint you control.
What evidence sources exist today¶
Five entries appear in the catalog — Microsoft 365, AWS, Google Workspace, Azure, and Google
Cloud — but all five are marked planned, not available. The catalog describes what each would read
(Entra ID posture, CloudTrail, the Admin SDK…) and which controls it would cover, but none has a
live collector yet. It is a map of what is coming, not something you can connect today.
What decisions it enables¶
Choosing where critical alerts should land before an incident happens — Slack for the team, PagerDuty or Opsgenie for on-call, ServiceNow or Jira to open a tracked remediation task — and deciding in advance which evidence sources to expect once the matching collector ships.
Honest limits¶
- No evidence source can be connected today: they are all planned, with no collector behind them.
- The catalog is shared reference data, not tenant-isolated; what is tenant-specific — what the tenant has already configured — is always read inside that tenant's own context.
Plan¶
The connectors module is available from the Free tier onward —
it needs no higher tier. How many destinations of the same type you can hold, and which
specific alert channels (Slack, Teams, PagerDuty, Opsgenie…) you can actually use, do vary by
plan: email alerts are available on every plan, webhook, Slack and Teams alerts from Automate,
and PagerDuty and Opsgenie from Operate. Essentials includes one connector; Automate and above
have no cap on connectors.