Microsoft Teams
Post Aegis notifications as cards in a Microsoft Teams channel.
The Teams connector gives Aegis one channel to post into. You create an incoming webhook (a private web address that lets an outside service post messages into one Teams channel) in Teams, paste its address into Aegis, and test it. From then on, people who switch Teams on in their notification preferences receive their Aegis notifications as cards in that channel. There is no sign-in with a Microsoft account and no bot: the webhook address itself decides where the cards land.
At a glance
| Direction | Out of Aegis. |
|---|---|
| What it sends |
A card with a title, a message and, where the notification points at
a record, a
View Details link back into Aegis. The connector's test
sends a fixed test card.
|
| Where it lands | The Teams channel of the incoming webhook. |
| Credentials and permissions |
The channel's incoming-webhook address. Only Microsoft Teams webhook
hosts are accepted: *.webhook.office.com,
outlook.office.com/webhook, and the Azure Logic Apps
and Power Automate trigger hosts (*.logic.azure.com,
*.environment.api.powerplatform.com).
|
| Owner of imported records | Not applicable: nothing is imported. |
| When it runs | At the moment a notification is sent. |
| Set it up |
/connectors/teams, by people allowed to configure
connectors, on a plan that includes the connector.
|
Who uses it
-
Admin and
Manager open
/connectors/teams, save the webhook, send the test message and delete the configuration. -
Contributor and
Viewer cannot open the page:
the server checks the role before the page renders and sends them to the
/unauthorizedpage, which explains what happened and offers a way back. They still benefit from the connector — once it is configured, anyone can switch Teams on for their own notifications in Notifications.
What's on this screen
No screenshot of this page was captured for this edition of the guide; the description below follows the page as it is built. You reach it from the Microsoft Teams tile on Connectors.
-
Breadcrumb and header.
Connectors / Microsoft Teamsat the top, then the titleMicrosoft Teams Configurationand one line explaining that the page sends notifications through incoming webhooks. -
Status banner. Once a configuration exists, a banner reads
Status: Connected(green),Status: Error(red) orStatus: Disconnected(neutral). Before anything is saved there is no banner. -
Last recorded error. When a test has failed, a red box
headed
Last recorded errorshows the reason and when it was recorded, so a red status explains itself. -
Webhook Settings.
Incoming Webhook URL(required, marked with a red asterisk) andChannel Name (Optional). After saving, the address is hidden as dots and the hint reads “The saved webhook URL is hidden. Paste a new URL to replace it.” -
Notification Preferences. Three tick boxes, all ticked by
default:
Policy updates(new, modified or approved policies),Risk alerts(high-severity or escalated risks) andCompliance updates(coverage changes and control gaps). See “Tips and limits” below for what they do today. -
Action row.
Delete Configurationon the left (only once a configuration exists);Cancel,Send Test Message(only once a configuration exists) andSave Configurationon the right. - Setting Up Teams Webhooks. A six-step help box at the bottom that repeats the Teams-side steps below.
Create the webhook in Teams
-
In Microsoft Teams, open the channel that should receive Aegis notifications
and select the three dots (
...) next to the channel name. The channel menu opens. -
Select
Connectors. The list of available connectors appears. -
Find
Incoming Webhookand selectConfigure. Teams asks for a name and an optional image. - Give it a name your colleagues will recognise, for example “Aegis GRC”, and create it. Teams shows the webhook address; copy it.
Anyone who has the webhook address can post into that channel. Paste it only into Aegis, and do not share it in chat or email. Aegis stores it encrypted, shows it only as dots after saving, and records only its host name in its log lines.
Configure the connector
-
Open Connectors and select the Microsoft Teams
tile. The
Microsoft Teams Configurationpage opens with empty webhook fields and all three notification tick boxes ticked. -
Paste the address into
Incoming Webhook URL. Aegis checks the field is filled in and is a well-formed address when you save; an empty field shows “Teams Webhook URL is required” and a malformed one shows “Invalid URL format”. -
Optionally enter a
Channel Name, such as#grc-alerts. It is a label for your own reference only; the webhook already decides the channel. - Leave the notification tick boxes as they are, or clear the ones you do not want recorded with the configuration.
-
Select
Save Configuration. The button readsSaving..., then a green note reads “Configuration saved. Send a test message to verify the connection.” The status banner appears, andSend Test MessageandDelete Configurationbecome available.
A new or changed configuration is stored as Disconnected. Only
a successful test moves it to Connected. Saving the same
settings again keeps an existing Connected status.
Send a test message
-
Select
Send Test Message. The button readsSending...while Aegis posts a card titled “Aegis GRC - Test Message” to the channel, with the status and a timestamp. -
On success a green note reads “Test message sent to Teams”, the banner
changes to
Status: Connected, and the card appears in the Teams channel. -
On failure a red note gives a fixed reason, the banner changes to
Status: Error, and theLast recorded errorbox shows the same reason without a page reload. The reasons are listed in the table below.
| Reason shown | What it means |
|---|---|
Invalid Teams webhook URL |
The address is not on one of the accepted Microsoft hosts. Aegis refuses it before sending anything. |
Teams webhook URL blocked |
Aegis's outbound protection refused the address, for example because it resolves to a private network or redirects off a Teams host. |
Teams webhook returned an error response |
Teams received the request and refused it — often because the webhook was removed or the channel was recreated. |
Failed to send Teams test message |
The request did not reach Teams, for example a network failure. |
Every test — passed, failed or blocked — is written to the audit log with its outcome and a machine-readable code, never with the webhook address or Teams's own error text.
Replace or remove the webhook
-
To point Aegis at a new webhook, paste the new address over the hidden one
and select
Save Configuration. The status returns toDisconnecteduntil you test again. Saving without touching the hidden field keeps the stored address. -
To stop posting altogether, select
Delete Configuration. A confirmation asks “Are you sure you want to delete this connector configuration?”; confirm, and Aegis removes the connector and returns you to Connectors.
Who receives cards
The connector only supplies the channel. Cards are sent from these places:
- Personal notifications. Each person decides, per notification type, whether Teams is one of their channels in Notifications. Teams notifications arrive one by one; they are never gathered into a digest.
- The regulatory change digest. When the Teams connector can deliver, the digest described in Regulatory changes is also posted to its channel.
A workflow's Send Teams Message action does not use this connector:
it takes its own webhook address in the action settings. See
Workflows.
Aegis also has an API endpoint, /api/connectors/teams/send, that
posts a card with a title, message, severity and an optional link to the
configured channel. It is there for integrations; in the current version no
screen in Aegis sends through it.
Tips and limits
- The test message tells you why a send failed with a fixed reason, for example an address outside the Teams hosts. The test accepts only the hosts real notifications use, so a green test means real cards will go through too.
-
The three tick boxes under
Notification Preferencesare saved with the configuration, but in the current version no delivery path reads them: which notifications reach Teams is decided by each person's notification preferences. Do not rely on clearing a tick box to stop a type of card. - If the Teams connector is switched off for your organisation's plan, Aegis stops posting to the stored webhook, the test returns an access error, and the Teams channel stops being offered in notification preferences.
- If Teams recreates the channel or the webhook is removed, the old address stops working and sends fail. Create a new webhook, paste it in, save and test.
- One Teams channel per Aegis organisation: the connector holds a single webhook address.
- Card text is escaped before it is sent, so record titles containing Markdown or special characters appear as written rather than changing the card's formatting.
Where this connects
- Connectors — the catalogue and status of every connector.
- Notifications — switch Teams on or off per notification type; notification preferences are also reachable from Settings.
- Regulatory changes — the digest that also posts to Teams.
-
Workflows — the
Send Teams Messageaction with its own webhook address. - Slack — the equivalent connector for Slack.