Hi @YashikaAgrawal , Thank you for reaching out to the Microsoft Community Forum.
As @lbendlin suggested, choose option A when downloading. This option includes both the report and the dataset, allowing you to recreate or reconnect it in the new tenant. The other option keeps the live connection pointing to the dataset in Tenant A, which won’t work after the migration.
Power BI content is region-bound, so if Tenant A’s workspace is in North Europe and Tenant B’s is in West US, reports and semantic models won’t connect across those regions. Power BI doesn't support cross-region live connections, so your workspaces and capacities in Tenant B should be created in the same region as they were in Tenant A. This ensures compatibility when reconnecting reports to datasets and avoids broken links or performance issues.
The tenant setting you highlighted about Azure Maps is not relevant here. Instead, make sure users are allowed to download .pbix files and that content publishing, external sharing and Git integration are enabled if needed. There is no tenant setting that allows region bridging, this must be handled by matching regions during deployment.
Once you’ve downloaded the PBIX file with data, publish it to a workspace in Tenant B that resides in the same region. If it originally connected to a semantic model, open the file in Power BI Desktop and update the data source to point to the new model in Tenant B. If you’re managing multiple reports, you can automate the rebinding using the Power BI REST API.
After migration, verify that row-level security settings and refresh schedules are restored, as these don’t carry over with the PBIX file. Once everything is reconnected, your reports will function as expected in the new tenant.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
