Back to GrowthDex
Growth idea action plan

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.

epic tacticlow budget

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.

Company 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 and metric

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.

DistributionMeetingsProduct-led Growthteams appsmeeting extensionhost-led rolloutcollaboration UX
GrowthDex operator note

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.

Founder checklist

  1. Read Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users and identify what is directly supported.
  2. Choose one channel context: Distribution, Meetings, Product-led Growth.
  3. Define the test around Meeting-extension visibility is gated by organizer policy assignment, not by attendee demand alone..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian