Key takeaway: Exchange Online is the mail and calendar engine behind much of Microsoft 365, so Outlook, Teams, OneDrive, SharePoint, Planner, To Do, Bookings and Power Automate all read and write the same mailbox data. When it works, a meeting link, a file link, a flagged task and a chat all line up. When it breaks, the cause is almost always one of a short list: licensing, a missing add-in, the wrong sharing setting, a mailbox that is not where the service expects, or a hybrid OAuth problem. This guide explains each integration, how it works under the hood, how to configure and govern it, and how to troubleshoot it.
In This Article
- How the Pieces Connect
- Teams Meetings From Outlook
- The Teams Calendar Is the Exchange Calendar
- Teams Chat, Channel Messages, and the Mailbox
- OneDrive and SharePoint Links in Mail
- Flags, To Do, Planner, and Tasks
- Bookings and Scheduling Pages
- Power Automate and Graph
- Copilot and Insight Tools
- Admin Checks for All Integrations
- How to Check It Worked
- Troubleshooting
- A Short Decision Guide
Users see this as "it just works." Admins need to know *why* it works, because each integration depends on a different service and fails for different reasons.
How the Pieces Connect
| Integration | What it uses | Admin controls |
|---|---|---|
| Teams meeting button in Outlook | Teams Meeting add-in, Exchange calendar | Teams meeting policies, add-in deployment |
| Teams calendar app | The user's Exchange Online mailbox | Mailbox location, licenses, hybrid OAuth |
| Teams chat and channel messages | Hidden mailbox folders (for retention and compliance) | Retention policies |
| Attach OneDrive/SharePoint files | Links to files, sharing links | SharePoint and OneDrive sharing settings |
| Flagged mail and To Do | The mailbox task folder and To Do service | License, To Do availability |
| Planner tasks in To Do | Planner and To Do services | Planner settings |
| Bookings | A Bookings calendar mailbox | Bookings policy, licensing |
| Power Automate | Graph/Exchange connectors | Data loss prevention for flows, connector policy |
| Viva Insights, Copilot | Graph data from mail and calendar | License, privacy settings |
The shared foundation is Microsoft Entra ID for identity and Microsoft Graph for data. If sign-in is broken or the license is missing, several integrations fail at once, which is a hint.
Teams Meetings From Outlook
How it works. Installing Teams (or the new Teams client) installs the Microsoft Teams Meeting add-in for Outlook. A New Teams Meeting button appears on the Outlook calendar ribbon. Clicking it adds a join link and dial-in details to the invite, and creates the meeting in the Teams service tied to the organizer's account.
What users do.
- In Outlook, choose New Meeting, add attendees, and click Teams Meeting.
- Send the invite. Attendees click Join at the time.
- For recurring meetings, the same link is used for the series.
Admin controls.
- Meeting policies in the Teams admin center control who can bypass the lobby, record, present, and use chat.
- Dial-in numbers need Audio Conferencing licenses if you want phone join.
- Default meeting options can be set per policy or by organizers in Meeting options.
- Deploy the add-in with Microsoft 365 Apps. Avoid blocking Outlook add-ins broadly.
When the button is missing.
| Check | Fix |
|---|---|
| Teams installed for this Windows user? | Install or repair Teams, then restart Outlook |
| Add-in disabled? | File, Options, Add-ins, Manage COM Add-ins, Go, enable *Microsoft Teams Meeting Add-in* |
| Outlook running as a different elevation level than Teams? | Run both as the standard user |
| Account lacks a Teams license or meeting policy blocks scheduling? | Fix license and policy |
| Using the new Outlook or web? | The button is built in; check the Teams license |
| Add-in registered per machine vs per user | Reinstall Teams with the machine-wide installer if appropriate |
Meetings created by one organizer and edited by another can lose their Teams link. Only the organizer should edit the meeting, or use co-organizers where available.
The Teams Calendar Is the Exchange Calendar
The Calendar app in Teams displays the user's Exchange Online calendar. For it to work the mailbox must be in Exchange Online, or in a correctly configured hybrid with OAuth, and the user must be licensed for Exchange and Teams. Symptoms of a mailbox in the wrong place include a blank Teams calendar, "We couldn't load your calendar," or missing meeting creation features.
Check:
Get-Mailbox jsmith@contoso.com | Format-List RecipientTypeDetails, ArchiveStatus
Get-MailboxPlan -Identity "ExchangeOnlineEnterprise" | Format-ListFor a user with an on-premises mailbox, the hybrid must be healthy: Test-OAuthConnectivity, intra-organization connectors, and valid certificates. See internal PKI and hybrid certificates.
Shared calendars, room calendars, and Microsoft 365 group calendars appear in Teams only partly. Teams channel calendars are Microsoft 365 group calendars, so make sure the group exists and the user is a member.
Teams Chat, Channel Messages, and the Mailbox
Teams stores chat and channel messages in the Microsoft 365 backend, and a compliance copy goes to hidden folders in Exchange mailboxes (the user's mailbox for chats, the group mailbox for channel messages). This matters because:
- Retention policies for Teams use those hidden folders. See retention policies.
- eDiscovery searches find Teams messages through mailboxes.
- A mailbox on hold also preserves Teams messages stored in it.
- If a user has no Exchange Online mailbox (for example an on-premises mailbox with no hybrid), Teams compliance features cannot store messages in the expected place, and retention for those messages does not work as intended.
OneDrive and SharePoint Links in Mail
Attaching a file as a link. In a new message, choose Attach File, Browse Web Locations (or Attach, Browse cloud locations), pick the file, and choose how to share (view or edit; for people in the organization or specific people). Recipients get a link to the one live version. Benefits: no duplicate copies, one version of the truth, and you can revoke access later.
Admin controls (SharePoint admin center, Policies, Sharing).
- External sharing level for the organization and per site.
- Default link type: *Specific people* is safer than *Anyone with the link* or *People in your organization*.
- Link expiration for guests and Anyone links.
- Block download for sensitive sites through Conditional Access.
- Sensitivity labels that control sharing and encryption on files.
Attachments and size. Exchange Online limits message size (150 MB maximum when configured, with defaults lower). Link sharing is the practical answer for large files. Check the limit with Get-TransportConfig | Format-List MaxSendSize, MaxReceiveSize.
Recipients who cannot open a link usually lack permission (the sender chose "Specific people" and wrote the wrong address), or are guests blocked by tenant sharing rules, or are using an account that does not match the invited address.
Flags, To Do, Planner, and Tasks
- Flagged email in Outlook shows up in Microsoft To Do under *Flagged email*, because both use the mailbox task data. Complete it in either place and it syncs.
- Planner tasks assigned to a user appear in To Do under *Assigned to me* and in the Teams Tasks app.
- Outlook Tasks are the same data as To Do tasks in the mailbox.
Users who do not see flagged mail in To Do usually have an account mismatch (signed in to a different account), or an outdated Outlook, or To Do is disabled by policy.
Admins can govern these with Microsoft 365 apps and service settings in the admin center, and with the Tasks and To Do settings.
Bookings and Scheduling Pages
Bookings gives customers a scheduling page. It creates a Bookings calendar (a special mailbox) and checks the staff's Exchange calendars for free/busy, then writes appointments back. Control who can create Bookings pages with Set-OrganizationConfig -BookingsEnabled $false or through the Bookings policy, and review the settings on payment, social sharing, and who can access the pages.
Power Automate and Graph
Flows can trigger on new mail, create calendar events, and move attachments to SharePoint. Admins should:
- Use data loss prevention policies in the Power Platform admin center to control which connectors can mix (for example, business connectors with consumer ones).
- Prefer shared mailbox triggers for process mail, and avoid personal accounts that expire.
- For applications using Microsoft Graph with application permissions, apply an application access policy or role-based access control for applications so the app only reaches the mailboxes you intend.
- Review enterprise application consent regularly.
Copilot and Insight Tools
Microsoft 365 Copilot reads the user's mail, calendar, files, and chats that the user can access. It respects permissions, but it also makes bad permissions visible: overshared files and shared mailboxes become easy to find. Before a rollout, fix oversharing, apply sensitivity labels, and tidy delegate permissions. Viva Insights uses calendar and mail metadata to show meeting time and focus time; check privacy settings and what managers can see.
Admin Checks for All Integrations
- Licenses. Confirm each user has Exchange Online, Teams, SharePoint, and any add-on (Audio Conferencing, Copilot). Missing service plans cause partial failures.
- Mailbox location. Everyone using Teams calendar and compliance features should have an Exchange Online mailbox.
- Sharing defaults. Review SharePoint and OneDrive sharing, guest access in Teams, and link types.
- Add-ins. Review the Outlook add-ins deployed from the Integrated apps page.
- Conditional Access. Make sure policies for Exchange, SharePoint, and Teams do not block each other's sign-ins. Legacy clients and compliant-device rules often break an integration.
- Service health. Check the Microsoft 365 admin center service health and message center.
- Pilot meeting. Run a test meeting with users on different clients (Windows, Mac, web, mobile) and a guest.
How to Check It Worked
- Create a Teams meeting from Outlook and join from another device.
- Open Teams Calendar and confirm it matches Outlook.
- Share a file by link with a colleague and with a guest, and confirm access matches your settings.
- Flag an email and confirm it appears in To Do.
- Assign a Planner task and confirm it shows up in To Do.
- Check a retained Teams message through a Content Search in a test.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| No "Teams Meeting" button | Add-in disabled, Teams not installed for this user, missing license or policy |
| Teams calendar empty or error | Mailbox not in Exchange Online, hybrid OAuth broken, or missing license |
| Meeting link works for some attendees only | Lobby settings, guest policies, or anonymous join blocked |
| Link to a file says "access denied" | Shared with specific people, or external sharing blocked |
| Flagged mail missing in To Do | Different account, To Do disabled, or sync delay |
| Teams chats not retained | Retention policy not applied, or no Exchange Online mailbox |
| Planner tasks missing | User not assigned, Planner turned off, or the plan was deleted |
| Booking page shows no times | Staff calendar not connected, working hours missing, or permissions wrong |
| Flow stops working | Connection expired, license changed, or the connector was blocked by policy |
A Short Decision Guide
- Teams meeting from Outlook: add-in plus Teams license and policy.
- Large attachments: send links, set sharing defaults.
- Teams compliance: Exchange Online mailbox plus retention policies.
- Process automation: shared mailbox trigger plus DLP policy.
- Before Copilot: fix permissions and sharing.
Related guides: sharing calendars, retention policies and DLP, and access from anywhere.
Product names, admin center paths, limits, and licensing change often in Microsoft 365, and I have not tested these steps in your tenant. Confirm them against Microsoft's current documentation and run a pilot. If you want a review of how your tenant's integrations are set up, get in touch.