Forum Discussion
west us 2 outage
Hi! is there any possibility that the capacities allocated in WEST US 2 were not available for more than 5 hours from now?
Hi jrapanelli.,
The CapacityNotActive error doesn't by itself confirm a West US 2 outage. Microsoft documents this error when the workspace isn't connected to an active Fabric capacity, or when the capacity is experiencing an issue that prevents Fabric operations.
I would first confirm that the capacity still shows as Active in Azure and that the workspace is still assigned to it. Microsoft's Fabric capacity troubleshooting guidance lists paused/suspended capacities and capacity-side issues among the possible causes.
For a regional/service incident, I would check Azure Service Health rather than relying only on the public Azure status page. Service Health is personalized to your subscription and region, so it can show incidents that aren't published as a broad public outage. The Fabric Service Status page is worth checking as well.
If the capacity is definitely active and multiple workspaces/users on the same West US 2 capacity are seeing this for several hours, I would open a Microsoft support ticket and include the request ID and session ID from the error details.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
3 Replies
v-sathmakuriCommunity Support
Hi jrapanelli ,
Could you check the suggestion provided above and let us know if you have any additional queries?
Thanks!!
- v-sathmakuri
Hi jrapanelli ,
Could you review the suggestion provided above and let us know if you have any additional questions, we are happy to address.
Thanks!!
- ShivekMaharaj
Community Champion
Hi jrapanelli.,
The CapacityNotActive error doesn't by itself confirm a West US 2 outage. Microsoft documents this error when the workspace isn't connected to an active Fabric capacity, or when the capacity is experiencing an issue that prevents Fabric operations.
I would first confirm that the capacity still shows as Active in Azure and that the workspace is still assigned to it. Microsoft's Fabric capacity troubleshooting guidance lists paused/suspended capacities and capacity-side issues among the possible causes.
For a regional/service incident, I would check Azure Service Health rather than relying only on the public Azure status page. Service Health is personalized to your subscription and region, so it can show incidents that aren't published as a broad public outage. The Fabric Service Status page is worth checking as well.
If the capacity is definitely active and multiple workspaces/users on the same West US 2 capacity are seeing this for several hours, I would open a Microsoft support ticket and include the request ID and session ID from the error details.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.