Skip to content

Connect Outlook to Microsoft Teams

Keep Outlook and Microsoft Teams in step without copying records between them by hand. Autonoly watches Outlook for the events you care about and runs the matching action in Microsoft Teams — on a free plan, with no code and nothing to host.

What you can automate between Outlook and Microsoft Teams

When → Then

New email received in inbox or folder in Outlook → Send message to channel in Microsoft Teams

When → Then

Email matching search criteria arrives in Outlook → Send personal chat message in Microsoft Teams

When → Then

Calendar event created or updated in Outlook → Create interactive card in Microsoft Teams

When → Then

Meeting invitation received in Outlook → Create or update teams in Microsoft Teams

When → Then

Contact added or modified in Outlook → Upload files in Microsoft Teams

When → Then

Out-of-office status changed in Outlook → Schedule online meeting in Microsoft Teams

Outlook triggers and Microsoft Teams actions

Outlook triggers

  • New email received in inbox or folder
  • Email matching search criteria arrives
  • Calendar event created or updated
  • Meeting invitation received
  • Contact added or modified
  • Out-of-office status changed

Microsoft Teams actions

  • Send message to channel
  • Send personal chat message
  • Create interactive card
  • Create or update teams
  • Schedule online meeting
  • Upload files
  • Create tabs and connectors

How to connect Outlook to Microsoft Teams

  1. Connect your Microsoft account. Authorize Autonoly to access your Outlook account via Microsoft's secure OAuth 2.0 authentication through the Microsoft Graph API
  2. Configure mailbox and calendar permissions. Set which mailboxes, calendars, and contact folders Autonoly can access and what actions it can perform on your behalf
  3. Connect to Microsoft Teams. Authorize Autonoly to access your Teams environment using Microsoft's secure OAuth authentication
  4. Configure application permissions. Set up which Teams features Autonoly can access and modify, following your organization's security policies
  5. Pick your trigger and action. Choose the Outlook event that should start the workflow, then the Microsoft Teams action it should run. Add a condition step if only some records should pass through.
  6. Test with one record, then turn it on. Run the workflow once against a real record and check the result in Microsoft Teams before enabling it.

Keeping Microsoft Teams notifications useful

Filter before you notify

A message for every record is a channel people mute within a week. Add a condition so only the cases that need a human get through.

Group the routine ones

Batch low-priority events into a scheduled digest and reserve instant messages for what is genuinely urgent.

Put the answer in the message

Include the fields somebody needs to act, so the notification does not just tell them to go and look somewhere else.

Route by content

Send to the channel that owns the record rather than one firehose channel everybody ignores.

Frequently asked questions

How do I connect Outlook to Microsoft Teams?

Connect both accounts to Autonoly, choose a Outlook trigger such as “New email received in inbox or folder”, then pick the Microsoft Teams action you want to run. The workflow goes live as soon as you save it — there is no code to write and nothing to host.

Is the Outlook to Microsoft Teams integration free?

Autonoly has a free plan you can build and run this workflow on. Paid plans add volume and advanced steps. See the pricing page for current limits.

How quickly does data sync between Outlook and Microsoft Teams?

Workflows run as soon as the Outlook trigger fires. You can also run them on a schedule if you would rather batch updates than send them one at a time.

Can I filter which Outlook records reach Microsoft Teams?

Yes. Add a condition step between the trigger and the action, and only records matching your rule continue. This is the usual way to keep test or draft records out of a production system.

Do I need a developer to set this up?

No. The builder is visual, and both Outlook and Microsoft Teams connect through standard authentication. If you do want code, you can drop into a script step at any point in the workflow.

Related automations, guides and terms

More on automating Outlook and Microsoft Teams.

IntegrationMicrosoft Teams integrationMaximize team collaboration with automated notifications, interactive bots, and seamless workflow integration across your Microsoft 365 environment.GuideHow to Transfer Data Between Web Apps That Don't IntegrateBusinesses use dozens of SaaS tools, but many simply do not connect to each other. When there is no API, no Zapier connector, and no native integration, teams resort to manual CSV exports, copy-paste, and data re-entry. This guide covers every practical approach to bridging the integration gap — from manual workarounds to AI browser automation — with honest comparisons of when each method makes sense.GuideHow to Automate Legacy Web Apps That Only Have a UILegacy web apps with no APIs, no webhooks, and no integrations are the hardest systems to automate. Traditional RPA costs $10K-$100K+/year and requires specialized developers. Learn how AI browser agents offer an affordable alternative for automating government portals, old CRMs, Oracle Forms, healthcare systems, insurance carrier portals, and internal tools — using nothing but the browser UI.IntegrationGmail integrationRevolutionize your email workflow with intelligent filtering, automated responses, and seamless integration with your business processes.IntegrationDiscord integrationEnhance your Discord community with automated moderation, interactive experiences, and powerful event-driven workflows that scale.IntegrationSignal integrationAutomate secure, encrypted notifications and alerts to Signal using bots so your team gets critical updates on a private channel.