Skip to content

Commit 3776100

Browse files
authored
fix the message to be for Azure Machine Learning workspace resource instead of compute instance resource
it seems mistakenly mentioned that the targeted identity is the compute instance one, however, it should be the identity of the workspace itself.
1 parent 89e0bdf commit 3776100

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/how-to-create-compute-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ A compute instance won't be considered idle if any custom application is running
154154
Also, if a compute instance has already been idle for a certain amount of time, if idle shutdown settings are updated to an amount of time shorter than the current idle duration, the idle time clock is reset to 0. For example, if the compute instance has already been idle for 20 minutes, and the shutdown settings are updated to 15 minutes, the idle time clock is reset to 0.
155155

156156
> [!IMPORTANT]
157-
> If the compute instance is also configured with a [managed identity](#assign-managed-identity), the compute instance won't shut down due to inactivity unless the managed identity has *contributor* access to the Azure Machine Learning workspace. For more information on assigning permissions, see [Manage access to Azure Machine Learning workspaces](how-to-assign-roles.md).
157+
> If the Azure Machine Learning workspace resource is also configured with a [managed identity](#assign-managed-identity), the compute instance won't shut down due to inactivity unless the managed identity has *contributor* access to the Azure Machine Learning workspace. For more information on assigning permissions, see [Manage access to Azure Machine Learning workspaces](how-to-assign-roles.md).
158158
159159
The setting can be configured during compute instance creation or for existing compute instances via the following interfaces:
160160

0 commit comments

Comments
 (0)