Forum Discussion
Power BI Embedded capacity no longer in Azure?
- 2 months ago
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
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.