# Teams Add pinned apps pane before rollout email

> Check the Add pinned apps pane before you send the rollout email, because the Teams store lists more apps than the policy layer can actually pin.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-add-pinned-apps-pane-before-rollout-email/
- 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: rare
- Budget: free
- Channels: Distribution, Onboarding, Brand Trust
- Stages: teams apps, pin eligibility, admin workflow, rollout trust


## Why this can grow

Teams admins often assume store availability and pinnability are the same thing. Microsoft says they are not. The setup-policy docs note that the Add pinned apps pane only includes apps that can actually be pinned through policy, and on desktop that usually means personal-scope static tabs and bots. That makes the pane a practical launch checklist. If the app is not there, the rollout promise is already wrong. Catching that before the announcement saves support churn and keeps the adoption plan attached to the surfaces the product can really occupy.

## 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 add pinned apps pane before rollout email can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Distribution and Onboarding 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 the Teams store lists all Teams apps, but the Add pinned apps pane includes only the apps that can actually be pinned through policy, including personal-scope static tabs and bots on desktop.

## Adjacent tactics in the same lane

- [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 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 meeting extension follows the organizer policy](/growth-ideas/teams-meeting-extension-follows-the-organizer-policy/) - 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

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