# Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users

- Canonical HTML: https://growth.iangoh.com/sources/microsoft-learn-use-setup-policies-to-manage-install-and-pin-agents-and-/
- Original source: https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies
- Domain: learn.microsoft.com
- Latest check: 2026-06-09
- Channels: Activation, Brand Trust, Distribution, Meetings, Mobile, Onboarding, Product, Product-led Growth, Retention

## Cited GrowthDex tactics

- [Teams Add pinned apps pane before rollout email](/growth-ideas/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.
- [Teams admin pins hold the top slot while users experiment below](/growth-ideas/teams-admin-pins-hold-the-top-slot-while-users-experiment-below/) - Turn on user pinning only after the admin pins define the default path, so teams can personalize the surface without burying the core workflow you need adopted first.
- [Teams meeting extension follows the organizer policy](/growth-ideas/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.
- [Teams mobile policy needs two pins before rollout](/growth-ideas/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.
- [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) - Treat admin pinning as part of distribution, not IT cleanup, so the app lands in the app bar or compose area where repeat usage can actually happen.

## Related reading

- [GrowthDex Blog](/blog/)
- [All growth ideas](/growth-ideas/index.md)