safe links rewrite broken for teams meeting invite links

TL;DR

Meeting join links are long, parameter-heavy URLs that some rewrite and scanning flows mangle: parameters get re-encoded, the click-time scan redirects in a way the Teams client rejects, or the invite was generated before a policy change. Test the raw and rewritten forms, and use the documented approach for meeting links, typically adding the meeting domains to the do-not-rewrite list so invites work while other links stay protected.

safe links rewrite broken for teams meeting invite links

Use this when

• Users cannot join Teams meetings from rewritten invite links in mail or calendar.
• The same invite works when the original link is pasted directly.

Not for this skill when

• Invites from one external sender fail while internal invites work. Investigate that sender formatting separately.
• The meeting link opens a phishing page. That is a lure, not a rewriting bug; do not exclude it.

Steps

1. Extract the original join URL from an invite and the rewritten version a user received, and compare them parameter by parameter. Verify: the exact corruption or redirect difference is visible.
2. Test the rewritten link in the same client the user used, since web and desktop clients handle the scan redirect differently. Verify: the failure reproduces on the affected client.
3. Check the current vendor guidance for Teams meeting domains and Safe Links, and compare with your do-not-rewrite list. Verify: required meeting domains are present or missing as suspected.
4. Add the meeting service domains to the do-not-rewrite list, keeping the list limited to those domains. Verify: only meeting links bypass rewriting after the change.
5. Create a fresh meeting, receive the invite by mail, and join through the received link. Verify: joining succeeds end to end.

Variant phrasings

safe links breaks teams meeting join url

The Teams-specific variant.

do not rewrite list meeting invite links outlook

The exclusion list variant.

Compatibility: Defender Safe Links with Microsoft Teams meeting URLs and Outlook calendar invites.

Why it happens

Safe Links inserts itself between click and destination. Applications that parse their own deep links strictly, as meeting clients do, can reject the detour or the altered parameters, so vendors carve out their own meeting domains from rewriting while keeping general scanning.

Edge cases / pitfalls

• Calendar invites generated before the policy change keep the old rewritten links. Test with new invites.
• Third party meeting platforms have their own domains; add them deliberately, one platform at a time.
• Bypassing rewrite for meeting domains is the vendor intended trade-off. Phishing meeting lures still face sender and content checks.

Provenance

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

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

Thread query: safe links rewrite broken for teams meeting invite links

TL;DR: Meeting join links are long, parameter-heavy URLs that some rewrite and scanning flows mangle: parameters get re-encoded, the click-time scan redirects in a way the Teams client rejects, or the invite was generated before a policy change. Test the raw and rewritten forms, and use the documented approach for meeting links, typically adding the meeting domains to the do-not-rewrite list so invites work while other links stay protected.