How to Sync Google Workspace to Outlook, Connect Email with Microsoft Outlook 365 Easily 2026

Sign in as a Workspace admin and land on the Admin console's home dashboard, which surfaces quick links for managing users and billing along with setup recommendations for the domain. Nothing needs to change here. This is the jumping-off point before heading into the Google Workspace Marketplace, where the sync connector lives, or into Gmail's end-user access settings if you're connecting Outlook directly instead.

In the Google Workspace Marketplace, an app such as sync.blue is built to keep contact data synced between Google Workspace and other platforms, including Outlook. The listing shows what it does plainly, "Keeps your contacts in sync between countless apps," along with its rating, download count, and permissions before you install. This trades a few minutes of manual setup for an authorization flow the app walks you through, and it's the better fit if you want contacts and directory info staying in sync on an ongoing basis instead of doing a one-time import.

Once installed and activated, the app's own dashboard opens to a "My connections" page that explains the model plainly: one connection syncs data between exactly two accounts, and you can create as many connections as you need. Click Create connection to start linking your Google Workspace account to the Outlook side. This step replaces manually entering incoming and outgoing mail server details, since the app handles the authorization handshake with both platforms.

The connection wizard runs through three labeled stages, Choose your apps, Authorize your apps, and Configure connection, starting with a search box where you pick the source. Typing "google workspace" surfaces specific options, including Google Workspace Domain Shared Contacts and Google Workspace Directory, so you can pick the exact dataset you want flowing out of Workspace instead of a generic "Google" option that might pull in more than you intend.

After picking the Workspace source, the wizard moves to step 2 and asks you to sign in and grant permission on the Google side, then repeats the process for Outlook as the destination app. Each platform's own OAuth consent screen is what grants access, not a password typed into the connector. Step 3, Configure connection, is where you set sync direction and frequency before the two accounts start exchanging data on their own.

If you'd rather not add a Marketplace app and only need mail, modern Outlook (Microsoft 365, Outlook 2019, or Outlook 2016) can add a Google Workspace account directly through Google's own OAuth sign-in screen. Choose Add Account in Outlook, enter the Workspace email address, and Outlook hands off to a Google sign-in and consent page instead of asking for a password itself.

No app password, no manual server settings, and no separate IMAP toggle needed for this path. Google recommends this route specifically. Since May 1, 2025, Workspace accounts no longer accept the older style of sign-in where a third-party app asks for your Google username and password directly.

Older Outlook builds that don't support OAuth still need the legacy path, and it has two extra requirements this guide previously skipped. First, a Workspace admin has to turn on IMAP access for the account: in the Admin console, go to Apps > Google Workspace > Gmail > End User Access, then enable POP and IMAP access for the relevant organizational unit.

Second, because plain passwords are no longer accepted, you need an app password: turn on 2-Step Verification for the account, generate an app password, and enter that 16-character string in Outlook in place of the normal login. The server settings are imap.gmail.com on port 993 (SSL) for incoming and smtp.gmail.com on port 587 (TLS) or 465 (SSL) for outgoing. This route only handles mail; it won't sync contacts or calendar the way a dedicated connector does.

Whichever method you use, check Outlook after the initial sync to confirm mail, contacts, or calendar events (depending on what you connected) show up and update when something changes on the Workspace side. A connector-based sync runs on its own schedule, so give it a few minutes after setup before assuming something is broken if a contact hasn't appeared yet.