Fabric Built-in Roles (RBAC)

[Madhusmita1012]

Can we have a built-in RBAC implemented for Fabric.

In our Org we had a requirement to restrict users from updating the Fabric Capacity admins while at the same time, they should be allowed to change the SKU size.

Since both the operation SKU and Capacity Admin update use the same type:

"type": "Microsoft.Fabric/capacities",

The IAM Actions Microsoft.Fabric/capacities/write is able to update both SKU and Capacity Admin.

Is there a possibility for the PG Team to segregate the IAM actions for both SKU and capacity admins? Something like this:

For SKU Updates - Microsoft.Fabric/capacities/skus/(read/write).

For capacity Admins Updates - Microsoft.Fabric/capacities/admins/(read/write).

[Jonathan_Garris]

Thanks for your suggestion!