
When Outlook differs between a desktop and phone, first establish where the missing item is stored. Mail, calendars, and contacts can use different account connections, and a local data file can contain information that exists only on one computer.
Write down the Outlook client, account provider, account type, and affected folder or calendar. “Outlook” names the application; it does not by itself identify the service storing the data. Use the provider’s browser view as a comparison point when that service offers one.
Map the account before changing it
Scroll the table horizontally on a small screen. Keyboard users can focus the table region and use the arrow keys.
| Data or connection | What to expect | What to establish |
|---|---|---|
| Microsoft 365 / Exchange account | Supported clients synchronize server-backed mail, calendars, and contacts. | Whether the item belongs to the account or a local folder. |
| IMAP connection | Mail synchronization; calendar and contacts need separate supported integration. | Which provider connection handles the other data. |
| POP connection | Mail download behavior depends on client and server settings. | Whether unique messages remain only on the desktop. |
| Local PST or local-only folder | A local store requiring a deliberate backup or migration process. | Which items are absent from the account’s server view. |
Microsoft’s sync basics describes differences among Exchange, IMAP, and POP. Client features vary, so use the documentation for your installed Outlook version when configuring a connection.
Some Outlook clients synchronize supported non-Microsoft accounts through Microsoft’s cloud. The supported data and providers depend on the client. Read Microsoft’s account-sync explanation when deciding whether that arrangement fits your organization’s requirements.
Use a browser–desktop–phone comparison
- Check the service. Sign in through the provider’s normal browser interface. Look for the specific message, calendar event, or contact.
- Check the location. On the desktop, inspect the selected account and folder. For an event, inspect its calendar; for a contact, inspect the account or contact folder.
- Check the affected client. Confirm connectivity, sign-in status, synchronization errors, and whether the relevant calendar or folder is visible.
- Test one item type. Create an innocuous calendar event in the server-backed calendar, then check the phone. Separately test a contact if contacts are the problem.
- Test the reverse direction. Edit the test item on the phone and verify the browser view. Record where the change stops.
If a browser change reaches the desktop but not the phone, focus on the phone connection. If an item is visible only in a local desktop folder, reconnecting the phone will not transfer that local item. It needs a supported migration into the intended account.
Worked example: email works, calendar is missing
Microsoft’s mobile troubleshooting guidance confirms that IMAP and POP handle mail rather than calendar and contact synchronization. Use your provider’s supported sign-in flow for additional data types instead of guessing Exchange server settings for an unrelated service.
If the phone shows the event at another time, compare time zones and the underlying instant before changing the appointment. The calendar sync guide provides that test and a downloadable log.
Preserve unique data before a reset or migration
Before removing an account, rebuilding a profile, or replacing a data file, inventory unsent messages, local folders, contacts, calendars, and recent offline edits. Preserve unique material through the export or backup method documented for your Outlook version, then confirm the saved copy is readable.
An OST is generally a synchronized local cache tied to its account and profile; plan recovery around the service and supported tools. A PST may contain unique local archives. Treat each file according to its actual role. Microsoft explains PST and OST storage and the limitations of syncing an active PST through OneDrive. A general cloud-sync folder is a poor substitute for a deliberate live-mailbox synchronization design.
For a migration, copy a small representative set first. Include a recurring event with an exception, a contact with multiple fields, and a message with an attachment. Check the destination in the browser and the intended clients before expanding the move. Retain the source until you have reconciled the results.
If the failure persists, give support the client version, provider, affected data type, time of the last successful sync, exact error, and the three-way test result. That evidence narrows the problem more effectively than repeatedly deleting and adding the same account.
Continue exploring
- Calendar Sync: Accounts, Subscriptions, Imports, and Time Zones
- Online Backup
- All software guides and earlier coverage
Product documentation checked September 7, 2026. Recheck your installed version, account plan, and organization’s settings when following product-specific steps.