Best Practice for Capacity Removal After Power BI Tenant Migration and Prevent Workspace Creation

Hi YashikaAgrawal 

Point A – Removing Capacity After Migration

Yes, once you're 100% sure all workspaces have been migrated from CAP3 to the TATA tenant and nothing is using that capacity anymore, it's safe (and actually recommended) to remove it from the Infy tenant. No point in keeping or paying for unused capacity. Just make sure:

• No datasets or dashboards are still tied to it.
• All workspace owners confirm their content has moved and is working as expected.

Then you can go ahead and delete CAP3 from the admin portal under Capacity settings.

Point B – Preventing Workspace Creation in the Old Tenant

To stop users from creating new workspaces in Infy:

1. Go to Admin Portal >> Tenant settings >> Create workspaces
2. Change it from “Entire org” to just a specific admin group (this stops regular users from creating workspaces).

Also, double-check:

• Remove migrated users from any AAD groups tied to workspace permissions in Infy.
• Optionally, disable their licenses in Infy if they’re fully moved to TATA.

This helps avoid confusion, keeps things clean, and ensures no one accidentally builds reports in the wrong place.

Hi YashikaAgrawal ,

Yes that is a recommended approach for this kind of  cross-tenant scenarios