# Microsoft Teams

The Microsoft Teams integration delivers real-time notifications from Interlynk to your Teams channels via incoming webhooks.

***

## Purpose

* Receive notifications for vulnerability discoveries, policy violations, license issues, and SBOM uploads in Microsoft Teams channels.
* Route notifications by severity level.

## Webhook Setup

### Creating a Teams Incoming Webhook

1. In Microsoft Teams, navigate to the target channel.
2. Click the channel name > **Manage channel** > **Connectors** (or **Apps** > search for "Incoming Webhook").
3. Click **Configure** on the Incoming Webhook connector.
4. Enter a name (e.g., "Interlynk Notifications") and optionally upload an icon.
5. Click **Create**.
6. Copy the generated webhook URL.

### Configuring in Interlynk

1. Navigate to **Settings > Organization > Integrations**.
2. Click **Microsoft Teams**.
3. Click **Add New** to add a webhook configuration.
4. Enter:
   * **Teams Webhook URL**: The incoming webhook URL from your Teams channel.
   * **Notification Type**: Select the notification level (**All**, **Alert**, **Warning**, or **Info**).
   * **Frequency**: Currently supports **Instant** delivery.
5. Click **Save**.

You can add multiple webhook configurations for different channels or notification levels.

## Message Types

Teams notifications include the same event categories as other messaging integrations:

| Category        | Examples                                   |
| --------------- | ------------------------------------------ |
| Vulnerabilities | New critical/high vulnerability discovered |
| Licenses        | License compliance violation detected      |
| Policies        | Policy scan completed with failures        |
| Uploads         | SBOM uploaded and processed                |

Messages are formatted as adaptive cards or connector cards with:

* Event summary and severity
* Affected product and environment
* Link to the relevant Interlynk dashboard page

## Required Permissions

### Microsoft Teams

* Permission to manage connectors/webhooks in the target channel.

### Interlynk

| Permission           | Purpose                             |
| -------------------- | ----------------------------------- |
| `view_connections`   | View Teams integration settings     |
| `edit_connections`   | Add or update Teams webhooks        |
| `delete_connections` | Remove Teams webhook configurations |

## Security Notes

* Webhook URLs are encrypted at rest.
* Teams webhook URLs are secret — do not share them publicly or commit to source control.
* If a webhook URL is compromised, delete the connector in Teams and create a new one.

## Troubleshooting

| Issue                 | Cause                             | Resolution                                                             |
| --------------------- | --------------------------------- | ---------------------------------------------------------------------- |
| No messages appearing | Invalid or expired webhook URL    | Verify the webhook is still active in Teams channel settings           |
| Connector removed     | Teams admin deleted the connector | Re-create the incoming webhook in Teams and update the URL             |
| Messages delayed      | Teams webhook rate limits         | Reduce notification frequency or filter to higher-severity events only |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.interlynk.io/administration/microsoft-teams.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.