Skip to content

Commit 62acb22

Browse files
author
Larry
committed
fixing text that wasn't showing in rendered page.
1 parent 56b986d commit 62acb22

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/machine-learning/concept-enterprise-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ To enable provisioning a Cosmos DB instance in your subscription with customer-m
178178
> [!NOTE]
179179
> This key vault instance can be different than the key vault that is created by Azure Machine Learning when you provision the workspace. If you want to use the same key vault instance for the workspace, pass the same key vault while provisioning the workspace by using the [key_vault parameter](https://docs.microsoft.com/python/api/azureml-core/azureml.core.workspace(class)?view=azure-ml-py#create-name--auth-none--subscription-id-none--resource-group-none--location-none--create-resource-group-true--sku--basic---friendly-name-none--storage-account-none--key-vault-none--app-insights-none--container-registry-none--cmk-keyvault-none--resource-cmk-uri-none--hbi-workspace-false--default-cpu-compute-target-none--default-gpu-compute-target-none--exist-ok-false--show-output-true-).
180180
181-
This Cosmos DB instance is created in a Microsoft-managed resource group in your subscription. The managed resource group is named in the format <AML Workspace Resource Group Name><GUID>
181+
This Cosmos DB instance is created in a Microsoft-managed resource group in your subscription. The managed resource group is named in the format `<AML Workspace Resource Group Name><GUID>`.
182182

183183
> [!IMPORTANT]
184184
> * If you need to delete this Cosmos DB instance, you must delete the Azure Machine Learning workspace that uses it.

0 commit comments

Comments
 (0)