## TL;DR
Mobile mail paths differ: the account may be connected through a different client or protocol, the Safe Links policy may be assigned per client type, or an older app version renders the original link. Confirm the user is on the supported Outlook mobile app with the work account, check the policy applies to mobile, and test with a fresh message, since already-delivered mail keeps whatever form it arrived in.

```text
link rewrite rule not working on mobile outlook client
```

## Use this when
- Links arrive rewritten on desktop Outlook but original on the same user phone.
- Click protection works in mobile browser mail but not the app.

## Not for this skill when
- The user reads mail in a third party app through basic protocols. Rewriting is applied at delivery; if links are original there, investigate the delivery path, not the app.
- Protection fails on desktop too. That is a tenant policy issue.

## Steps
1. Identify the exact mobile app, version and account type the user uses for work mail. Verify: the client is a supported Outlook mobile build.
2. Send a fresh test mail with a link to that user and inspect it first on mobile. Verify: the new message link form on mobile is observed directly.
3. Review Safe Links policy assignment for client or device conditions that exclude mobile. Verify: no device-based exclusion explains the gap.
4. Check for multiple accounts in the app; personal account mail is governed by different controls and confuses reports. Verify: the report concerns the work account mailbox.
5. After any fix, retest with another fresh message and a click. Verify: the link is rewritten and the click-time check runs on mobile.

## Variant phrasings
### safe links not working outlook mobile app
The mobile app variant.
### link rewriting desktop works mobile does not policy
The client difference variant.

Compatibility: Outlook for iOS and Android with Defender Safe Links policies.

## Why it happens
Rewriting happens at delivery, so the client mostly displays what arrived. Reports of mobile-only failure usually mean the mail arrived through a different path, a different account, or the user compares new desktop mail with old mobile mail delivered before a policy change.

## Edge cases / pitfalls
- Mail delivered before a policy change is never rewritten retroactively. Always test with new mail.
- Shared and delegated mailboxes opened in mobile apps follow their own delivery path. Test the exact mailbox type.
- Keep mobile app versions in support scope; very old builds mishandle rewritten links.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FXv2e4tBN2xP1ZyxntVzCg