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

[YashikaAgrawal]

Hi,

We are currently working on a Power BI tenant-to-tenant migration from the Infy tenant to the TATA tenant.

Point A

In the Infy tenant, we have three capacities: CAPI, CAPE, and CAP3. Most of our Power BI workspaces are currently hosted in CAP3.

Question:
Once we successfully move all the workspaces from CAP3 to the new TATA tenant, is it recommended to delete the CAP3 capacity from the Infy tenant via the Admin Portal?

What is the best practice for handling unused capacity after workspace migration in a Power BI tenant migration scenario?

Any guidance or official recommendations would be appreciated.

Point B

We are working on a Power BI tenant migration from the Infy tenant to the TATA tenant.

After migrating the workspaces and reports to the TATA tenant, we want to prevent migrated users from creating new workspaces in the Infy tenant.

Specifically:

• Migrated users should not be able to create workspaces in Infy.

• They should not see other workspaces in the Infy tenant.

I have reviewed the Admin portal setting: Create workspaces (enabled for the entire organization)

Are there any other options or best practices to restrict workspace creation in the source tenant for migrated users?

Thanks,

[rohit1991 · Accepted solution]

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.

[v-sdhruv · Accepted solution]

Hi @YashikaAgrawal ,

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

[rohit1991 · Accepted solution]

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.

[YashikaAgrawal]

Thanks for the reply, got 1 doubt, can you please help.

We currently have one workspace in the INFY tenant (e.g., WK1) that includes both INFY and TATA users.

• Users from the TATA tenant who are currently in the INFY tenant will be migrated to the new TATA tenant.

• The same workspace (WK1) will also be migrated to the TATA tenant.

For this WK1 workspace in the TATA tenant, should I create a security group specifically for INFY users and add them in Manage Access to ensure proper permissions?

Thanks,