> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-teams.md).

# Export to Microsoft Teams

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Export To Microsoft Teams** node allows you to send messages to a Microsoft Teams channel from your data flow.\
It uses Microsoft Graph APIs to securely communicate with Microsoft Teams.

Microsoft Teams is a collaboration platform within Microsoft 365 that enables communication through channels and shared conversations.\
With this node, you can automatically send messages (for example notifications or updates) to a selected Teams channel.

For each row in your data, one message is sent to the configured Teams channel.

#### How it works

1. Select a valid **Connection** to Microsoft
2. Open **Advanced** to configure:
   * The **Team**
   * The **Channel**
   * The **Content column**
3. For each input row, a message is sent to the selected Teams channel
4. The original data continues unchanged

***

### Configuration Options

| Setting                                                                                                             | Required | Description                                                                                      |
| ------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------ |
| Connection                                                                                                          | Yes      | Select a Microsoft Office 365 connection or an OAuth2 connection (Microsoft Graph).              |
| Advanced                                                                                                            | Yes      | Opens a configuration screen where you select the **Team**, **Channel**, and **Content column**. |
| Within the Advanced screen, available Teams and Channels are automatically loaded based on the selected connection. |          |                                                                                                  |

***

### Team & Channel Selection

The node automatically retrieves available Teams and Channels based on your connection.

#### Teams

* Shows the teams you have access to
* You select the team where messages will be posted

#### Channels

* Shows the channels within the selected team
* You select the channel where messages will be posted

***

### Message Behavior

* Each row in your data results in **one Teams message**
* All messages are sent to the **same Team and Channel**
* The content of the message comes from the selected **Content column**

***

### Output

* The node does **not** change your data
* No extra columns are added
* The data continues to the next step in your flow

***

### Tips & Best Practices

* The connection must have permission to post messages in the selected Teams channel
* Only **plain text messages** are supported
* No formatting (HTML) is supported
* Make sure the **Content column** exists and contains text

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | May 28, 2026 | Initial documentation version added. |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-microsoft-teams.md?ask=<question>&goal=<user_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.