Microsoft Teams
Microsoft·AE_HSc_MicrosoftTeamsConnectorGuide
Overview
The Microsoft Teams connector integrates AlertEnterprise's Guardian platform with Microsoft Teams for real-time chat notifications driven by Guardian workflows — most notably visitor check-in / check-out notifications to hosts, escorts, and visit requestors.
Architecturally distinctive: the connector is built on Microsoft Bot Framework, not the Graph API. AE provisions a registered AE Guardian Teams Bot in the customer's Azure tenant; the bot is the communication bridge between Guardian-side workflow events and Teams-side chat delivery.
Topology: Guardian Platform → Alert Microsoft Teams Connector → AE Guardian Teams Bot (Bot Framework) → Microsoft Teams.
Architecture
Composed from this connector's actors + edges. Trust zones are color-coded; trust crossings render as thicker lines.
Authentication
1 method supported
The AE Guardian Teams Bot is registered as an Azure AD application in the customer's tenant. Authentication uses OAuth 2.0 client credentials against Microsoft's Bot Framework. The bot must be granted the appropriate Teams app permissions and installed in the relevant Teams.
Prerequisites
Everything that must be in place for this connector to work, with the owner who's responsible.
Azure AD tenant + Bot Framework registration
customerCustomer's Azure AD tenant where the AE Guardian Teams Bot is registered as an application. Bot Framework requires explicit registration in Azure.
Teams app installed in target Teams
customerThe AE Guardian Teams Bot must be installed in the Teams channels / chats it will message into. Customer Teams admin must approve installation.
Configured directory mapping (host email → Teams user)
customerGuardian's visitor workflow needs to map visit host / escort email addresses to Teams user identities. Standard via Azure AD / Entra ID directory.
Known limitations
Documented constraints to set customer expectations before deployment.
Outbound chat only (today)
informationalThe connector documents Send Chat Message only — no documented inbound flow (Teams → Guardian) at present.
Data fields
1 field mapped between AE Guardian and the vendor system.
| AE field | Vendor field | Description | Direction | Required |
|---|---|---|---|---|
| Chat Message | Teams Chat Message (Bot Framework) | Outbound chat messages — recipient (host / escort / requestor), body, optional adaptive-card content. | outbound | yes |
- src/connectors/microsoft-teams/source.pdf — p7 — Chapter 2, Connector Architecture
- src/connectors/microsoft-teams/source.pdf — p15 — Chapter 5, Register AE Guardian Teams Bot