Skip to content

Latest commit

 

History

History
57 lines (36 loc) · 2.01 KB

README.md

File metadata and controls

57 lines (36 loc) · 2.01 KB
Raw

Microsoft Fabric Management Function App

This Azure Function paused your Microsoft Fabric capacity on a daily basis (at 18:01 UTC).

It first checks the current state. If the capacity is running, the capacity is paused.

Blog post

How to use this Azure Function in combination with Microsoft Fabric is explained in this blog post.

Credits

This Azure function uses the REST API as found here.

Check out that repository for more details.

The repository, maintained by Kasper Kirkegaard, offers automated solutions using Azure Data Factory and Fabric data pipelines.

Entra ID application

The Entra ID application, needed to get access to the service, can be acquired via the command line:

az ad sp create-for-rbac -n msftfabriccontributor

Just run it on the command line in the Azure portal.

This will result in a JSON message that looks like this:

{
  "application client Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "displayName": "msftfabriccontributor",
  "password": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "directory tenant Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

I have taken the liberty to make the clientId and tenantId more descriptive.

Contributor role for the Entra ID application

Give the Entra ID application contributor access to the Capacity so it can read and alter the state.

Application settings

The Azure Function expects a number of Azure function application settings:

  • apiVersion -> at this moment 2022-07-01-preview
  • appId -> from RBAC message
  • dedicatedCapacityName -> Resource name your Capacity
  • password -> from RBAC message
  • resourceGroupName -> name of the resource group your Capacity is living in
  • subsciptionId -> from RBAC message
  • tennant -> from RBAC message