Open the connector picker in Copilot Studio and search for Outlook. You’ll find two options: Office 365 Outlook and Microsoft 365 Outlook. Both send emails, both manage calendars, neither requires premium licensing. So why do they exist separately?

the outlook logo on a white background

Office 365 Outlook is the mature Power Platform connector. It works across Power Automate, Power Apps, Logic Apps, and Copilot Studio, with a wide action surface: triggers, folder management, attachments, reply/forward, flagging, and more.

Microsoft 365 Outlook is purpose-built for generative AI agents. Rather than individual actions, it offers three curated tool groups: Manage emails, Manage calendar, and Manage contacts. Fewer actions, but designed so the model knows how to use them without being explicitly told.

It’s actually three connectors

There’s a third: Outlook.com, for personal accounts only. The split is architectural:

  • Office 365 Outlook: work/school accounts, authenticated via Entra ID.
  • Outlook.com: personal accounts. New enterprise connections no longer allowed; personal account support in Power Automate deprecated May 2025.
  • Microsoft 365 Outlook: work/school accounts only. Copilot Studio requires Entra ID anyway.

One gotcha worth knowing: sending from a shared mailbox still works. Set up Send As or Send on Behalf Of in Exchange, create the connection with your work account, and specify the service account in the From parameter.

hand with thumb and index finger touching and last three things extended to give okay sign or indicate number 3

Which to use

Use Microsoft 365 Outlook when building a generative agent acting on natural language: HR bots, helpdesk agents, sales assistants. The tool groups make it easier for the AI to pick the right action.

Use Office 365 Outlook when you need triggers, advanced email operations, cross-platform compatibility, or deterministic logic with explicit branching.

For a simple “send an email” scenario, either works. The differences emerge at the edges.

The two connectors reflect Microsoft’s broader split between deterministic automation and AI-native orchestration. They’re not competing. The naming confusion is mostly a side-effect of the “Office 365 to Microsoft 365” rebrand that never quite finished.

Tags: , ,