Forum Discussion
Cannot change Workspace Capacity Tier
Hello,
I'm quite new when it comes to Fabric Admin settings and I cannot find any answer on my issue over this forum. I purchased Fabric, scaled it to F64, I assigned my workspace to Fabric capacity, I literally met all requirements to use Power BI Copilot exept one, my workspace is still assigned to F2. How can I change this?
See on the left there is Azure Portal with Fabric SKU = F64, on the right Admin Portal with workspaces attributes.
Thanks 🙂
Hello mora11
Other users have reported similar issue in this forumhere are some possible solutions :
If the capacity was recently upgraded, wait for at least 24 hours to see if the issue resolves itself
orTry reassigning the Fabric capacity to the workspace. This can sometimes trigger an update in the displayed capacity
If the issue persists, it’s advisable to raise a support ticket with Microsoft for further investigation
please accept this solution if this is helpful
6 Replies
Hello mora11
if I am reading the question and screenshot properly this is what I have understood
- you have created 2 F64 capacity names F64-test and F64-2-test in Azure portal
- you have assigned these capacity to a workspace
- but workspace despite of being assigned to F64 is showing F2
please let me know if my understanding is correct
thanks
The other way around:
- I have created one F64 capacity in Azure portal
- I have assigned two brand new workspaces (names F64-test and F64-2-test) to a capacity
- but workspace despite of being assigned to F64 is showing F2
Hello mora11
are you following the similar steps mentioned here: https://docs.thereportinghub.com/tutorials/embedded-capacity-admin/switching-to-a-fabric-capacity
Hello mora11
Other users have reported similar issue in this forumhere are some possible solutions :
If the capacity was recently upgraded, wait for at least 24 hours to see if the issue resolves itself
orTry reassigning the Fabric capacity to the workspace. This can sometimes trigger an update in the displayed capacity
If the issue persists, it’s advisable to raise a support ticket with Microsoft for further investigation
please accept this solution if this is helpful
