For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
The Microsoft Teams connector is part of the Integration Hub. It posts the notification types you choose to one Teams channel, so a team sees new reviews, decisions and alerts where it already talks.
What it does
- One post per event. A Coverbase notification can go to several people. The channel gets it once, however many recipients it had.
- An Adaptive Card. Each post carries the notification’s title, its text (shortened past 2,000 characters) and, when the notification links somewhere, a button that opens the record in Coverbase.
- Never in the way. If Teams is unreachable or rejects a post, the notification still reaches its recipients in Coverbase and by email.
Authentication
The connector posts to a webhook URL that you create in Teams. The URL is itself the credential: anyone who holds it can post to the channel. Coverbase stores it in a secrets manager and only ever shows its host.- In the Teams channel, create a Workflows webhook (the “Post to a channel when a webhook request is received” template), or a legacy incoming webhook connector.
- Copy the URL. Coverbase accepts HTTPS URLs on
webhook.office.com,logic.azure.comandenvironment.api.powerplatform.comhosts only.
Set up in Coverbase
- Open Configuration → External Integrations, click Microsoft Teams, and click Channel notifications at the bottom of the dialog.
- On the connection’s Channel tab, paste the Webhook URL.
- Under Notification Types, choose which notifications post. Each one posts once to the channel, whoever it was for.
- Click Save, then Send test message and check the channel.
Register the bot
Chats, Coverbase AI and approval cards need a bot registered in your own Azure tenant. A bot alone is enough: the channel webhook above is only for notifications. Open Configuration → External Integrations and click Microsoft Teams. The dialog is a checklist that checks each step for you:- Register a bot in Azure. In the Azure portal, create an Azure Bot. For the type of app choose Single Tenant, and let Azure create a new Microsoft App ID. In the bot’s Configuration, copy the Microsoft App ID and the App Tenant ID. Under Manage Password, create a client secret and copy its value. Enter all three in the dialog and click Save and verify. Coverbase checks them with Microsoft and stores nothing if Microsoft refuses them, so a typo never replaces a working bot.
- Point the bot at Coverbase. Copy the Messaging endpoint the dialog shows. In Azure, paste it into the bot’s Configuration and save. Under Channels, add Microsoft Teams and accept the terms.
- Add the app to Teams. Click Download app package to get
coverbase-teams-app.zip. It is built for your bot’s app ID, so it only works for your organization. A Teams admin uploads it in the Teams admin center under Teams apps → Manage apps → Upload new app, and allows it in your app permission policies if they block custom apps. Steps 2 and 3 check off when Microsoft first calls Coverbase, which happens when someone adds the app. - Choose what people can use. Turn on Vendor requests, Coverbase AI and Approval cards.
- Try it in Teams. Click Open in Teams and send the bot a message. The dialog shows Teams is live within a few seconds.
Chats with the bot
Someone who adds Coverbase from Apps in Teams gets a welcome message listing what it can do.
The bot answers only people whose Microsoft address belongs to an active member of your organization, and they act with their own Coverbase permissions. Once Teams is live, Copy announcement in the dialog gives you a ready-to-post message for your team.
The Approval Cards status is Live, Needs the bot (approvals on but no app ID and secret, so cards post without buttons), Needs a channel, or Off.
Deciding from a card
- You act as yourself. The first time someone presses a button, Coverbase looks them up in Microsoft’s roster for the conversation and matches the address to an active member of your organization. They then decide with their own Coverbase permissions, so a person who cannot decide in the dashboard cannot decide in Teams. Nothing on the card identifies anyone.
- A press counts once. If Teams delivers a press twice, it is recorded once. A press on a card someone already decided reports it as decided.
- A card is tied to what it showed. If the disposition was revised or the acceptance chain moved on after the card was posted, the press is refused rather than applied to a decision the presser never saw.
- Decline needs a reason. Declining a Front Door sign-off does what Decline does in Coverbase: the disposition goes back to the TPRM Office as a draft, both sign-offs clear, the reason goes on the audit trail, and the person who recorded the disposition, the TPRM Office group and the requester are notified. Declining an acceptance step records remediation or rejection. Returning exit evidence reopens the step for its owner.
- One card per event, kept current. A Front Door card posts once for both sign-off groups. When someone presses a button, the card is replaced with the outcome. When someone signs off or declines in Coverbase instead, the card is replaced too. It then shows who signed and which group is still waiting, the decided disposition once both groups have signed, or who declined and why.
- An outage never loses a notification. If approvals are off, the bot is not in a channel, or a post fails, the plain card goes out instead.

The Approvals tab on the Microsoft Teams connection: every button press, who pressed it, and what it did.
Related
Email and notifications
The notifications you can choose from.
Slack
The Slack app.
Integration Hub guide
Connecting and pausing a connection.
Webhooks
Sending structured events to your own systems instead.