Forum Discussion

YashikaAgrawal's avatar
YashikaAgrawal
Icon for Advocate V rankAdvocate V
1 year ago
Solved

Can't create the workspace Power BI

Hi, We are working on Power BI tenant migration from TATA to Infy tenant. In portal.azure.com(TATA tenant)   a. Earlier "[email protected]" was a Guest and was able to create the Workspace in Power BI....
Need Help
  • ibarrau's avatar
    ibarrau
    1 year ago

    Hi. Make sure the that the tenant has the possibility of creating workspaces enabled. As a Fabric Administrator, you can get in settings - admin portal - tenant settings - create workspaces.

    In there you can make it only possible for the whole tenant or specific security groups:

     

    If the user is a EntraID account and member of the workspace. In addition, that setting allows the user to create. Then it should work. If it's still sending the error, wait for some hours just in case it's some kind of temporal error/bug, otherwise rise a ticket to support.

    I hope that helps,

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

Hi YashikaAgrawal ,

 

This is a common headache after tenant migrations, but it’s usually fixable! Here’s what to check:

1. Admin settings in the new tenant: Go to the Power BI Admin Portal, then Tenant settings > “Create workspaces.”
Make sure workspace creation is enabled and that Tom’s new account (or his security group) is allowed to create workspaces. If this is set to “Specific security groups,” double-check Tom is included.

2. Tom’s account type: Tom needs to be a full member in the new (Infy) tenant, not just a guest. Sometimes after a migration, it takes a little time for new permissions to kick in, so waiting a bit and then trying again can help.

3. Quick troubleshooting steps: Try a different browser or incognito mode. Have Tom sign out and back in to clear any session issues. Try creating the workspace directly from the Power BI Service (web) instead of Desktop.

4. If you still get the error: Sometimes it’s just a temporary glitch after big changes wait 30 60 minutes and try again. Ask your admin if anyone else in the new tenant can create a workspace. If not, it’s almost certainly a tenant setting. Your admin can also check the Microsoft 365 Service Health dashboard for any ongoing issues.

 

If you’ve checked all of the above and it’s still not working, it’s worth raising a support ticket with Microsoft they can look for any backend issues, especially after migrations.