> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/admin-portal/settings/log-exporter/teams.md).
# Teams
## Prerequisites
To ingest RADIUSaaS logs into a **Microsoft Teams Channel**, only Microsoft Teams itself as well as privileges to add **connectors** to the relevant **channel** are required.
## Configuration steps
Follow those steps to push RADIUSaaS logs to a **Microsoft Teams Channel**:
1. Navigate to **Microsoft Teams**
2. Click on the **Channel** > **More options** > **Manage team**
3. Go to **Apps**
4. Click **+ Get more apps**
5. Search for "**Incoming Webhook**"
6. Click **Add** then **Add to a team**
7. Select your team
8. Click **Set up a connector**
9. Provide a **Name** for the connector
10. Upload a logo
11. Click **Create** to generate the **Webhook Connector URL**
{% hint style="warning" %}
Make sure you copy the Url.
{% endhint %}
Now it is time to configure the export target in the Log Exporter.
* Navigate to your **RADIUSaaS Admin Portal > Log Exporter**
* Click **+ Add** > **Teams**
* Provide a **Name** and **Description**
* Configure the **Message Filters** to your needs
* Paste the **Webhook Connector URL** in the field **Teams channel Webhook URL**
* Configure the **Message** to be sent to your Microsoft Teams Channel
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.radiusaas.com/admin-portal/settings/log-exporter/teams.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
