Notion Slack notifications: what changed and 5 workarounds
Notion Slack notifications changed for many teams. Learn what likely changed, what is still supported, and 5 practical workarounds using automations.
Fixing Zapier Outlook Connection Errors (Legacy Deprecation): Step-by-Step
Microsoft deprecated legacy Outlook connections in Zapier. Learn how to reconnect, handle admin consent in Microsoft Entra, and restore broken Zaps.
TABLE OF CONTENTS
If your Zapier automations suddenly stopped sending or reading Outlook email, you are probably hitting Microsoft's legacy Outlook connection deprecation. The fix is usually not “toggle it off and on.” It is a combination of reconnecting the correct account and granting the right admin consent so Zapier can access the mailbox again.
Why Zapier Outlook connections break
Most failures come from one of these:
- The Zap uses a legacy Outlook connector that Microsoft no longer supports.
- The mailbox requires admin approval for the permissions Zapier is requesting.
- You are signed into multiple Microsoft accounts and Zapier keeps picking the wrong one.
Fast diagnosis checklist
Before you change anything, identify:
- Which Zaps are failing.
- Which Outlook connection each Zap uses.
- Whether the mailbox is a personal mailbox or a shared mailbox.
Step-by-step: reconnect Outlook in Zapier
1) Go to Zapier → My Apps
- Find the Outlook connection used by the failing Zap.
- Click Reconnect.
2) Use a clean browser session
If you manage multiple Microsoft logins:
- Put your admin account in one browser profile.
- Put the mailbox account in a separate browser profile or incognito session.
Goal: make the “pick an account” step predictable.
3) If you see “Approval required,” submit the request
When prompted:
- Add a short justification like “Zapier workflow automation.”
- Submit the request.
4) Approve the request in Microsoft Entra / Azure AD
In Microsoft Entra:
- Go to Enterprise applications.
- Find the Admin consent requests area.
- Locate the Zapier request.
- Review permissions and Approve.
If you do not see the request immediately:
- Refresh.
- Check the notification bell.
- Re-run the Zapier reconnect to generate the request again.
5) Re-test the Zap
After approval:
- Return to Zapier.
- Reconnect again if needed.
- Use the Zap “Test” step.
Common gotchas
- If Zapier keeps opening the wrong account, switch browser profiles.
- If it is a shared mailbox, you may need to authorize via an admin-managed account with delegated access.
- Some Zaps may need the Outlook step swapped from “legacy” to the updated Outlook app.
When to rebuild vs. repair
Repair is best when:
- The only issue is permissions or connection.
Rebuild is best when:
- The Zap uses old Outlook actions that no longer exist.
Get help fixing your broken Zaps
Outlook reconnections usually break at the admin consent step, especially when shared mailboxes and multi-account Microsoft environments are involved. If you've followed these steps and the Zap is still failing, book a ZoomFlow session — one of our consultants will debug the connection with you live and get the Zap running in the same call.
Related Posts
PracticePanther to Notion: Zapier sync for law firms
Learn a simple, one-way Zapier setup to sync PracticePanther clients, matters, invoices, and payments into Notion, with rollups that track AR without manual work.
Custom CRM vs. Off-the-Shelf: What a Zapier Automation Consultant Actually Recommends
A Zapier automation consultant breaks down when to build a custom CRM vs. buy off-the-shelf, and how to fill every gap with smart automations.
