# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-meeting-extension-follows-the-organizer-policy/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies)
- GrowthDex source hub: [Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users](/sources/microsoft-learn-use-setup-policies-to-manage-install-and-pin-agents-and-/)
- Last checked: 2026-06-09T06:09:26.000Z
- Rarity: epic
- Budget: low
- Channels: Distribution, Meetings, Product-led Growth
- Stages: teams apps, meeting extension, host-led rollout, collaboration UX


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where teams meeting extension follows the organizer policy can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Distribution and Meetings channel.
3. Use the evidence from learn.microsoft.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Teams admin pins hold the top slot while users experiment below](/growth-ideas/teams-admin-pins-hold-the-top-slot-while-users-experiment-below/) - same source, 1 shared channel, 1 shared stage
- [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) - same source, 1 shared channel, 1 shared stage
- [Teams mobile policy needs two pins before rollout](/growth-ideas/teams-mobile-policy-needs-two-pins-before-rollout/) - same source, 1 shared channel, 1 shared stage
- [Teams Add pinned apps pane before rollout email](/growth-ideas/teams-add-pinned-apps-pane-before-rollout-email/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Teams rollout should survive the policy layer](/blog/the-teams-rollout-should-survive-the-policy-layer/) - enterprise rollout, distribution, product-led growth

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.