Skip to content

Commit 464ac8e

Browse files
committed
move section
1 parent 244838d commit 464ac8e

File tree

1 file changed

+35
-31
lines changed

1 file changed

+35
-31
lines changed

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

Lines changed: 35 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -132,8 +132,42 @@ SSH access is disabled by default. SSH access can't be changed after creation.
132132

133133
[!INCLUDE [ssh-access](../../includes/machine-learning-ssh-access.md)]
134134

135+
135136
---
136137

138+
139+
140+
141+
## Create on behalf of (preview)
142+
143+
> [!IMPORTANT]
144+
> Items marked (preview) below are currently in public preview.
145+
> The preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
146+
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
147+
148+
As an administrator, you can create a compute instance on behalf of a data scientist and assign the instance to them with:
149+
150+
* Studio, using the [Advanced settings](?tabs=azure-studio#advanced-settings)
151+
152+
* [Azure Resource Manager template](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.machinelearningservices/machine-learning-compute-create-computeinstance). For details on how to find the TenantID and ObjectID needed in this template, see [Find identity object IDs for authentication configuration](../healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md). You can also find these values in the Azure Active Directory portal.
153+
154+
* REST API
155+
156+
The data scientist you create the compute instance for needs the following be [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md) permissions:
157+
158+
* *Microsoft.MachineLearningServices/workspaces/computes/start/action*
159+
* *Microsoft.MachineLearningServices/workspaces/computes/stop/action*
160+
* *Microsoft.MachineLearningServices/workspaces/computes/restart/action*
161+
* *Microsoft.MachineLearningServices/workspaces/computes/applicationaccess/action*
162+
* *Microsoft.MachineLearningServices/workspaces/computes/updateSchedules/action*
163+
164+
The data scientist can start, stop, and restart the compute instance. They can use the compute instance for:
165+
* Jupyter
166+
* JupyterLab
167+
* RStudio
168+
* Posit Workbench (formerly RStudio Workbench)
169+
* Integrated notebooks
170+
137171
## Enable idle shutdown (preview)
138172

139173
> [!IMPORTANT]
@@ -236,7 +270,7 @@ Administrators can use a built-in [Azure Policy](./../governance/policy/overview
236270
1. Navigate to Azure Policy in the Azure portal.
237271
2. Under "Definitions", look for the idle shutdown policy.
238272

239-
:::image type="content" source="media/how-to-create-attach-studio/idle-shutdown-policy.png" alt-text="Screenshot for the idle shutdown policy in Azure portal.":::
273+
:::image type="content" source="media/how-to-create-attach-studio/idle-shutdown-policy.png" alt-text="Screenshot for the idle shutdown policy in Azure portal." lightbox="media/how-to-create-attach-studio/idle-shutdown-policy.png":::
240274

241275
3. Assign policy to the necessary scope.
242276

@@ -284,36 +318,6 @@ You can also create your own custom Azure policy. For example, if the below poli
284318
}
285319
```
286320

287-
## Create on behalf of (preview)
288-
289-
> [!IMPORTANT]
290-
> Items marked (preview) below are currently in public preview.
291-
> The preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
292-
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
293-
294-
As an administrator, you can create a compute instance on behalf of a data scientist and assign the instance to them with:
295-
296-
* Studio, using the [Advanced settings](?tabs=azure-studio#advanced-settings)
297-
298-
* [Azure Resource Manager template](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.machinelearningservices/machine-learning-compute-create-computeinstance). For details on how to find the TenantID and ObjectID needed in this template, see [Find identity object IDs for authentication configuration](../healthcare-apis/azure-api-for-fhir/find-identity-object-ids.md). You can also find these values in the Azure Active Directory portal.
299-
300-
* REST API
301-
302-
The data scientist you create the compute instance for needs the following be [Azure role-based access control (Azure RBAC)](../role-based-access-control/overview.md) permissions:
303-
304-
* *Microsoft.MachineLearningServices/workspaces/computes/start/action*
305-
* *Microsoft.MachineLearningServices/workspaces/computes/stop/action*
306-
* *Microsoft.MachineLearningServices/workspaces/computes/restart/action*
307-
* *Microsoft.MachineLearningServices/workspaces/computes/applicationaccess/action*
308-
* *Microsoft.MachineLearningServices/workspaces/computes/updateSchedules/action*
309-
310-
The data scientist can start, stop, and restart the compute instance. They can use the compute instance for:
311-
* Jupyter
312-
* JupyterLab
313-
* RStudio
314-
* Posit Workbench (formerly RStudio Workbench)
315-
* Integrated notebooks
316-
317321
## Schedule automatic start and stop
318322

319323
Define multiple schedules for auto-shutdown and auto-start. For instance, create a schedule to start at 9 AM and stop at 6 PM from Monday-Thursday, and a second schedule to start at 9 AM and stop at 4 PM for Friday. You can create a total of four schedules per compute instance.

0 commit comments

Comments
 (0)