MC688930 - Teams admin center: App centric management and changes to app permission policies

Updated July 5, 2024:April 18, 2025: We have completed Phase 1. Phase 3 (auto-migration) has begun and is updated to define the rollout timeline below. Thank you for your patience.

We are excited to announce thatand cohorts. Phase 2 (self-migration) is also updated and extended to mid-May for the customers who are not in the first round of app auto migration. See below for details.

The migration to app-centric management rollusing the Migration Wizard (Phase 2) started rolling out is scheduled to complete in late JuneNovember 2024 (previously May). This phase will be available to all tenants and can be initiated at the admin’s discretion.

What iscompleted rolling out in phase 2?

• Migration wizard: a step-by-step guide to help you migrate the permission policies. You will bemid-December 2024. Administrators are now able to select which polities to migratestart the migration themselves using the wizard. The automatic migration for customers with only a global permission policy (Phase 1) will complete by end-March 2025 and designate users groups or individuals who should have access to the apps.
• Testing and Validation: before finalizing the migration, you will have the opportunity to test and export your staged changes. You can use this to make side-by-side comparisonthose with your current setup, ensuring everything is perfect before you proceed.
• Duration: The migration process is designed to have no downtime for the end users and can take a few hours to complete. During the migration, your existingmultiple permission policies (Phase 3) will remainbegin in effect until the transition to app centric management completes.

Detailed documentation for the migration process will beis available in our online documentation, which currently includes information on managing apps after ACM migration.at App centric management to manage user access to Teams apps - Microsoft Teams | Microsoft Learn.

App centric management introduces new admin settings to control who in the tenant can install Teams apps. First, admins can set a default value for new apps that are published to the Teams app store. Second, admins can manage apps for users, groups, or everyone in the organization. This feature replaces the existing app permission policies and provides admins with the ability to manage access to the app individually. The app permission policies for existing customers are migrated to maintain existing app availability in the tenant. 

This message is associated with Microsoft 365 Roadmap ID 151829151829 

When this will happen:

This feature will gradually roll out across three major phases.

Phase 1 (from late November 2023 (Complete): Auto-migration for only single policy customers - This is applicable for customer with only a global permission policy. The roll-out has started and will be complete by end of March 2025.

Phase 2: Self-migration – admins of our customers can do self-migration using the Migration Wizard. This is the preferred way for customers to have tenant admin to be in the loop of migration. The migration Wizard is extended until mid-May (previously end of March 2024 (previously late February) affects the tenants that use only the Global app permission policy and have no2025) for customers with one or more custom app permission policies. The app status from the permission policy and tenant settingspolicies with users assigned to them. There will be no further exceptions granted.

Phase 3: Auto-migration for all customers – This is for customers who have not completed self-migration in Phase 2. This has started in mid-April and will complete by mid-May 2025 for customers with custom permission policies, but no users assigned to them. All other customers will be auto-migrated to preserve the admin intent. The starting in mid-May until end of June 2025 (previously starting April 2025).  Auto-migration will not affectmaintain the end users and their ability to use the apps. Admins may see the Manage apps pagesame access defined in a read-only mode for a short time.

Phase 2(early July 2024 (previously late June)) affects the tenants that use both global and custom app permission policies whenever there is no conflict between a user’s assigned policies. This phaseIf a user’s policies conflict by allowing and blocking the same app for them, we will letauto-migrate their app as allowed. After auto-migration, there will be a security group created for each set of users assigned to each app permission policy. These groups will be assigned to each app they are allowed in their respective policy, maintaining their app access. Groups Administrators can manage these groups like any others to customize the admin choose to migrate to app centric management by following a migration process that will changeassignments, such as adding and removing users, or removing the existing app permission policies to app assignments in the new app centric model. The admins will have the choice to modify the apps that are assigned using the custom permission policies to be accessible to groups, if they want. group and replacing it with another.

Phase 3 (more details coming soon as a follow up MC post) applies to the tenants that skipped the migration in phase 1 or 2. These tenants will be migrated automatically in this phase.

How this will affect your organization:

Starting with this release, you can:

1. Manage Teams apps for selected set of users, groups or all users in the organization.

2. Set the default value for new apps published to Teams app store for each of the app types: Microsoft, third-party and custom apps.

What you need to do to prepare:

No action needed for phase 1 tenants with Global permission policy only. More information will. Migrate to app centric management manually via the Migration Wizard provided in Phase 2 by mid-May 2025 (previously the end of March 2025) if you do not want to be provided for phase 2 and 3 tenants in a follow-up communication before launch.auto-migrated during Phase 3.