Forum Discussion
Post PatronWorking with Fabric Capacities
Hello,
Once a capacity is created can I:
1) Rename it?
2) Change its Compute Power (like F2->F4)?
3) How about scaling down ? from F4->F2?
4) What do you do from a goverance perspective with the capacities? how often do you check if a capacity is not needed anumore? and which actions do you do? delete it? pause it?
Thank you,
Pedro
Hi fabricpribeiro, I think deborshi_nag already gave the "to-the-point" answers to your questoins! I'm just want to add some precisions/extra-help on some:
Once a capacity is created can I:
1) Rename it? - Nop , Paid capacities are live in Azure and Fabric uses these resources, in general, azure resources CANNOT BE RENAME with just few exceptions like Azure SQL Databases... Fabric capacities is not one of these exceptions, hence, can't be renamed.
2) Change its Compute Power (like F2->F4)? Yes, you can scale your capacities up or down, from azure portal, locate your capacity and go to Change size as shown on the picture below.
4) What do you do from a goverance perspective with the capacities? Simple rules of thumb... always islotate development from production, that is create one capacity for development and another one for production and monitor usage, start simple with Enable Workspace Monitoring in Microsoft Fabric - Microsoft Fabric | Microsoft Learn
5) how often do you check if a capacity is not needed anumore? The first think I need you to understand is that Fabric capacities ARE NOT PAY-AS-YOU-GO! Simple example, let' say you create an F2 capacity in Azure ($350.40 USD Month) and you let it be there for the whole month, but you don't use any Fabric services during this period ... you still will get a bill for $350.40 at the of the month! That being said and if I'm the person paying the bills, I WOULD CHECK AT LEAST ONCE A DAY, perhaps even more than once 😅
I hope you get my point, fabric capacities are expensive and should be closely monitored! How often? perhaps the person paying the bills should answer this 😋
6) and which actions do you do? delete it? pause it? In terms of what you can do, do both! If you are not using it DELETE IT! It's very easy to create a new one and the risk of leaving an unused capacity active for the whole month and paying for it is to great, so drop it and only keep the ones YOU KNOW ARE IN USE AND WILL BE CLOSED MONITORED, and with those, when not in use Pause them 😉
Hope you find this extra information useful! If so, a kudos will be nice and if you mark this also a part of the solution, will be great to ... all the best mate.
2 Replies
- deborshi_nag
Super User
Hello fabricpribeiro
1) No, you can't rename your Fabric capacity. Premium capacities allowed that, Fabric capacities don't!
2) Yes. You can scale a Fabric F‑SKU capacity up or down in the Azure portal (Change size > Resize).
3) Yes, however, if the capacity is busy, Fabric may postpone the change until resources are available.
4) Perform the following as and when required -
a) Monitor CU consumption and throttling using Capacity Metrics App
b) Check workspaces assigned per capacity to identify idle capacities, move workspaces between capacities
c) Pause capacity out of business hours, note - this is only applicable to PAYG capacities
Please refer to this Microsoft documentation page for Capacity Metric Apps
What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn
- svenchio
Hi fabricpribeiro, I think deborshi_nag already gave the "to-the-point" answers to your questoins! I'm just want to add some precisions/extra-help on some:
Once a capacity is created can I:
1) Rename it? - Nop , Paid capacities are live in Azure and Fabric uses these resources, in general, azure resources CANNOT BE RENAME with just few exceptions like Azure SQL Databases... Fabric capacities is not one of these exceptions, hence, can't be renamed.
2) Change its Compute Power (like F2->F4)? Yes, you can scale your capacities up or down, from azure portal, locate your capacity and go to Change size as shown on the picture below.
4) What do you do from a goverance perspective with the capacities? Simple rules of thumb... always islotate development from production, that is create one capacity for development and another one for production and monitor usage, start simple with Enable Workspace Monitoring in Microsoft Fabric - Microsoft Fabric | Microsoft Learn
5) how often do you check if a capacity is not needed anumore? The first think I need you to understand is that Fabric capacities ARE NOT PAY-AS-YOU-GO! Simple example, let' say you create an F2 capacity in Azure ($350.40 USD Month) and you let it be there for the whole month, but you don't use any Fabric services during this period ... you still will get a bill for $350.40 at the of the month! That being said and if I'm the person paying the bills, I WOULD CHECK AT LEAST ONCE A DAY, perhaps even more than once 😅
I hope you get my point, fabric capacities are expensive and should be closely monitored! How often? perhaps the person paying the bills should answer this 😋
6) and which actions do you do? delete it? pause it? In terms of what you can do, do both! If you are not using it DELETE IT! It's very easy to create a new one and the risk of leaving an unused capacity active for the whole month and paying for it is to great, so drop it and only keep the ones YOU KNOW ARE IN USE AND WILL BE CLOSED MONITORED, and with those, when not in use Pause them 😉
Hope you find this extra information useful! If so, a kudos will be nice and if you mark this also a part of the solution, will be great to ... all the best mate.
