Forum Discussion
Power BI Embedded capacity no longer in Azure?
Hi,
I have a number of Power BI Emedded capacities that are assinged for customers use. They are all fine but a recently added on, set to refresh its data at 23:00 or so each night has vanished. Last night I can see an event that the refresh started and that was the last event recorded. No issues. However, the capacity that supported the workspace is no longer in the resource group in azure and its no where to be seen. There is no evidence of removal by anyone or anything?
I have since supplied a new capacity to it and its working but my concern is that this happens again.
Any experience with a capacity just "vanashing" ?
Its a concerning situation.
Thanks
Just want to advise this this issue was resolved on Friday by the Micosoft team at there end. The capacity had failed to be visible in the Azure Portal the duration of the incident. Eventiually it was made visible within the original Resource Group and I was able to to interact with it. As it had been replaced already I was able to suspend it.
So thankfully back to where we were but using the replacement capacity I added to support my workspace after the issue began.
Craig
8 Replies
Building on powerbidev123's Activity Log point -- here's exactly where to look and what you'll find, because an A-SKU capacity doesn't vanish on its own; something issued a delete, and the Activity Log always records who.
Go to the resource group -> Activity Log (or the subscription-level Activity Log if the whole RG is gone), widen the time range to the last 7 days, and filter Operation for "Delete Capacity" / "Microsoft.PowerBIDedicated/capacities/delete". The Caller column tells you whether it was a person, a service principal, or an automation account. That single line usually ends the mystery.
The two causes I see most often for a "nobody touched it" disappearance:
- A cost/automation script that pauses capacities overnight -- if it calls delete instead of suspend, or a Logic App / Automation runbook has the wrong verb, the capacity is gone rather than paused. The Caller will be the service principal or managed identity that runs it. Worth checking since your missing one is the recently added capacity: a new resource that wasn't added to the "don't touch" scope of such a script is the classic victim.
- Something at the subscription/billing layer -- an Azure subscription that lapsed, hit a spending limit, or was moved/cancelled will tear down its resources, and that shows at the subscription Activity Log, not the RG.
To stop the recurrence rather than just explain it: put a Delete lock (CanNotDelete) on the capacity or its resource group -- Settings -> Locks -- and, if these are client-facing and revenue-critical, an Azure Policy denying delete on Microsoft.PowerBIDedicated resources. A lock would have turned last night's silent delete into a failed operation you'd have seen immediately.
Happy to help read the Activity Log entry if you paste the Operation + Caller.
powerbidev123Solution Sage
CrazyCraigo , thats strange. You could check if in your resource group area was there any kind of server outage or maybe check by opening an azure support ticket for investigation.
Although you did check if anyone removed the resource group , you consider checking once the subscription Activity Log export, Log Analytics, or a centralized audit trail if you have one.
v-abhinavmuCommunity Support
Hi CrazyCraigo,
Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to jbarrosPT & powerbidev123 for sharing valuable insights.
Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.
Thank you for being part of the Microsoft Fabric Community.
- v-abhinavmu
Hi CrazyCraigo,
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank youJust want to advise this this issue was resolved on Friday by the Micosoft team at there end. The capacity had failed to be visible in the Azure Portal the duration of the incident. Eventiually it was made visible within the original Resource Group and I was able to to interact with it. As it had been replaced already I was able to suspend it.
So thankfully back to where we were but using the replacement capacity I added to support my workspace after the issue began.
Craig
- v-abhinavmu
Hi CrazyCraigo,
Thank you for the update, Craig. Glad to hear that the capacity is visible again and that the issue has been resolved by the Microsoft team.
We appreciate you sharing the outcome with the community, as it may be helpful to others who experience a similar issue.
Thank you for keeping us updated.
This issue continues to be ongoing. There is not log or record of the items deletion as it wasn't truly deleted. It can be seen in the Fabric Admin portal but does not exist in Azure. As such it has been MS support for a week not and they check in daily but there is no progress/success yet.
- v-abhinavmu
Hi CrazyCraigo,
Thank you for the update and for sharing the additional details.
Since the capacity is still visible in the Fabric Admin portal but not in Azure, and there are no corresponding Azure Activity Log entries, this appears to require further investigation by Microsoft Support. As your support case is already in progress, I recommend continuing to work with the support team, as they have access to backend diagnostics that aren't available through the portal.
Once the root cause is identified, we'd appreciate it if you could share the outcome here, as it may help other community members who encounter a similar issue.
Thank you for your patience, and please let us know if there's any additional information we can help clarify.
