The first thing most people do when they try to get Google Workspace working in Outlook is set up IMAP. That’s the biggest mistake you can make — especially if your company uses Google’s SSO, 2-Step Verification, or shared calendars. IMAP gives you email only. No contacts sync. No real-time calendar updates. And zero access to Google Chat or Spaces. You’ll think it’s working — until Michael Rodriguez’s meeting invitation disappears after a sync conflict, or Priya Sharma’s delegated calendar stops showing free/busy status.
The Short Version
Here’s how each method actually behaves in real-world use — tested across Outlook 365 (v2405), Outlook 2019, and Outlook on the web:
| Method | Calendar | Contacts | Limitations | |
|---|---|---|---|---|
| IMAP + SMTP | ✓ Full sync | ✗ Static .ics only | ✗ Manual import only | No delegation, no push updates, breaks with 2-Step |
| Google Workspace Sync for Microsoft Outlook (GWSMO) | ✓ Full sync | ✓ Real-time, two-way | ✓ Two-way sync | Deprecated since July 2022. Won’t install on Outlook 365 v2308+ |
| Outlook Add-in (Google Calendar Sync) | ✗ Not supported | ✓ One-way only (Google → Outlook) | ✗ No contact sync | Only works in desktop Outlook. Fails silently if Google admin disables API access. |
| Exchange ActiveSync (via Google’s EAS gateway) | ✓ Push email | ✓ Real-time calendar & tasks | ✓ Contacts (read-only) | Requires Google Workspace Business Plus or Enterprise. Disabled by default in many orgs. |
Method 1: IMAP + SMTP
Go to File > Add Account > Manual setup > POP or IMAP. Enter your Google Workspace email, select IMAP, then fill in imap.gmail.com (port 993, SSL) and smtp.gmail.com (port 465, SSL). Enable 'Less secure app access' — or better yet, create an App Password under your Google Account Security settings if 2-Step is on.
This works for email only. Nothing else. Your inbox shows up. But James O'Brien’s recurring team meeting won’t update if he moves it. Delegated calendars appear as static folders — not live views. Contacts stay in Google and never touch Outlook’s address book.
Worse: If your Google admin has enforced SSO or disabled IMAP entirely (common in Education and Government editions), this fails at step one. No error message — just a spinning wheel and silence.
Surprising tip: Even if IMAP works, Outlook caches old calendar data for up to 72 hours. Force-refresh with F9, then right-click the calendar folder > Update Folder. Still won’t fix delegation gaps.
Method 2: Google Workspace Sync for Microsoft Outlook (GWSMO)
This was Google’s official connector — and it worked well. It synced email, calendar, contacts, and tasks in real time. It respected delegation. It even handled shared mailboxes with permissions.
But Google killed GWSMO in July 2022. The installer now blocks installation on Outlook 365 versions newer than v2307. On Outlook 2019, it installs but crashes during calendar sync if you’re using Microsoft Entra ID federation.
If you find an old MSI installer online, don’t run it. It uses deprecated OAuth scopes. It will fail authentication — and worse, expose your Google credentials to unapproved token requests. Admins can see these attempts in the Google Admin Console under Reports > Audit > Token activity.
GWSMO also required local admin rights. That’s why it failed silently on locked-down corporate laptops — no warning, just missing icons in the ribbon.
Method 3: Exchange ActiveSync (EAS)
This is the only method that gives full, native-like integration — but only if your Google Workspace edition supports it and your admin has enabled it.
EAS is turned off by default. Your Google admin must go to Admin Console > Apps > Google Workspace > Gmail > Client access > Enable Exchange ActiveSync. Then assign the policy to users or OUs. Without this, Outlook shows 'Cannot connect to server' — no hint about where to fix it.
Once enabled, add the account via File > Add Account > Automatic setup. Type your Google email. Outlook detects EAS automatically. No manual ports. No passwords. Uses modern OAuth2 — so it respects 2-Step, SSO, and conditional access rules.
EAS syncs email, calendar, contacts, and tasks. Shared calendars show live free/busy. Delegation works. Meeting updates flow both ways. Even offline edits sync when you reconnect.
But there’s a catch: Contacts are read-only in Outlook. You can’t edit them in Outlook and push back to Google. And EAS doesn’t support Google Chat or Spaces — those remain web-only.
Also: Outlook on the web doesn’t support EAS. So if you rely on Outlook Web App, you’re stuck with IMAP or nothing.
Which Should You Choose?
Use this decision matrix — based on your actual setup, not what sounds best:
| Your Situation | Do This | Why | Admin Check |
|---|---|---|---|
| You’re on Google Workspace Business Plus or Enterprise AND your admin has EAS enabled | Use EAS — automatic setup | Full sync, zero config, respects security policies | Check Admin Console > Apps > Google Workspace > Gmail > Client access |
| You’re on Google Workspace Business Standard or lower | Use IMAP — but only for email | EAS isn’t available. GWSMO is dead. IMAP is the only fallback. | Confirm IMAP is enabled under Admin Console > Apps > Google Workspace > Gmail > User settings |
| You need calendar sync and can’t upgrade Google Workspace | Use Outlook Web App + Google Calendar side-by-side | No sync needed. Just open both tabs. Works with SSO, 2-Step, and delegation. | Zero admin action required |
| You manage devices via Group Policy and block third-party apps | Block IMAP entirely. Use Outlook Web App only | Prevents credential leakage from App Passwords. Forces OAuth2 via browser. | Set Computer Configuration > Administrative Templates > Google > Disable IMAP Access |
| You use Outlook 365 on Mac | Use IMAP — EAS isn’t supported on macOS Outlook | Microsoft hasn’t implemented EAS for Mac. No workaround exists. | N/A — client limitation |
