Enterprise chat
DJINN + Microsoft Teams
The command room for a company that does not run on Slack. Same brain, different front door.
How it connects
The same shape as Slack
Threads, channels, a long-lived connection. The work is the adapter; everything behind it is shared.
Tenant-scoped from day one
Enterprise deployments care about which tenant, which team and which retention policy — scoped during onboarding rather than retrofitted.
Connector spec
- Auth
- oauth2 · microsoft_v1
- Host
- https://graph.microsoft.com
Scopes requested
GET v1.0/teams/${source.id}/channels
Emits channel · incremental on createdDateTime · cursor pagination
Declared boundary: per record via v1.0/teams/${source.id}/members
This spec parses and validates, and it has not been run against a live Microsoft Teams account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Microsoft Teams setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupTenant app registration
- PolicyCompliance and retention scoping
Want Microsoft Teams wired into your own company brain?