Forum Discussion
Fabric Capacity Auto pause capability
- 1 year ago
Hi Srisakthi ,
Currently, there is no built-in feature to schedule pausing Fabric Capacity directly within the platform, similar to the VM auto shutdown feature. However, you can achieve this through automation using REST APIs.
Azure Automation:
- Create a runbook that runs on a timer to invoke the suspend or resume operations at specified intervals.
- You can use Azure Data Factory to orchestrate this process. Set up a pipeline in ADF that includes a web activity to call the Azure Automation runbook. This way, you can manage the scheduling and execution of the runbook through ADF.
Fabric Pipeline:
- Similarly, you can create a pipeline within Fabric to manage the pausing and resuming of capacity. Use a web activity within the Fabric pipeline to call the necessary REST APIs for suspending or resuming operations.
Regards,
Shreya
Hello,
Thanks to all for your questions and answer.
I tried to develop a logic app to start/suspend the fabric capacity at specific times but I don't find the right syntax for the start/suspend. The scheme is the following:
- Recurrence
- Condition: is day of week
- If no then nothing
- If yes start capacity (action name = API REST Start)
- Delay of 1h time for the required tasks to run
- Suspend capacity (action name = API REST Suspend)
Unfortunately, the syntax of the action does not seem to work. Does anyone know what the right syntax is (or if there is something wrong even before) ?
Thanks in advance for your help.
Guillaume
- Shreya_Barhate1 year agoResolver II
Hi Anonymous
The logic app structure you've outlined is on the right track. Just a quick note on the action names:
- To reactivate a paused Fabric capacity, use the action name Resume (not Start).
- To pause the capacity, use the action name Pause (instead of Suspend).
These are the correct terms used in the Fabric REST API for managing capacity states. Also, ensure that your Logic App is properly authenticated and that the API calls include the required headers and permissions.
Thanks and Regards,
Shreya- Anonymous1 year agoNot applicable
Thanks, it all works well ! The trick was also to correct the adress of the capacity with "capacities\[name of the capacity]".