Mitchell Lyon

How I Route Monitoring Emails to Microsoft Teams Using Power Automate (Outlook V3)

In a corporate IT environment, email quickly becomes noise.

Monitoring systems send alerts.
Security tools send notifications.
Vendors send updates.
Ticketing systems generate threads.

Eventually, critical alerts get buried inside hundreds of automated messages.

Instead of asking engineers to “watch their inbox more carefully,” I built a simple Power Automate flow that pushes only important monitoring emails into a Microsoft Teams channel our team actively watches.

This post walks through exactly how I built it.

What This Flow Does

When a monitoring email arrives that matches specific criteria:

  • Specific folder
  • Specific sender
  • Specific subject content

Power Automate automatically posts a structured message into a designated Teams channel.

No manual forwarding.
No custom code.
No API integration.

Just clean signal routing.

Step-by-Step Instructions

Step 1: Prepare Your Outlook Folder

Before building the flow, reduce noise at the source.

  1. In Outlook, create a folder such as:
    • Monitoring Alerts
    • Prod Alerts
    • Critical Notifications
  2. Create an Outlook rule:
    • Move only high-priority monitoring emails into this folder.
    • Filter by sender and/or subject (e.g., “CRITICAL”, “SEV1”, “PROD”).

This ensures Power Automate evaluates only meaningful alerts.

Step 2: Create the Flow in Power Automate

  1. Go to:
    https://make.powerautomate.com
  2. Click:
    Create → Automated cloud flow
  3. Name the flow:
    Monitoring Emails to Teams
  4. Choose the trigger:
    When a new email arrives (V3)

Click Create.

Step 3: Configure the Outlook (V3) Trigger

This is where the filtering happens.

Folder

Set the Folder field to the monitoring folder you created earlier.

This prevents the flow from running against your entire inbox.

From

In the From field, specify the monitoring tool’s sender address.

Examples:

Subject Filter

In the Subject Filter field, add keywords that identify true alerts.

Examples:

  • CRITICAL
  • SEV1
  • PROD
  • OUTAGE

This ensures the flow triggers only on high-signal emails.

Because filtering is handled directly in the trigger, no additional condition block is required.

Step 4: Add the Microsoft Teams Action

Click New Step.

Choose:
Microsoft Teams → Post a message in a channel

Configure:

  • Team: Select your operational team
  • Channel: Choose your monitoring/alerts channel
  • Message Type: Standard

Step 5: Format the Teams Message

Instead of sending raw HTML, format the message using dynamic content fields.

Example message structure:

🚨 Monitoring AlertSubject: [Dynamic Subject]
From: [Dynamic From]
Received: [Dynamic DateTimeReceived]Preview:
[Dynamic Body Preview]Link to Email:
[Dynamic Web Link]

In Power Automate, insert these from the dynamic content panel:

  • Subject
  • From
  • Date Time Received
  • Body Preview
  • Web Link

This keeps the message readable and actionable inside Teams.

Why This Works

This approach improves alert visibility without introducing new tools.

It:

  • Reduces alert fatigue
  • Moves critical signals into your collaboration layer
  • Improves shared visibility
  • Encourages faster acknowledgment
  • Eliminates manual forwarding

Most importantly, it routes alerts to where engineers already live during incidents.

Final Thoughts

Monitoring maturity isn’t just about tooling.

It’s about signal delivery.

If your incident awareness depends on someone checking Outlook at the right moment, you don’t have reliable alerting.

You have luck.

Sometimes operational improvements aren’t about buying something new.

They’re about rerouting attention.

Leave a comment