How to Manage Power BI Reports After a Microsoft 365 Tenant Migration
Question details
The user needs to know how to handle and manage Power BI assets like reports, datasets, and permissions following a Microsoft 365 tenant migration.

- Product
- Microsoft Power BI
- Device & OS
- not provided
- Scenario
- Completing a Microsoft 365 tenant-to-tenant migration and ensuring Power BI assets continue to function correctly.
- Observed behavior
- Power BI reports, datasets, refresh schedules, gateways, permissions, and row-level security configurations become disconnected or lost during the migration process.
Before making changes to your new tenant, ensure you have a complete inventory of all original Power BI workspaces, exported .pbix files, and data gateway configurations.
Recreate and Reconnect Power BI Assets in the New Tenant
Since tenant migrations do not automatically move Power BI configurations, you must manually recreate connections, datasets, and permissions in the target environment.
During a Microsoft 365 tenant migration, Power BI items such as reports, datasets, workbooks, and row-level security (RLS) settings are typically not seamlessly migrated. They must be re-established in the target tenant to restore functionality.
Download the original .pbix files from your source tenant workspaces before the old tenant is deprecated or locked.
Log in to the new Microsoft 365 target tenant and navigate to the Power BI service.
Create new workspaces in the target tenant and publish your saved .pbix files to these environments.
Reconfigure your On-premises Data Gateways and authenticate your data sources to re-establish automated refresh schedules.
Manually reassign sharing permissions to the new tenant user accounts and recreate your row-level security (RLS) roles.

Consult the Official Power BI Community
If you encounter specific configuration errors with datasets or gateways post-migration, the Power BI community forum is the best place for specialized support.
Looking for a simpler office suite? Try WPS Office
Tenant migrations in Microsoft 365 can be complex and resource-intensive. If you're looking for an easier, lightweight alternative for your daily document, spreadsheet, and presentation needs without the overhead of complex tenant management, WPS Office is an excellent choice. It offers powerful data analysis tools and is highly compatible with Microsoft formats.
- 1. Download the software: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install WPS Office: Follow the on-screen instructions to install the suite on your computer.
- 3. Open your files: Launch WPS Office and seamlessly open your existing Microsoft Office files without worrying about formatting issues.

Frequently Asked Questions
Can Power BI reports be automatically migrated during a Microsoft 365 tenant migration?
No, Power BI reports, datasets, and workspaces usually require manual migration or specialized third-party migration tools to move from a source tenant to a target tenant.
What happens to row-level security (RLS) after migrating to a new tenant?
Row-level security configurations are tied directly to the specific users and security groups of the source tenant. You must manually recreate RLS roles and assign them to the new user accounts in the target tenant.
Do I need to reinstall the On-premises data gateway?
Yes, you typically need to reconfigure or reinstall the On-premises data gateway and re-bind your cloud datasets to the new gateway connection in the target tenant.
Will my scheduled dataset refreshes continue to work after the migration?
Scheduled refreshes will fail after a tenant migration until you re-authenticate your data sources and update the connection credentials in the new Power BI environment.




