Microsoft Teams Channel
@omadia/channel-teams
Microsoft Teams als First-Class-Channel für Omadia. Bot-Framework-Adapter, Adaptive-Card-Rendering, Roster + Mention-Resolution, Attachment-Persistenz mit HMAC-signiertem Proxy. Konsumiert den geteilten Graph-Client aus `@omadia/integration-microsoft365` für Attachment-Downloads + Roster-Lookups.
- latest
- v0.11.0
- license
- MIT
- versions
- 8
- author
- byte5 GmbH
install
In your omadia instance, open Admin → Registries and add this registry, then install Microsoft Teams Channel from Admin → Plugins → Store.
https://hub.omadia.aisetup guide
Connect Microsoft Teams
Teams runs as an Azure Bot that reuses the same Azure AD app as the Microsoft 365 integration. Install @omadia/integration-microsoft365 first — it owns the app credentials (client id / secret / tenant); this channel only adds Teams-specific knobs.
1. Register the Azure Bot
- Azure Portal → create an Azure Bot resource.
- Use the existing app registration from the Microsoft 365 integration (same Microsoft App ID).
- Configuration → Messaging endpoint:
<your-public-base-url>/api/teams/messages. - Channels → enable Microsoft Teams.
2. Upload the Teams app
Upload the Teams app package (manifest.json + icons as a ZIP) in Teams under Apps → Manage your apps → Upload a custom app.
3. Optional knobs
- OAuth Connection Name: if you add a v4 OAuth connection in the Azure
Bot Service, put its name here to enable calendar SSO (OBO flow). Empty →
calendar tools report
sso_unavailable. - Notify Team ID: the AAD groupId of the team where bell notifications
appear — get it via Teams → Team settings → Get link to team (groupId
query param) or Graph Explorer (
/teams). Empty → log-only. - Attachment prefix, topic URL and directory label have safe defaults.
versions
setup fields
Values the operator fills in at install-time.
permissions
memory
reads: [0] · writes: [0]
graph
reads: [0] · writes: [0]
network
outbound: [2]
filesystem
scratch: false