I redesigned how Microsoft Teams admins control external collaboration: 40+ settings across three portals became one overview and three modes, now available worldwide.
320M+people use Microsoft Teams every monthMicrosoft, October 2023
In each organisation, an IT admin decides who outside the company its people can chat, call, meet and share channels with.
Can we work with our new vendor in Teams?
That simple question sent admins through three portals and more than 20 pages, piecing together how roughly 40 settings depended on each other.
Where admins had to look
Chat, calls, meetings and channels
40+ controls across 6+ policies
Identity and cross-tenant access
Teams admins can see it, but not change it
Files
Left for a later milestone
Nothing showed the organisation’s overall stance. One wrong setting could block legitimate work or expose the company, and it was one of the most-criticised areas of Teams administration.
Small business, generalist. Wants a safe default, then wants to get back to work.
Enterprise. Wants transparency, granular control and the freedom to deviate from recommendations.
Nobody sets out to change aninbound access policy. They want towork freely with partners orlock things down.
Rebuilding the policies wasn’t possible before Ignite, so the new experience sits on top of them.
The occasional admin stops at the overview. The expert goes one level deeper.
The familiar way in, now with a summary.
“What is our stance?” Read-only.
“What exactly is set?” Grouped and collapsed.
Each mode sets every policy underneath at once.
Presets show their values as ticks and crosses. Only Custom shows toggles and dropdowns, so nothing looks editable unless it is. Experts can copy a preset into Custom and change only what they need.
So nothing applies silently. Admins see every setting that will change, with its current and new value, before they confirm.
The dialog shows what failed and what saved, and switches the mode to Custom to match. Admins can retry or export a changelog.
An invalid setting gets the platform’s standard warning triangle, with the reason on hover.
If a change needs a Global Administrator, the action stays available and a dialog explains why, instead of a disabled button.
If a setting is changed there, the overview reports Custom mode.
Mode changes apply org-wide only, and every change dialog says so.
A two-page introduction that admins open themselves, so concept explanations stay out of the everyday screens.
| The call | Instead of | Why |
|---|---|---|
| A read-only overview | An editable dashboard | Simple for occasional admins, with room to grow. The cost is one extra click for experts. |
| Presets can’t be partly edited | Editing a preset in place | An edited preset that still says “Open” would mislead. Customers preferred a custom configuration. |
| The mode is the main decision | Mode as a utility behind a menu | Choosing an intent should come before small edits. “Edit settings” became “Change mode”. |
| Organisation-wide scope, for now | Scope by team, domain or organisational unit | Customers asked for it, but it couldn’t be done well by Ignite. |
November 2025, about four months after the first design review.
Customers confirmed strong demand for consolidation, but preferred a persistent summary card on the page they already used over an entry banner. I switched the main page to a status-first design.
A formal review of the live build with 14 participants found 0 blocking issues across 3 core tasks.
It exposed friction in three areas, which fed into the next iteration:
A green success message after copying a preset read as “applied”.
Next iteration: Say plainly that settings are copied, not yet applied.
The option was hidden behind an ellipsis menu.
Next iteration: Bring it to the surface.
Different terms were used for the same idea.
Next iteration: One consistent set of words.
Yes, for chats, calls and meetings.
The overview answers it on one page. In this Controlled-mode example, shared channels are off.
Source: Microsoft 365 Roadmap, ID 523211 (opens in a new tab)
huge
| Before | After |
|---|---|
| 3admin portals | 1unified view |
| 20+configuration pages | 1overview + 1 settings flow |
| 40+controls across 6+ policies | 3modes: Open, Controlled, Custom |
The overview became the foundation for future admin insight on Teams Admin Center.
Switching modes was the hardest interaction to get right, and research caught it late.
Such as time to configure and the split across modes, so impact is measured, not just described.
