> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/getting-started/chat-and-alerts/send-alerts-to-private-microsoft-teams-channels.md).
# Send Alerts to Private Microsoft Teams Channels
Because Microsoft Teams apps can't be member of a private Teams channel, additional setup is required to send alerts to a private channel. The reason for this is a technical limitation in Microsoft Teams that exists since several years and was not solved until now. In some cases it might be easier to create a new MS Team instead, and only allow authorized people access to this team. Please note that alerts in private channels will be sent as the user who has performed the setup steps and not as Aikido.
***
Follow these steps to send alerts to a private Microsoft Teams channel:
{% stepper %}
{% step %}
**Install the Aikido app**
If not already done, follow the steps described on this page: [Microsoft Teams Notifications](/getting-started/chat-and-alerts/ms-teams-notifications.md)
{% endstep %}
{% step %}
**Create the Workflow**
Select the private channel that should receive the alerts, click on "More Options" (the three dots) and select "Workflows".
Search for and select **"Send webhook alerts to a channel"**. After that select the Microsoft Team and the private channel where the alerts should be sent. Finish the creation by clicking on "Save".
Select Microsoft Team and private channel
Copy and save the workflow URL using the copy button. You need this URL later.
{% endstep %}
{% step %}
**Finish setup**
Open the Microsoft Teams integration page in the Aikido dashboard and click on "Create alert". Inside the channel select input, click on "Link a different private channel". After that the following dialog is opened. Select the Microsoft Team and enter the channel name and the workflow URL. Click on "Add Channel" to finish the setup.
Finish the connection
{% endstep %}
{% step %}
**Confirm successful setup**
After clicking on "Add Channel", you should receive the message "This channel has been successfully added to Aikido." in your private Microsoft Teams channel. If you did not receive any message, please check the following step.
{% endstep %}
{% step %}
**Edit the Workflow (Not always needed)**
{% hint style="info" %}
This step is only required if you did not receive the success message in your private channel.
{% endhint %}
The workflow is sometimes configured to send messages as the Power Automate bot, but this bot cannot send messages to private channels either.
Click on "Workflows Home" in the right bottom corner of the dialog and then on "Edit in Power Automate". Expand the "Attachment is null" section by clicking on it. Modify the "Post card in a chat or channel" action and select "User" for the "Post as" setting as shown in the following screenshot. Make sure to save your changes after that.
Modify Workflow
{% endstep %}
{% endstepper %}
---
# 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://help.aikido.dev/getting-started/chat-and-alerts/send-alerts-to-private-microsoft-teams-channels.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.
