CrowdStrike affecting fabric capacity?

[Anonymous]

Hi,

Is CrowdStrike incident affecting fabric capacities?
I could not resume our dev capacity so I removed it and now I cannot deploy another capacity 😂

I realized this could be a separate issue since I cannot resume our prod capacity either but I don't see any status update neither in Fabric nor in Azure service health !!

[Anonymous · Accepted solution]

Hi @Anonymous ,

We have reported this issue and submitted it to the product team. They have been aware of the issue and the engineers will do their best to resolve it.

This issue is expected to be fixed in around two weeks, so please be patient.

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Corar]

@Anonymous A question, since the softdelete will hit in 7 day for him and for me, is there a way to hold that for the case that the capacity is deleted and cannot be added (s. below). 

[Corar]

It is now possible to create, resume/stop capacity again, but when we try to reattach, it gives a Generic Migration error, independent of what we choose during reattach (Worspace Settings -> License -> Fabric Capacity:

PowerBICapacityFoldersMigrationGenericArtifactsMigrationOtherErrorException

[Corar]

So capacity can be created again, resumed/stoped, but the reattach does noch work, independent of region/large/small model:

[Corar]

Same here, opened a Ticket and problem was unknow to support so far. Really would like to repdeploy before we hit 7days grace period..

[Anonymous]

Now I can resume the capacity but can't assign it my workspace  Couldn't resume our prod capacity now
I have 2 days worth of work inside, that I hadn't commited to git yet 🙁

[Corar]

Yeah also still cannot create one