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.
Why this can grow a startup
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.
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.
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
Teams mobile ignores the intended policy when fewer than two apps are pinned and falls back to the existing client configuration.
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, Activation, Mobile is relevant to teams apps, mobile rollout, policy setup and you can run a bounded test with a free 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 Activation, 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: Share of target users completing the product's first-value 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