Back to latest version
Comparing Sep 2, 2025 latest (Feb 18, 2026) Swap

MC795355 - Microsoft Teams admin center: App centric management for app installation and changes to app setup policies

Message Center

Metadata at latest

Last Updated

Feb 18, 2026

Published May 23, 2024

Service

Microsoft Teams

Tag

Major change
Updated message
New feature
Admin impact

Platforms

Desktop

Metadata changes

End date
Dec 21, 2026Apr 30, 2026

Body changes

removed textadded text

Updated September 2, 2025:February 17, 2026: We have updated the content.timeline. Thank you for your patience. 

Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization.

After rollout, app app-centric management will replace Installed apps in the Teams admin center and givelet admins the ability to install apps individually. The Existing Installed apps in your app setup policies will be migrated to app centric management based on your current user and group assignments for each policy. The rest of your settings in app setup policies will remain unchangedintact; however, no new additions will be permitted, and only deletions will continue to work based on app setup policies, including Pinned apps. After this rollout,be allowed. Instead, you can install Teams apps for selected sets of users, groups, or all users indirectly from the organization, and Installed appsrespective app. Other settings in app setup policiespolicies, including Pinned apps, will no longer be available. remain unchanged.

This message is associated with Microsoft 365 Roadmap ID 394274 and 500637.

When this will happen:

App centric management will roll out in fourfollowing General Availability phases.

  • Phase 1 | We will begin rolling this feature for all tenants mid-October 2025 and complete rollout by end of October. phaseMarch 2026 (previously end of February). Phase 1 applies to tenants who meet both conditions: 1) tenants with no Installed apps in the Global app setup policy and 2) tenants with no custom app setup policies created in the Teams admin center. After rollout, these tenants will have app centric management enabled for their app installs. Admins may see the Manage apps page in read-only mode for a short time.
  • Phase 2 | We will begin rolling this feature for all tenants mid-end of October 2025 and complete rollout by end of October. This phase applies toMarch 2026 (previously end of February) for all remaining tenants. This phase will migrate apps installed for users and groups through Installed apps in app setup policies to app centric management.

How this will affect your organization:

Before the rollout: If you install an app to a user, the user cannot actually use an admin preinstalled app if you did not take the additional step to allow the user to use it. After the rollout, if you install an app through app centric management, the user will immediately be able to use the app.

Before the roll out, a user will only have apps installed from a single app setup policy, following the policy resolution precedence rules. After the rollout, if you have multiple custom app setup policies assigned tocan install any number of Teams apps for selected sets of users, groups, or all users or groups, appsin the organization from every policy will be installed to the user or group assigned to that policy, regardless of the policy resolution precedence rules. respective apps.

 Learn more: Preinstall Teams apps for your org users - Microsoft Teams | Microsoft Learn

What you need to do to prepare:

No action needed for Phase 1 tenants. We will update this message with more information before the rollouts for Phases 2 tenants.

You may want to update any relevant documentation as appropriate.

Before rollout, we will update this post with revised documentation.