Cannot Create Fabric Capacity

[blhart216]

I hope I can get some help here. I think there is a bug in the Azure Portal as I am unable to create a Capacity.  I get these strange authentication errors, and it won't allow me to select a region.  

[NandanHegde]

Based on my understanding, in order to create a fabric capacity the user must have a Power BI licnese associated with him/her.

If your account dosent have any license, request for a free pro license and post that you can proceed with the capacity creation

[v-aatheeque]

Hi @blhart216 

I’m glad to hear the issue seemed to resolve itself earlier. Just to confirm, is everything now working as expected when creating Fabric capacity in the Azure Portal, or are you still encountering any errors?

[v-aatheeque]

Hi @blhart216 

Just to cross-check  since the issue seemed to resolve itself earlier, is everything now working as expected when creating Fabric capacity in the Azure Portal, or are you still experiencing any issues?
I’ll be happy to assist further if needed.

[v-aatheeque]

Hi  @blhart216 
@NandanHegde   Thanks for your prompt response, In addition to that ,

Based on the  above error - "The default location can't be detected because the tenant or user isn't registered to Microsoft Fabric ". Here are few suggestions:

• Your Microsoft 365 tenant does not yet have Fabric enabled.
•  your user account is not licensed/assigned the necessary permissions to create Fabric items (like Lakehouses, Warehouses, Eventhouses, etc.).
• Sometimes, specific regions may not have the capacity available. If you cannot select a region, it might be due to regional capacity limits. Try selecting a different region or check if there are any constraints in the region you are trying to create the capacity in.
• Clear your browser's cache and cookies, or try accessing the Azure Portal in incognito mode. This can sometimes resolve unexpected authentication errors.

  Additonally you can refer this doc :  https://learn.microsoft.com/en-us/fabric/admin/region-availability

  
  Hope this helps !!

[blhart216 · Accepted solution]

It has appeared to self correct.  It was a very strange bug.