March 14, 2025
Microsoft announced the deprecation of the Application Impersonation role in Exchange Online, a move aimed at enhancing security within the platform. This role, traditionally used to grant applications broad access to multiple mailboxes, is being phased out due to its extensive permissions and potential security risks. The deprecation process is as follows:
- May 2024: New assignments of the Application Impersonation role will be blocked.
- February 2025: Complete removal of the Application Impersonation role and its feature set from Exchange Online.
What to do now
Mark, our BitTitan migration expert, has created a tutorial video so you can learn the new steps for assigning access control for your migration. The video begins with setting up endpoints for a MigrationWiz project that involves Microsoft 365 at the source and/or the destination. Then, you’ll see how to use PowerShell to create the management scope, create a new service principle, and assign the management role. After assigning API application permissions and creating a new one-time ‘client secret’ password, you’re ready to proceed with your migration.
Be Ready for the Change
From February 2025, Microsoft has started the depreciation process to remove the Application Impersonation role from O365. Exchange On-premises and Hosted Exchange are not affected by these changes. For further information please see this article.
If you are currently using Application Impersonation for your migrations, it’s only a matter of time before this method becomes obsolete and stops functioning. It is highly recommended that you switch to using the new API permission process to avoid delays in your project due to permission failures.
For MigrationWiz users, this change necessitates a transition to alternative authentication methods to ensure uninterrupted service. MigrationWiz has been proactive in addressing this shift by adopting new APIs that eliminate the need for the Application Impersonation role. Users are advised to utilize PowerShell scripts provided by MigrationWiz to enable these new authentication methods. This approach not only aligns with Microsoft’s security enhancements but also removes the previous requirement of using Global Admin accounts with RBAC Impersonation.
As always, BitTitan also supports your migrations with meticulous documentation. A Knowledge Base article has already been written to guide you through the changes to application impersonation. You can read it here, and use it as a companion for your next Microsoft 365 migration: Replacement to the Retirement of Role-Based Access Control for Applications in Exchange Online.
Migrating Without Application Impersonation
With Application Impersonation no longer available in Exchange Online, IT teams must configure supported application permissions to continue migrating mailboxes. MigrationWiz provides updated authentication workflows that use application permissions, management scopes, and role assignments instead of the retired Application Impersonation role. Administrators can review BitTitan’s Microsoft 365 authentication requirements to configure the appropriate access.
Separately, Microsoft is retiring Exchange Web Services (EWS), prompting changes to how mailbox migrations connect to Exchange Online. BitTitan now offers Microsoft Graph API mailbox migrations for supported scenarios. Organizations should evaluate both authentication requirements and migration compatibility when planning future Exchange Online migrations.
Contact us if you have questions or need help with a migration. You and your team can learn from any video in our expanding tutorial library, anytime.
FAQs About Exchange Online Application Impersonation
Why did Application Impersonation stop working for Exchange Online migrations?
Microsoft removed the Application Impersonation role from Exchange Online in February 2025 because it granted applications broad access to multiple mailboxes. Migration tools that previously relied on this role must use supported application permissions and authentication methods to access Exchange Online mailboxes.
How do I replace Application Impersonation permissions in MigrationWiz?
Administrators should follow BitTitan’s current Exchange Online authentication guidance to configure the required application permissions, management scope, service principal, and role assignments. MigrationWiz provides documentation and PowerShell guidance to help administrators configure access without relying on the retired Application Impersonation role.
Does the Application Impersonation retirement affect on-premises Exchange migrations?
Microsoft’s removal of the Application Impersonation role applies to Exchange Online. The same retirement does not directly affect on-premises or hosted Exchange environments. However, migration authentication requirements vary by source and destination, so administrators should review the appropriate MigrationWiz guide before starting a project.
Why am I getting permission errors after updating my MigrationWiz authentication settings?
Permission errors may occur when application permissions, management scopes, service principals, or role assignments are missing or incorrectly configured. Verify the application registration and confirm that it has access to the required mailboxes. For migrations using EWS, also review the current EWS access requirements and application allow-list settings.
Can MigrationWiz migrate Exchange Online mailboxes without Application Impersonation?
Yes. MigrationWiz supports authentication methods that do not rely on the retired Application Impersonation role. Administrators can configure supported application permissions for eligible migration scenarios. MigrationWiz also offers Microsoft Graph-based mailbox migrations, although supported features and requirements depend on the selected project type.
