Microsoft Power Automate is a low-code application that connects Microsoft and third-party applications to automate repetitive work. Flows can handle tasks ranging from creating and updating records to sending emails, populating spreadsheets, and managing Microsoft Teams. Flows can be relatively simple or become much more complex depending on the process you’re trying to automate. In this Fast Class, we’ll walk through three examples of Microsoft Teams tasks you can automate with Power Automate.

Microsoft Teams actions and triggers in Power Automate

A Power Automate flow typically starts with a trigger, or an event that tells the flow when it should run. After that trigger occurs, the flow performs one or more actions. Microsoft Teams offers a variety of actions in Power Automate. For example, you can:

• Create a team.
• Create a channel.
• Post a message in a chat or channel.
• Add members to a team.

You can combine those actions with events happening elsewhere in your Microsoft environment. For example, when something important changes on an account record in CRM, a flow could automatically post a message to a Teams channel. Teams also provides triggers that can start flows based on activity within Teams. These include:

• When you’re mentioned in a channel.
• When a new team member is added.
• When certain keywords are mentioned.
• When a new channel message is added.

These triggers and actions give you plenty of opportunities to reduce manual work. Let’s look at three examples.

Scenario 1: Create a team when a new customer is added to CRM

If your organization creates a Microsoft Team for every customer, creating those teams manually can become repetitive. Instead, you can build a flow that automatically creates the appropriate team whenever a new account is created in CRM. The flow starts with a Dataverse trigger for when a row is added, modified, or deleted. For this scenario, the change type is set to Added and the table is Accounts. Next, add the Microsoft Teams Create a team action. Rather than entering the team name manually, you can use dynamic content from the CRM account record. The new account’s name becomes the name of the new Microsoft Team. You can also configure details such as:

• The team's description.
• Whether the team should be public or private.
• Who should become a member or owner of the team.

In this example, the customer team is private so that only the people who need access can see it.

Automatically add the account owner

Creating the team is only part of the process. We also want the owner of the CRM account to become a member and owner of the new Microsoft Team. To add someone to a team, the flow needs the user's principal name, which in this scenario is retrieved from the user's CRM record. The flow uses the Get a row by ID action to retrieve the account owner's user record. Once the user's email information is available, the Microsoft Teams Add a member to a team action can add that individual to the newly created team. Dynamic content from the Create a team step provides the ID of the new team, so the flow knows exactly where the user should be added. The account owner can also be made an owner of the team so they can manage it and add additional members later. After saving the flow, creating a new CRM account triggers the automation. The result is a new customer team in Microsoft Teams without someone needing to create it manually.

Scenario 2: Get notified about important project communication

For our second example, imagine you're working on an important project with its own dedicated Teams channel. You don't want important communication to get lost, so you'd like to receive an email every time someone posts a new message in that channel. For this flow, use the Microsoft Teams trigger When a new channel message is added. Select the specific team and channel you want to monitor. The flow then sends an email containing information from the Teams message, including:

• The time the message was sent.
• The content of the message.

You can also mark the email as high importance so that it stands out in your inbox. If desired, you can take the flow further by formatting the date and time or adjusting the email content to fit your needs. This automation gives you another way to monitor a high-priority Teams channel without having to repeatedly open Teams and check for new messages.

Scenario 3: Create a list of teams for periodic cleanup

Over time, organizations can accumulate a large number of teams in Microsoft Teams. Some stay active, while others may belong to finished projects, old initiatives, or groups that are no longer being used. Reviewing those teams periodically can help keep your Microsoft Teams environment organized.

For this example, we'll create a flow that handles part of that cleanup process by producing a list of existing teams. The flow starts with a manual trigger, so you can run it whenever you're ready to conduct a review. Next, use the List Teams action in Power Automate. This action retrieves the available teams without requiring additional information. Because the result contains multiple teams, Power Automate uses an Apply to each loop to process each one individually. For each team, the flow retrieves its URL. Including the URL makes the resulting list more useful because reviewers can quickly open a team and determine whether it still contains active communication or can potentially be removed.

Send the list of teams to Excel

The final part of the flow uses the Excel add a row into a table action. First, prepare an Excel workbook with a formatted table in OneDrive. The Power Automate flow can then add one row for each Microsoft team. Each row contains:

• The name of the team.
• The URL for the team.

In the Fast Class example, Power Automate finds 133 teams. Rather than manually finding and entering information for each one, the flow loops through all 133 and creates a corresponding row in the Excel spreadsheet. The finished spreadsheet provides management with a convenient starting point for reviewing the current Teams environment and identifying teams that may no longer be needed.

More ways to automate Microsoft Teams

These three examples only scratch the surface of what's possible with Microsoft Teams and Power Automate. Depending on your processes, you could use flows to:

• Create teams or channels for new customers and projects.
• Notify people when important information is posted.
• Monitor channels for specific activity.
• Respond when someone is mentioned.
• Trigger processes when keywords appear in Teams.
• Create periodic lists of teams for review.
• Connect Teams processes with CRM, Excel, email, and other applications.

The key is to identify repetitive work that follows a predictable process. If you're regularly performing the same steps or manually moving information between applications, there may be an opportunity to automate some or all of that work with Power Automate.