Microsoft 365 Email Not Syncing: Troubleshooting Guide for Philippine Businesses

Outlook not syncing is one of the most disruptive day-to-day M365 issues in Philippine offices — especially after a network change, a password reset, or a device re-enrolment. Most sync failures trace to a small set of root causes, and most can be resolved without a support ticket.

This guide covers desktop Outlook, Outlook for iOS/Android, and common error codes, in order of most to least common cause.

Step 1: Check M365 Service Health Before Touching the Client

Before adjusting any client settings, confirm the issue is not a Microsoft-side outage. Open the Microsoft 365 admin centre → Health → Service health. Alternatively, check status.office.com.

If Exchange Online or Outlook is listed as degraded or under investigation, the fix is to wait. Philippine offices on M365 Business plans occasionally experience delays originating from the Asia Pacific datacentre region — nothing on the client side resolves a service outage.

Step 2: Re-Authenticate the Account

The most common cause of sync failure after a password change, MFA reset, or Conditional Access policy update is a stale authentication token. Outlook continues to appear to run but cannot retrieve new mail.

Desktop Outlook (Windows):

1. File → Account Settings → Account Settings
2. Select the Exchange/M365 account → Remove
3. Close Outlook completely — check the system tray and end any lingering OUTLOOK.EXE processes
4. Reopen Outlook → Add Account → enter email address
5. Sign in with current credentials and complete MFA when prompted

Outlook for iOS/Android:

1. Settings → Mail accounts → select the account → Delete Account
2. Re-add via Outlook app settings (always use the Outlook app, not the iOS or Android system mail client, for M365 accounts)

If MFA is prompting repeatedly without completing, the issue may be an authenticator app registration problem. Follow the M365 MFA setup guide for Philippine businesses for the correct re-registration steps.

Step 3: Decode the Send/Receive Error Code

Outlook for Windows reports sync errors with specific codes under Send/Receive → Show Progress → Details. The most common codes in Philippine M365 deployments:

Error Code	Cause	Fix
0x800CCC0E	Cannot connect to server	Check internet connection; confirm firewall allows *.outlook.com and *.office365.com
0x80004005	General authentication failure	Re-authenticate the account (Step 2)
0x8004010F	Outlook data file inaccessible	Repair or rebuild the OST file (Step 4)
0x80070005	Permission denied to data file	Run Outlook once as administrator; check antivirus is not locking the OST
0x80040164	Autodiscover failure	Follow Autodiscover troubleshooting (Step 5)

Step 4: Repair or Rebuild the OST File

If Outlook connects but folders are missing or show stale data, the local cache file (OST) is corrupted.

1. Close Outlook fully
2. Open Control Panel → Mail → Email Accounts → Data Files tab
3. Note the OST file path (typically %LOCALAPPDATA%\Microsoft\Outlook\)
4. Rename the OST file — append .old to the filename; do not delete it until sync is confirmed working
5. Reopen Outlook — it rebuilds the OST from the server automatically

For large mailboxes (20 GB+), the rebuild takes 30–90 minutes. Going forward, set Outlook to Cached Exchange Mode with a 12-month sync window to keep the OST file manageable: File → Account Settings → Change → adjust the slider to 12 months.

Step 5: Test and Fix Autodiscover

Autodiscover tells Outlook where Exchange lives. If it resolves incorrectly, Outlook cannot configure or reconnect the account.

Test from Outlook:

1. Hold Ctrl → right-click the Outlook icon in the system tray
2. Select Test Email AutoConfiguration
3. Enter the user's email address → Test
4. Results should show autodiscover.outlook.com as the Exchange server

If Autodiscover points to an on-premises Exchange server or returns an error, the cause is typically a stale DNS SRV or CNAME record — or a hybrid Exchange configuration not fully cleaned up after migration to M365. This requires admin-level DNS changes and is appropriate to escalate.

Step 6: Firewall and Proxy Rules for M365 Endpoints

Philippine offices running Fortinet FortiGate, Palo Alto, or Cisco Secure Firewall with SSL inspection can break M365 sync when the firewall intercepts TLS connections to Microsoft's endpoints. The fix is to exclude Microsoft's URLs from SSL inspection entirely.

Required endpoints — allow outbound on port 443 and exclude from SSL inspection:

• *.outlook.com
• *.office365.com
• *.microsoft.com
• login.microsoftonline.com
• *.sharepoint.com
• *.lync.com

Microsoft publishes the full M365 URL and IP range list with change notifications. Subscribe to their RSS feed so firewall exclusion rules stay current as Microsoft updates infrastructure.

Step 7: Mobile-Specific Checks

For Outlook on iOS/Android that connects but does not deliver new mail promptly:

Background refresh (iOS): Settings → Outlook → Background App Refresh → On. Without this, Outlook cannot fetch mail while the screen is off.

Battery optimisation (Android): Settings → Apps → Outlook → Battery → Unrestricted. Android's aggressive battery management kills background app processes on many Philippine-market devices (Samsung, OPPO, Xiaomi), which stops mail sync silently.

Push notification permissions: Outlook mobile requires push notification permissions to deliver mail immediately. If denied, mail only arrives when the app is opened manually.

Intune device compliance: If your organisation uses Microsoft Intune endpoint management, a device that falls out of compliance — expired certificate, MDM policy violation, unenrolled device — will be blocked from syncing by Conditional Access. Check the device's compliance status in the Intune admin centre before doing client-side troubleshooting.

Licence assignment: Confirm the user has an active M365 licence. A licence removed or expired in the admin centre cuts Exchange access immediately. Check via M365 admin centre → Active Users → select user → Licences and apps tab.

When to Escalate

Escalate to your M365 administrator or managed service provider when:

• The issue affects multiple users simultaneously — this is a tenant or service-level problem, not per-device
• Autodiscover resolves to an incorrect or on-premises server
• Conditional Access is blocking access after a planned device refresh
• The M365 service health dashboard shows no issues but sync consistently fails across re-authentication attempts

Keeping M365 licence assignments clean and Intune device compliance current prevents the majority of recurring sync issues in Philippine offices.

---

Related reading

• Microsoft 365 MFA Setup Guide for Philippine Businesses
• Microsoft Intune Endpoint Management for Philippine Businesses
• Microsoft 365 Licence Optimisation for Philippine Businesses
• Zero Trust Security for Philippine Businesses: What It Means and How to Implement It

Talk to our Cloud & I.T. team