Microsoft Teams is a core tool for daily collaboration across teams. Cutover’s enhanced integration makes it even easier to stay aligned during runbook execution.
Using the Microsoft Graph API, Cutover can dynamically search for and select the right Teams channel or existing chat based on the authenticated user’s access. This ensures a smoother setup experience when configuring Teams actions within a runbook.
Authentication is handled securely via Microsoft’s recommended OAuth2 flow, ensuring compliance and security from start to finish.
Once integrated, you can use Integration Actions in your runbook to send messages directly to:
A Microsoft Teams channel
A One-on-One chat
A Group chat
Prerequisites
Before using the Microsoft Teams integration in Cutover, ensure the following conditions are met:
Authorization & Access
Your organization must already be using Microsoft Teams.
Cutover must be authorized to access Microsoft Teams information via Microsoft Graph API.
Cutover’s Delivery team must assist in setting up the required authentication information with Microsoft. Some steps may already be complete but are included here for transparency.
Note: Authorization is granted by your Microsoft tenant organization. To enable the integration, a Microsoft tenant administrator should contact a Cutover Delivery Partner for setup support.
When using the Microsoft Teams chat feature within a runbook:
The chat must already exist in Microsoft Teams.
The chat must have existing messages—empty chats cannot be found via search.
At this time, you cannot create a new chat or initiate a new One-on-One conversation from Cutover.
Even if the chat has a name in Microsoft Teams, Cutover will search by user membership within the chat, not by chat name.
Using the integration
Once your Microsoft Teams admin has completed authentication, the Cutover Delivery team will configure the integration for your workspace. This includes setting up how authentication will work based on whether the task is auto-started or manually triggered (see the section below for more details).
After setup is complete, the Microsoft Teams task types will be available for use in your runbooks.
Go to your Cutover workspace and create a new runbook.
Create a new task and open the edit panel.
You’ll now see the Microsoft Teams task types configured by the Delivery team.
There are two options to choose from, depending on your use case:
Send a message to a Microsoft Teams channel
Send a message to an existing Microsoft Teams chat
When you create the task, you’ll need to authenticate to Microsoft Teams in order to select the channel or chat the message should be delivered to. You’ll only be able to view channels or find existing chats that you have access to in MS Teams.
For Channel Messages:
Scroll to the Message section in the task edit panel.
Type your message and enter the channel name—a dropdown list of matching channels will appear.
Select the appropriate channel from the list.
For Chat Messages:
Enter your message, then choose between:
Group chat
One on One chat
Search for a user who is part of the chat. You’ll only see results for chats you’re already a member of with existing messages.
Sending the message
Once your task is set up:
Switch your runbook to Live Mode
Start the run and begin the task.
Cutover will automatically send your message to Microsoft Teams. When delivered, a green “Message sent” confirmation will appear on the right side of the task in the live run.
In Microsoft Teams, the message will appear in the chosen chat or channel—complete with a link to the corresponding Cutover runbook. Click the link to jump into the runbook and action any relevant tasks.
Task properties
When setting up an integration, further task property settings can be found within the Additional Settings area. Depending on which of the task settings are chosen when the integration is set up, the start of the integration is affected when the runbook is in live execution.
Auto start: When sending a message to a channel, it will be sent to the channel selected during the setup of the integration task. There is no manual input to start the task and the message will be posted from the person who selected the channel.
Manual start (if auto start is not selected): When auto start is not selected, the integration task must be started manually. The integration will be executed if the user who starts the task is the same as the one that selected the channel. If a different user starts the task, this user will need to authenticate with Microsoft.
The message will then be sent in the name of this user.
Important: If the user starting the task does not have the appropriate permissions to post in the channel or in a chat, the integration will fail.
