Forum Discussion

YashikaAgrawal's avatar
YashikaAgrawal
Icon for Post Patron rankPost Patron
1 year ago
Solved

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

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 o...
Need Help
  • rohit1991's avatar
    rohit1991
    1 year ago

    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's avatar
    v-sdhruv
    1 year ago

    Hi YashikaAgrawal ,

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

rohit1991's avatar
rohit1991
Icon for Super User rankSuper User
1 year ago

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's avatar
    YashikaAgrawal
    Icon for Post Patron rankPost Patron
    1 year ago

    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,