Skip to content

Commit da1c2bd

Browse files
brendaleePeterCLu
authored andcommitted
Update how to view quota/usage section
1 parent f1c6d2e commit da1c2bd

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/machine-learning/how-to-manage-quotas.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -110,24 +110,24 @@ To set quotas at the workspace level, go to any workspace in your subscription,
110110

111111
## View your usage and quotas
112112

113-
Viewing your quota for various resources, such as Virtual Machines, Storage, Network, is easy through the Azure portal.
113+
Azure Machine Learning Compute quota on your subscription is managed separately from other Azure resources quota. To view this quota, you need to drill down into Machine Learning services.
114114

115-
1. On the left pane, select **All services** and then select **Subscriptions** under the General category.
115+
1. On the left pane, select **Machine Learning service** and then select any workspace from the list shown.
116116

117-
1. From the list of subscriptions, select the subscription whose quota you are looking for.
117+
2. On the next blade, under the **Support + troubleshooting section** select **Usage + quotas** to view your current quota limits and usage.
118118

119-
**There is a caveat**, specifically for viewing the Azure Machine Learning Compute quota. As mentioned above, that quota is separate from the compute quota on your subscription.
119+
3. Select a subscription to view the quota limits. Remember to filter to the region you are interested in.
120120

121-
1. On the left pane, select **Machine Learning service** and then select any workspace from the list shown
121+
4. You can now toggle between a subscription level view and a workspace level view:
122+
+ **Subscription view:** This allows you to view your usage of core quota by VM family, expanding it by workspace, and further expanding it by the actual cluster names. This view is optimal for quickly getting into the details of core usage for a particular VM family to see the break-up by workspaces and further by the underlying clusters for each of those workspaces. The general convention in this view is (usage/quota), where the usage is the current number of scaled up cores, and quota is the logical maximum number of cores that the resource can scale to. For each **workspace**, the quota would be the workspace level quota (as explained above) which denotes the maximum number of cores that you can scale to for a particular VM family. For a **cluster** similarly, the quota is actually the cores corresponding to the maximum number of nodes that the cluster can scale to defined by the max_nodes property.
122123

123-
1. On the next blade, under the **Support + troubleshooting section** select **Usage + quotas** to view your current quota limits and usage.
124+
+ **Workspace view:** This allows you to view your usage of core quota by Workspace, expanding it by VM family, and further expanding it by the actual cluster names. This view is optimal for quickly getting into the details of core usage for a particular workspace to see the break-up by VM families and further by the underlying clusters for each of those families.
124125

125-
1. Select a subscription to view the quota limits. Remember to filter to the region you are interested in.
126+
Viewing your quota for various other Azure resources, such as Virtual Machines, Storage, Network, is easy through the Azure portal.
126127

127-
1. You can now toggle between a subscription level view and a workspace level view:
128-
+ **Subscription view:** This allows you to view your usage of core quota by VM family, expanding it by workspace, and further expanding it by the actual cluster names. This view is optimal for quickly getting into the details of core usage for a particular VM family to see the break-up by workspaces and further by the underlying clusters for each of those workspaces. The general convention in this view is (usage/quota), where the usage is the current number of scaled up cores, and quota is the logical maximum number of cores that the resource can scale to. For each **workspace**, the quota would be the workspace level quota (as explained above) which denotes the maximum number of cores that you can scale to for a particular VM family. For a **cluster** similarly, the quota is actually the cores corresponding to the maximum number of nodes that the cluster can scale to defined by the max_nodes property.
128+
1. On the left pane, select **All services** and then select **Subscriptions** under the General category.
129129

130-
+ **Workspace view:** This allows you to view your usage of core quota by Workspace, expanding it by VM family, and further expanding it by the actual cluster names. This view is optimal for quickly getting into the details of core usage for a particular workspace to see the break-up by VM families and further by the underlying clusters for each of those families.
130+
2. From the list of subscriptions, select the subscription whose quota you are looking for.
131131

132132
## Request quota increases
133133

0 commit comments

Comments
 (0)