Skip to content

Commit c7fbb98

Browse files
authored
Update how-to-create-compute-instance.md
1 parent a5b2285 commit c7fbb98

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -428,6 +428,9 @@ As an administrator, you can create a compute instance on behalf of a data scien
428428

429429
* [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 Microsoft Entra admin center.
430430

431+
To further enhance security, when you create a compute instance on behalf of a data scientist and assign the instance to them, single sign on (SSO) will be disabled.
432+
The assigned to user needs to enable SSO on compute instance themselves after the compute is assigned to them.
433+
431434
## Assign managed identity
432435

433436
You can assign a system- or user-assigned [managed identity](../active-directory/managed-identities-azure-resources/overview.md) to a compute instance, to authenticate against other Azure resources such as storage. Using managed identities for authentication helps improve workspace security and management. For example, you can allow users to access training data only when logged in to a compute instance. Or use a common user-assigned managed identity to permit access to a specific storage account.

0 commit comments

Comments
 (0)