Teams meeting extension follows the organizer policy
Assign the policy to the meeting organizer group before you pitch in-meeting collaboration, because the extension only appears in meetings organized by users with that policy.
Why this can grow a startup
Meeting products often get marketed to attendees while the real gate sits with the organizer. Microsoft spells that out in the setup-policy docs. When apps are pinned for specific users, the meeting extension is available only in meetings organized by users assigned that policy, though other participants can use it inside those meetings. That changes the growth motion. The first distribution target is not everyone in the company. It is the hosts who create the rooms where the app can appear. If the organizer never gets the policy, the rest of the audience never sees the experience you promoted.
Source-backed example
Microsoft says a pinned meeting extension is available only in meetings organized by users assigned the app setup policy, while other participants can access it inside those meetings.
Source-reported evidence
Source: Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users · Browse Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users tactics
Meeting-extension visibility is gated by organizer policy assignment, not by attendee demand alone.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Distribution, Meetings, Product-led Growth is relevant to teams apps, meeting extension, host-led rollout and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Distribution and Meetings, using evidence from Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.
SOURCE HUB
More tactics from Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users
Explore related GrowthDex examples and evidence connected to Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users.
Open Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users source hub