For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/integrations/microsoft-teams.md.
Docs

Microsoft Teams

Microsoft Teams connects Flezise to your tenant so the builder agent can receive tasks through @mentions in channels and chats, post replies in the originating conversation, and send approval and escalation alerts to a conversation ID you specify.

Note

Microsoft Teams requires a feature flag enabled on your Flezise installation. If the provider card shows a lock icon, contact your administrator.

The Microsoft Teams integration detail page: Connect with token button, Inbound events card, and Write-back card with notification target field

Connect

Teams connects through an Azure Active Directory app registration. Go to Project Settings → Integrations → Microsoft Teams, press Connect, and supply the credentials from your Azure app:

FieldValue
Tenant IDYour Azure AD tenant ID (a UUID)
Client IDThe application (client) ID of the registered app
Client SecretA client secret generated for that app

If OAuth is available on your deployment, press Connect instead of Connect with token. The OAuth flow requests these Microsoft identity scopes from your tenant:

ScopePurpose
offline_accessObtain a refresh token for long-lived access
ChannelMessage.Read.AllRead messages in channels where the app is installed
Chat.ReadRead messages in direct and group chats

Inbound event delivery uses the Microsoft Graph notification API. The platform performs a validationToken handshake when you register the subscription; the clientState value in each notification is checked against the connection to verify authenticity.

Capabilities

CapabilityWhat Flezise does
WebhooksReceives Graph change notifications and validates them with clientState
ReplyPosts replies in the channel or chat where the mention arrived

Configuration

The Write-back card controls what the builder agent sends back to Teams after each event.

Auto-respond to tickets is on by default. The builder agent posts a reply in the originating conversation and includes the pull-request link once work is done. Each reply uses credits.

Approval and escalation notifications is off by default. Enable it and a Notification target (channel/conversation ID) field appears. Enter the Teams conversation ID where the platform should post pending-approval and escalation messages.

The Inbound events card carries an Allow work-item triggers toggle. Enable it to allow events from Teams to create work items, subject to the project automation policy.

Events

EventWhen it fires
chatMessage.createdA message is posted in a monitored channel or chat

Received events pass through the classifier. If the automation policy allows it and Allow work-item triggers is on, a work item is created and agent triage begins.

Next steps