⚙️🪟🧑💼🔓CP - Teams - Allow other tenant sign-in
What this policy is for 🪄
The counterpart to
⚙️🪟🧑💼CP - Teams - Block other tenant sign-in.
While the block policy slams the door shut, this one hands out a key… but only to members of
🛡️🧑💼👈🔓Group - Multi tenant Teams Allowed users.
Why? 🤔
Sometimes you do need to log into another tenant:
- You’re in the middle of a merger or acquisition and working in a shared Teams environment
- There’s an ongoing cross-tenant migration with channels and files being moved
- You’re on a temporary project inside a partner tenant
Without this policy, you’d be forced into messy workarounds (and we all know how that story ends…).
🛠️ Configuration
Type: Settings Catalog
| Setting | State | Details |
|---|---|---|
| Microsoft Teams → Restrict sign in to Teams to accounts in specific tenants (User) | Disabled | Removes the restriction so Teams can sign into any tenant |
This opens Teams login for all tenants — but only for users who are explicitly assigned this policy.
💡 SuperVision Tip
Manage exceptions centrally via the
🛡️🧑💼👈🔓Group - Multi tenant Teams Allowed users.
With SuperVision:
- Keep group names consistent across tenants
- Add/remove members without touching Intune configs
- Make your blueprint “exception-proof” without creating chaos
👥 Group Assignments
✅ Included:
❌ Excluded:
- (none explicitly) — if they’re not in the group, they stay blocked.
📝 Governance Check
This is not a candy machine.
Only hand out access if:
- There’s a documented business reason (merger, migration, project)
- The customer has signed off in writing
- You review membership regularly and close the door when it’s no longer needed
🧞♂️ Pro tip: Don’t give this key to everyone “just in case.” That’s how you end up with a house party you didn’t plan.