# Teams mobile policy needs two pins before rollout

> Pin at least two apps in the policy before you announce a mobile rollout, or Teams mobile may keep showing the old configuration instead of the setup you thought you shipped.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-mobile-policy-needs-two-pins-before-rollout/
- 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, Activation, Mobile
- Stages: teams apps, mobile rollout, policy setup, activation


## Why this can grow

A lot of enterprise rollouts get judged against the wrong screen because desktop and mobile do not honor the policy the same way. Microsoft's setup-policy docs are explicit here: Teams mobile needs at least two pinned apps, and if the policy has fewer than two, the mobile client keeps its existing configuration. That matters because a mobile-heavy team can interpret the rollout as broken even when the admin center says the policy is live. The safer move is to treat the second pin as part of launch readiness, not as optional polish.

## 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. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. 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 mobile policy needs two pins before rollout can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Distribution and Activation 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 Teams mobile on iOS and Android requires at least two pinned apps in the policy or the mobile client keeps the existing configuration instead of reflecting the new policy settings.

## Adjacent tactics in the same lane

- [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) - same source, 2 shared channels, 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
- [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

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