> 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/pt/portal-de-administracao/settings/log-exporter/teams.md).
# Teams
## Pré-requisitos
Para ingerir logs RADIUSaaS numa **Canal do Microsoft Teams**, são necessários apenas o próprio Microsoft Teams, bem como privilégios para adicionar **conectores** ao **canal** correspondente.
## Passos de configuração
Siga estes passos para enviar logs RADIUSaaS para um **Canal do Microsoft Teams**:
1. Navegue até **Microsoft Teams**
2. Clique no **Canal** > **Mais opções** > **Gerir equipa**
3. Vá para **Aplicações**
4. Clique em **+ Obter mais aplicações**
5. Procure por "**Incoming Webhook**"
6. Clique em **Adicionar** depois **Adicionar a uma equipa**
7. Selecione a sua equipa
8. Clique em **Configurar um conector**
9. Forneça um **Nome** para o conector
10. Carregar um logótipo
11. Clique em **Criar** para gerar o **URL do Conector Webhook**
{% hint style="warning" %}
Certifique-se de que copia o URL.
{% endhint %}
Agora é hora de configurar o destino de exportação no Log Exporter.
* Navegue até ao seu **RADIUSaaS Admin Portal > Log Exporter**
* Clique em **+ Adicionar** > **Teams**
* Forneça um **Nome** e **Descrição**
* Configure o **Message Filters** adaptado às suas necessidades
* Cole o **URL do Conector Webhook** no campo **URL do Webhook do canal do Teams**
* Configure o **Mensagem** a ser enviado para o seu canal do Microsoft Teams
---
# 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/pt/portal-de-administracao/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.
