Using the New Outlook for Mac features in business environments
Check the affected messages in Outlook on the web first, then use the tenant’s Microsoft 365 Service health and Purview audit records to distinguish an Exchange Online incident from a New Outlook for Mac synchronization or rule-driven move.
1. Determine whether the move exists on the server
- Close Outlook for Mac to prevent it from making further changes during the test.
- Open Outlook on the web and inspect both:
- Inbox
- In-Place Archive—the name used for the Online Archive in Outlook on the web.
- Move one noncritical test message from the Inbox into the In-Place Archive.
- Sign out, sign back in, and check whether it stays there.
The Online Archive is a separate mailbox alongside the primary mailbox. Outlook for Mac supports dragging messages between them, while archive policies normally move older messages from the primary mailbox to the archive, not back to the Inbox.^1^
Interpret the result as follows:
- Message stays archived on the web but returns when Outlook for Mac is reopened: investigate the Mac client, another connected client, or a client-side rule.
- Message returns even while Outlook for Mac remains closed: investigate a server-side rule, another connected application/delegate, or a service-side mailbox issue.
- The message is only displayed in the Inbox on the Mac but remains archived on the web: this points to a client synchronization or display issue rather than an actual server-side move.
2. Verify whether last week’s outage is relevant
A public status page cannot confirm whether a previous incident affected this particular tenant. An administrator should open:
Microsoft 365 admin center → Health → Service health → Issue history
Review Exchange Online incidents and advisories from the last 7 or 30 days. Tenant-specific current issues appear under Active issues Microsoft is working on, while resolved incidents are under Issue history.^2^
If an advisory describes archive access, mailbox synchronization, or items moving between folders, follow that advisory and retain its incident ID. Otherwise, the outage should not be assumed to be the cause.
3. Identify what performed the move
For a definitive investigation, search the Microsoft Purview audit log for one or more affected messages. The administrator needs the Audit Logs role and an Exchange Online PowerShell connection. Microsoft documents searches for moved or missing messages, although auditing for owner Move operations might not already be enabled.^3^
$start = (Get-Date).AddDays(-2)
$end = Get-Date
$user = "[Email]"
Search-UnifiedAuditLog `
-StartDate $start -EndDate $end `
-UserIds $user `
-Operations Move,MoveToDeletedItems,Update `
-ResultSize 1000
Examine the matching records for the source and destination folder, operation time, user/logon type, and client information. Audit entries can expose fields such as DestFolderPathName, ClientInfoString, ClientProcessName, ClientVersion, and OperationResult, which help identify whether Outlook, a delegate, or another process initiated the operation.^4^
If no move events appear, check whether owner move auditing was configured:
Get-Mailbox [Email] |
Select-Object AuditEnabled, AuditOwner
Enabling additional auditing helps capture future moves; it will not recreate events that were never logged:
Set-Mailbox [Email] `
-AuditOwner @{Add="Move","MoveToDeletedItems","SoftDelete","HardDelete"}
4. Conditional checks
- If the audit record identifies a rule or the behavior continues with the Mac closed: review Outlook on the web under Settings → Mail → Rules, including rules that move or copy messages. Rule order matters because rules are processed in listed order.^5^
- If the audit identifies another client or delegate: temporarily disconnect that client or revoke the relevant mailbox access, then repeat the web test.
- If only Outlook for Mac reproduces it: install current Office for Mac updates, then test again. Microsoft previously fixed an Outlook for Mac Online Archive access defect through an Office update, although that documented issue concerns archive access rather than messages moving back.^6^
- If no actor is visible and no rule or advisory explains it: open a Microsoft 365 support request with affected message subjects, timestamps, screenshots from Outlook on the web and Mac, audit results, Outlook version, and any relevant service-health incident ID.
References
- Use your online archive with Outlook for Mac | Microsoft Support
- How to check Microsoft 365 service health
- Search the audit log for specific email messages
- How to use mailbox audit logs in Microsoft 365
- The rule I created does not work | Microsoft Support
- The new Outlook for Mac users cannot access Online Archive mailbox | Microsoft Support