Google Workspace users can use their business Gmail account directly inside Microsoft Outlook. This allows organizations to continue using familiar Outlook features while their email service remains hosted on Google Workspace.

However, Google Workspace authentication has changed significantly. Modern Outlook versions should normally connect to Google Workspace using OAuth, commonly displayed as “Sign in with Google.”

Older methods that authenticate only with the normal Google account username and password should no longer be used.

This guide explains:

• Recommended OAuth configuration
• Classic Outlook configuration
• New Outlook configuration
• Manual IMAP and SMTP settings
• App Password usage
• Google Workspace administrator considerations
• IMAP versus Google Workspace Sync for Microsoft Outlook (GWSMO)
• Common Outlook/Gmail problems
• Security recommendations
• Troubleshooting steps

1. What Is Google Workspace Email?

Google Workspace is Google's business productivity platform. Organizations can use Gmail with their own domain name, such as:

employee@company.com

instead of:

employee@gmail.com

Although the interface and underlying mail technology are based on Gmail, the account is administered through the organization's Google Workspace environment.

Users can access their mailbox through:

• Gmail in a web browser
• Gmail mobile application
• Microsoft Outlook
• Apple Mail
• Compatible third-party email clients
• Other applications supporting Google's authentication methods

For Outlook users, there are two important connection approaches:

1. Gmail/Google account connection using OAuth and IMAP
2. Google Workspace Sync for Microsoft Outlook (GWSMO), where supported

2. Important 2026 Security Change

Google no longer supports legacy Google Workspace applications that simply ask for a Google username and normal account password without using modern authentication.

Therefore, avoid configuring Outlook using only:

Email address + normal Google password

when Outlook is attempting legacy/basic authentication.

The preferred method is:

Outlook → Google Sign-In → OAuth Authorization → Allow Outlook access

OAuth is considerably better because Outlook does not need to store or repeatedly submit your normal Google password to authenticate using the old basic-authentication method.

3. Recommended Method: Add Google Workspace Directly to Outlook

Modern versions of Microsoft Outlook understand Google accounts.

In most situations, you should allow Outlook to detect the Google account automatically instead of manually entering IMAP and SMTP server information.

Requirements

Before starting, confirm that:

• The Google Workspace user account is active.
• The mailbox can successfully sign in to Gmail.
• You know the complete email address.
• You can complete Google's authentication process.
• Two-Step Verification can be completed if required.
• Your administrator has not blocked Outlook or third-party application access.
• Outlook is updated to a reasonably current version.

4. Configure Google Workspace in New Outlook for Windows

For the newer Outlook application:

1. Open Outlook.
2. Open View → View Settings.

Depending on the Outlook build, you may alternatively see account options under:

File → Account Info

3. Select:

Accounts → Your accounts

4. Click Add Account.
5. Enter your complete Google Workspace email address.

Example:

user@company.com

6. Click Continue.
7. Outlook should open Google's authentication page.
8. Select or confirm your Google Workspace account.
9. Enter your Google password on Google's sign-in page.
10. Complete Two-Step Verification if requested.
11. Review the permissions requested.
12. Click Allow.
13. Return to Outlook.
14. Wait for Outlook to finish adding the mailbox.
15. Click Done.

Outlook should begin synchronizing the mailbox.

Depending on mailbox size, Internet speed and Outlook configuration, the initial synchronization may take some time.

5. Configure Google Workspace in Classic Outlook

For Classic Outlook:

1. Open Microsoft Outlook.
2. Click:

File → Add Account

3. Enter the complete Google Workspace email address.

Example:

accounts@company.com

4. Click Connect.
5. Outlook should detect that the address belongs to Google.
6. A Google sign-in window should appear.
7. Confirm the Google account.
8. Enter the password on Google's authentication page.
9. Complete Two-Step Verification if required.
10. Review the permissions.
11. Select Allow.
12. Return to Outlook.
13. Wait for account configuration to finish.
14. Click Done.

Restart Outlook if necessary.

6. Why the Google Sign-In Window Is Important

A common mistake is assuming that seeing a Google login page means Outlook is redirecting the user unnecessarily.

It is actually an important security feature.

With OAuth, authentication occurs through Google's authorization system.

The basic flow is:

Outlook → Google Authentication → User Approval → Authorization Token → Outlook

This is preferable to giving an application unrestricted access using your normal account password.

7. Manual Google Workspace IMAP Settings

Manual configuration should normally be used only when automatic account detection does not work or when a specific legacy/technical configuration requires it.

Incoming Mail – IMAP

Setting	Value
Protocol	IMAP
Server	imap.gmail.com
Port	993
Encryption	SSL/TLS
Username	Complete Google Workspace email address
Authentication	OAuth preferred

Example username:

user@company.com

8. Google Workspace SMTP Settings

Outgoing Mail – SMTP

Setting	Value
SMTP Server	smtp.gmail.com
Recommended Port	587
Encryption	STARTTLS/TLS
Alternative Port	465
Encryption on Port 465	SSL/TLS
Authentication	Required
Username	Complete Google Workspace email address

For example:

user@company.com

Port 587 with TLS/STARTTLS is commonly used.

Port 465 with SSL/TLS is also supported in appropriate configurations.

9. Do You Still Need to Enable IMAP in Gmail?

Older setup instructions frequently tell users:

Gmail → Settings → Forwarding and POP/IMAP → Enable IMAP

This advice should not automatically be applied to every modern Google Workspace installation.

Google has changed how IMAP access and administrator controls work over time. Depending on the Google Workspace environment, access may be controlled centrally by the administrator.

If Outlook cannot connect through IMAP, the Google Workspace administrator should therefore verify whether IMAP access is permitted for the affected organizational unit or users.

10. What Is an App Password?

An App Password is a special password generated by Google for applications or devices that cannot use Google's preferred modern authentication process.

It is different from the user's normal Google password.

For example, suppose the normal Google password is:

MyNormalPassword

You should not enter that password into an old application that cannot perform Google's modern authentication.

Instead, where Google permits it, an App Password can be generated and used for that specific application.

11. When Should You Use an App Password?

Use an App Password only when necessary.

Typical situations include:

• An older Outlook configuration cannot use OAuth.
• A legacy email application requires IMAP/SMTP authentication.
• A device or application cannot display Google's OAuth login page.
• A compatible application specifically requires an App Password.

For modern supported Outlook installations, OAuth should be preferred.

12. Requirements for Google App Passwords

App Password availability depends on the Google account and security configuration.

Generally, Two-Step Verification must be enabled before App Password functionality becomes available.

App Passwords might also be unavailable when:

• The Google Workspace administrator restricts them.
• The account uses security configurations that prohibit App Passwords.
• Advanced security policies are enabled.
• The organization's authentication policy does not permit them.

Therefore, do not assume that every Google Workspace user will see an App Password option.

13. How to Create a Google App Password

If App Passwords are permitted:

1. Sign in to your Google Account.
2. Open Security.
3. Make sure 2-Step Verification is enabled.
4. Locate App Passwords, if available.
5. Authenticate again if requested.
6. Create an App Password for the required application.
7. Google will generate a special password.
8. Copy it.
9. Enter this App Password in Outlook or the application instead of the normal Google password.

Security Warning

Never publish, email or store an App Password in an unsecured document.

If you believe it has been exposed, revoke it and create another one.

14. Normal Google Password vs App Password vs OAuth

Authentication	Recommended?	Typical Usage
Normal password with legacy basic authentication	No	Obsolete/blocked configurations
App Password	Only when required	Legacy applications/devices
OAuth / Sign in with Google	Yes	Modern Outlook
GWSMO authentication	Yes, where appropriate	Supported Google Workspace + Outlook deployments

For a new Outlook deployment, OAuth should normally be the first choice.

15. What Is GWSMO?

Google also provides Google Workspace Sync for Microsoft Outlook (GWSMO).

GWSMO provides deeper synchronization between supported Google Workspace accounts and Microsoft Outlook.

It can synchronize information including:

• Gmail email
• Google Calendar
• Google Contacts
• Global Address List
• Tasks and certain other Outlook/Google data

This can be useful for organizations where employees strongly prefer the traditional Microsoft Outlook experience but the backend email system is Google Workspace.

16. IMAP vs GWSMO

These technologies should not be confused.

Feature	IMAP/OAuth	GWSMO
Email synchronization	Yes	Yes
Google Calendar integration	Limited/separate	Better integration
Google Contacts integration	Limited/separate	Supported
Global Address List	Limited	Supported
Simple setup	Usually easier	More deployment work
Additional Google software	No	Yes
Best for basic email	Yes	Possibly unnecessary
Best for Outlook-centric corporate users	Good	Often better

If employees primarily require email, standard Google account integration in Outlook may be sufficient.

If an organization requires stronger synchronization of email + contacts + calendars, investigate GWSMO.

17. Outlook Says "Something Went Wrong"

If Outlook reports:

Something went wrong

try the following:

1. Confirm that Gmail works in a web browser.
2. Confirm the complete email address.
3. Update Microsoft Outlook.
4. Restart Outlook.
5. Retry File → Add Account.
6. Complete the Google authentication window.
7. Make sure pop-up/login windows are not being blocked.
8. Check whether the Google Workspace administrator has restricted third-party applications.
9. Remove a partially created Outlook account/profile and retry if necessary.
10. Test the account on another computer or Outlook profile.

18. Outlook Keeps Asking for the Password

Repeated password prompts can occur because of:

• Old Outlook version
• Failed OAuth authentication
• Expired/revoked authentication token
• Incorrect legacy configuration
• App Password required by an older configuration
• Corrupt Outlook profile
• Google Workspace security policy
• Windows credential problems
• Network/proxy/security software interference

Do not repeatedly enter the normal Google password into an old legacy authentication prompt.

First determine whether Outlook is actually using OAuth.

19. "Invalid Username or Password" Even Though Password Is Correct

This is especially important after Google's retirement of legacy password-only authentication.

The password may actually be correct.

The problem may be that the application is trying to authenticate using an unsupported legacy method.

Possible solutions:

• Upgrade Outlook.
• Remove and re-add the account.
• Configure using Google's OAuth login.
• Use an App Password only when appropriate and permitted.
• Verify Google Workspace administrator policies.

20. Outlook Can Receive Email but Cannot Send

If incoming email works but outgoing email fails, check SMTP configuration.

Recommended values:

SMTP server: smtp.gmail.com

Port: 587

Encryption: STARTTLS/TLS

Alternative:

Port: 465

Encryption: SSL/TLS

Also confirm:

• SMTP authentication is enabled.
• Complete email address is being used as username.
• OAuth authentication completed successfully.
• Firewall/security software is not blocking SMTP connections.

21. Outlook Can Send but Cannot Receive

Check:

IMAP server: imap.gmail.com

Port: 993

Encryption: SSL/TLS

Also verify:

• Internet connection
• Google Workspace account status
• IMAP access policy
• Outlook synchronization status
• Folder synchronization
• Available Google storage
• Outlook profile health

22. Emails Appear in Gmail but Not Outlook

Possible causes include:

• Outlook synchronization delay
• IMAP synchronization problem
• Folder not subscribed/synchronized
• Outlook filters or views
• Cached profile problem
• Large mailbox synchronization
• Local Outlook data corruption

First verify the message in Gmail webmail.

If the message exists in Gmail but not Outlook, the mail has successfully reached Google's server. Troubleshooting should then focus primarily on Outlook synchronization rather than mail delivery.

23. Gmail Labels vs Outlook Folders

This is an important concept.

Gmail primarily uses labels, whereas Outlook traditionally presents mail organization using folders.

These systems are not identical.

One Gmail message can have several labels without several independent copies necessarily existing.

When Gmail data is displayed through Outlook, labels may appear similar to folders.

This can occasionally cause users to think messages are duplicated when the underlying Gmail organization works differently from a traditional folder-only mailbox.

24. Sent Mail Appears Twice

Duplicate sent messages may occasionally appear because both:

• Outlook saves a copy of the sent message, and
• Gmail automatically stores sent mail.

If duplicate Sent messages appear consistently, investigate Outlook's sent-message behavior and Gmail synchronization before deleting mail in bulk.

25. Deleted Email Behaviour

Deleting an email from Outlook may synchronize that action back to Gmail.

Therefore, users should understand that Outlook is not necessarily working with an independent copy of the mailbox.

Actions such as:

• Delete
• Move
• Archive
• Mark as read
• Flag

can synchronize with the server.

Always maintain appropriate organizational backup and retention policies for important business email.

26. Google Workspace Administrator Checks

If one user cannot configure Outlook, check the user's account first.

If many users suddenly cannot configure Outlook, investigate the Google Workspace environment.

Administrators should verify:

• User account is active
• Gmail service is enabled
• Appropriate IMAP access is permitted
• OAuth application access is permitted
• Context-Aware Access/security policies
• Two-Step Verification requirements
• App Password policy, if relevant
• Organizational Unit restrictions
• Third-party application access controls

27. Do Not Enable "Less Secure Apps"

Old tutorials may instruct users to enable:

Allow less secure apps

This is obsolete advice for Google Workspace.

Google has discontinued legacy password-only access for Google Workspace accounts.

If you find an old tutorial telling you to enable Less Secure Apps for Outlook, do not use that as your current configuration method.

Use OAuth / Sign in with Google instead.

28. Security Best Practices

For business Google Workspace accounts:

1. Enable Two-Step Verification.
2. Prefer OAuth.
3. Keep Microsoft Outlook updated.
4. Avoid sharing passwords with technicians or applications.
5. Revoke unused App Passwords.
6. Review connected applications periodically.
7. Remove access for old computers.
8. Use strong endpoint security.
9. Protect Windows user accounts with passwords/PINs.
10. Encrypt business laptops where appropriate.
11. Maintain email retention/backup policies.
12. Keep Windows updated.
13. Train users to recognize fake Google login pages.

29. How to Identify a Fake Google Login Window

OAuth is secure only when users authenticate through legitimate Google infrastructure.

Be suspicious when a page:

• Uses a strange domain
• Requests unnecessary information
• Asks you to send your password to a technician
• Downloads an unexpected executable
• Requests remote access without justification
• Has spelling errors or suspicious branding

For important business accounts, always verify the authentication page before entering credentials.

30. Recommended Configuration for Businesses

For most modern Google Workspace users:

Google Workspace → Modern Outlook → OAuth

Recommended architecture:

Google Workspace Gmail

↓

Google OAuth Authentication

↓

Microsoft Outlook

↓

IMAP/Google synchronization

This eliminates the need for legacy basic password authentication.

31. Configuration Quick Reference

Incoming Mail

Server: imap.gmail.com
Port: 993
Security: SSL/TLS

Outgoing Mail

Server: smtp.gmail.com

Recommended:

Port: 587
Security: STARTTLS/TLS

Alternative:

Port: 465
Security: SSL/TLS

Authentication

Preferred: OAuth / Sign in with Google

Fallback for compatible legacy applications: App Password

Not recommended/supported for legacy Google Workspace access: Normal username + password basic authentication

32. Recommended Troubleshooting Sequence

When Google Workspace is not working in Outlook, troubleshoot in this order:

Step 1

Open Gmail in a browser.

If Gmail itself does not work, solve the Google account problem first.

Step 2

Verify Internet connectivity.

Step 3

Check whether Outlook is current.

Step 4

Remove the failed account configuration if necessary.

Step 5

Add the Google Workspace account again.

Step 6

Make sure the Google authentication window opens.

Step 7

Complete OAuth authorization.

Step 8

If OAuth cannot be used, determine whether an App Password is appropriate.

Step 9

Verify IMAP/SMTP settings if manual configuration is being used.

Step 10

Ask the Google Workspace administrator to check security and application-access policies.

This approach is usually better than repeatedly changing ports and passwords without identifying the actual authentication problem.

Frequently Asked Questions (FAQ)

1. Can I use Google Workspace email in Microsoft Outlook?

Yes. Google Workspace Gmail accounts can be added to supported versions of Microsoft Outlook.

2. What is the recommended setup method in 2026?

Use Outlook's normal Add Account process and authenticate through Google's OAuth / Sign in with Google window.

3. Should I manually configure IMAP?

Usually not. Let Outlook automatically identify the Google account first. Manual configuration should primarily be used for troubleshooting or special configurations.

4. What is the Gmail IMAP server?

imap.gmail.com

5. What is the Gmail IMAP port?

Port 993 using SSL/TLS.

6. What is the Google Workspace SMTP server?

smtp.gmail.com

7. Which SMTP port should I use?

Port 587 with STARTTLS/TLS is commonly recommended. Port 465 with SSL/TLS is also supported.

8. Can I use my normal Google password in Outlook?

Modern Outlook should authenticate through Google's OAuth process. Legacy username/password-only authentication should not be relied upon.

9. What is an App Password?

It is a special password generated for applications or devices that cannot use the preferred Google authentication method.

10. Is an App Password the same as my Google password?

No.

11. Do I need Two-Step Verification?

It is strongly recommended for business accounts and is generally required when App Password functionality is used.

12. Why can't I see App Passwords?

Your account type, administrator policies or security configuration may prevent App Password usage.

13. Should I enable Less Secure Apps?

No. This is obsolete for Google Workspace and should not be used as a current Outlook configuration solution.

14. Why does Outlook open a Google login page?

Because Outlook is authenticating the account through Google's OAuth authorization system.

15. Why does Outlook repeatedly ask for my password?

Possible causes include an outdated Outlook installation, broken OAuth authorization, an old account configuration, corrupt Outlook profile or organizational security restrictions.

16. Why can Outlook receive email but not send?

Check SMTP authentication, server, port, encryption and OAuth authorization.

17. Why can Outlook send but not receive?

Check IMAP connectivity, synchronization status, Google Workspace policies and Outlook profile health.

18. Why are some emails visible in Gmail but missing from Outlook?

The problem is likely related to Outlook synchronization, folder/label mapping, cached data or the Outlook profile.

19. Does deleting mail in Outlook delete it from Gmail?

Because Outlook is synchronizing with the server, actions performed in Outlook can affect the server mailbox. Users should understand their account's synchronization behavior before deleting large quantities of mail.

20. What is GWSMO?

GWSMO stands for Google Workspace Sync for Microsoft Outlook. It provides deeper integration between supported Google Workspace accounts and Outlook.

21. Is GWSMO the same as IMAP?

No. IMAP mainly synchronizes email, whereas GWSMO can provide broader synchronization of supported Outlook and Google Workspace information.

22. Which is better: IMAP or GWSMO?

For basic email access, normal Outlook Google-account integration is usually sufficient. Organizations requiring deeper Outlook calendar/contact integration should evaluate GWSMO.

23. Can I configure multiple Google Workspace accounts in Outlook?

Yes, supported Outlook versions can contain multiple accounts.

24. Can Outlook work with Google Workspace when 2-Step Verification is enabled?

Yes. In fact, Two-Step Verification is recommended. Modern Outlook can authenticate through Google's OAuth process.

25. What should I check first when Google Workspace stops working in Outlook?

First open Gmail through a browser. If Gmail webmail works correctly, investigate Outlook authentication and synchronization next.

Conclusion

Setting up Google Workspace email in Microsoft Outlook is now considerably more security-focused than older IMAP tutorials suggest.

The most important rule for modern installations is:

Use OAuth / “Sign in with Google” whenever possible.

Do not depend on obsolete Less Secure Apps or ordinary password-only authentication.

For most users, simply adding the Google Workspace address to a current version of Outlook and completing Google's authorization screen is the preferred configuration.

Manual IMAP/SMTP settings remain useful for troubleshooting and specialized configurations, while App Passwords should be reserved for compatible applications that genuinely cannot use OAuth.

Organizations with employees who depend heavily on Outlook calendars, contacts and other Outlook-centric functionality should also evaluate Google Workspace Sync for Microsoft Outlook (GWSMO).

 

#GoogleWorkspace #MicrosoftOutlook #Gmail #OutlookSetup #GoogleWorkspaceSetup #GmailOutlook #EmailSetup #BusinessEmail #GoogleOAuth #OAuth #IMAP #SMTP #GmailIMAP #GmailSMTP #OutlookConfiguration #EmailConfiguration #GoogleWorkspaceAdmin #GoogleAdmin #AppPassword #TwoStepVerification #2FA #EmailSecurity #GmailSecurity #OutlookSecurity #ModernAuthentication #GoogleWorkspaceEmail #BusinessGmail #CorporateEmail #EmailTroubleshooting #OutlookTroubleshooting #GmailTroubleshooting #IMAPSettings #SMTPSettings #Outlook2024 #Outlook2021 #Outlook2019 #Outlook2016 #Microsoft365 #NewOutlook #ClassicOutlook #GWSMO #GoogleWorkspaceSync #GmailSettings #EmailClient #GoogleSecurity #WorkspaceAdmin #GoogleWorkspaceGuide #OutlookGuide #TechnicalSupport #BisonKB