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

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.

Create the webhook in Teams

  1. 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.
  2. Select Connectors. The list of available connectors appears.
  3. Find Incoming Webhook and select Configure. Teams asks for a name and an optional image.
  4. Give it a name your colleagues will recognise, for example “Aegis GRC”, and create it. Teams shows the webhook address; copy it.
Warning: the address is the credential

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

  1. Open Connectors and select the Microsoft Teams tile. The Microsoft Teams Configuration page opens with empty webhook fields and all three notification tick boxes ticked.
  2. 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”.
  3. Optionally enter a Channel Name, such as #grc-alerts. It is a label for your own reference only; the webhook already decides the channel.
  4. Leave the notification tick boxes as they are, or clear the ones you do not want recorded with the configuration.
  5. Select Save Configuration. The button reads Saving..., then a green note reads “Configuration saved. Send a test message to verify the connection.” The status banner appears, and Send Test Message and Delete Configuration become available.
Saving is not connecting

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

  1. Select Send Test Message. The button reads Sending... while Aegis posts a card titled “Aegis GRC - Test Message” to the channel, with the status and a timestamp.
  2. 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.
  3. On failure a red note gives a fixed reason, the banner changes to Status: Error, and the Last recorded error box 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

  1. To point Aegis at a new webhook, paste the new address over the hidden one and select Save Configuration. The status returns to Disconnected until you test again. Saving without touching the hidden field keeps the stored address.
  2. 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:

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

Where this connects