Workspaces, reports, datasets and their data sources migrate from one Microsoft 365 tenant to another as one audited run — credentials re-entered, every report rebound, every lineage intact on the other side.
The same run you just watched, as the log the app writes while it works — one line per asset, status updated live. Hand it to the acquiring side's IT team on day one.
A report goes across with every dataset and data source it depends on, the way a .pbix publishes. A dataset already on the destination is reused, not duplicated — the report is rebound to it.
Each new data source on the destination gets its credentials set through Power BI's own gateway and credential APIs. Nothing is extracted from the source tenant.
Reports and composite datasets that depend on a dataset elsewhere are re-linked to the migrated copy on the destination — the step that fails silently when done by hand.
Every migrated report is opened and checked against its source before the run reports success.
Nothing changes hands. The migration runs under your own identity, in your browser, through Microsoft's own APIs. Your admins keep every permission, your data never leaves your two tenants, and when the run ends there is no account, token or copy of ours left behind.