Automate Pause and Resume Fabric Capacity with LogicApps, Episode 1; The basics

[@pavlahrabcova391]

Hi, thanks for your videos! please what is api version - where did you get this number?

[@BI.Insight]

Thanks for bringing this to my attention 👍🏼. Just updated the description.

[@vijaydoradla3229]

Which role do we need to assign to the Logic App to manage Fabric capacity pause or resume through the Logic App?

[@BI.Insight]

Thanks for your comment. The user used in the Azure Resource Manager (ARM) operations must at least have Fabric Administrator role. Read more here: learn.microsoft.com/en-us/fabric/enterprise/pause-resume?WT.mc_id=DP-MVP-5003466

[@MatíasEzequielRivara]

im have a problem with short resource id. im put de character "/" but send error badrequest. im look log and seed a wrong path = /Microsoft.Fabric/capacities%2Fabric/resume" change "/" for "%2"

[@BI.Insight]

Hi Matias, Thanks for your comment. On which part of the solution you get the error, on "Read a resource" or "Invoke resource operation"?

[@handschriftonderwijs]

I notice something weird; every time when i try to fill in the Short Resource Id like in the blog and YT video (capacities/fabricname). I constant get a 404 not found. When i look at the logs and check the Inputs i see that it replaces the "/" with "%2F". Why is this? I think this is why the Action can't find it and returns a 404.

[@BI.Insight]

@@handschriftonderwijs Thanks for the comment. I cannot replicate the issue you face. Can you please clarify which operation gives you the error, the "Read a resource" or "Invoke resource operation"?

[@handschriftonderwijs]

@@BI.Insight In this video at 8:03; when i followed it exactly as is (ofcourse not the fabricname); it failed when i checked the run history like in 9:03; the Invoke resource operation was red crossed and was 404 Not Found.

[@BI.Insight]

@@handschriftonderwijs Please ensure your capacity is running. Encoding the "/" to "%2F" is normal and will not cause any issues. I suspect your interval on "Recurrence" is short and runs the workflow before you saved it and while it runs, your capacity is not in "Active" state. That is just a possibility. I suggest you use the "Read a resource" operation before the "Invoke resource operation" to get the status of the capacity first. This has been explained in detail in the second episode of this series: kzbin.info/www/bejne/ZmrJh4V8Zb-kprMsi=jRbpU43nK8gwnaUz