Merge pull request #786 from Blackmist/removing-azureml-stuff

updates per PM

Author: prmerger-automator[bot]

articles/ai-services/encryption/cognitive-services-encryption-keys-portal.md

@@ -27,20 +27,6 @@ Azure AI is built on top of multiple Azure services. While the data is stored se
         * unwrap key
         * get
 
-        For example, the managed identity for Azure Cosmos DB would need to have those permissions to the key vault.
-
-## How metadata is stored
-
-The following services are used by Azure AI to store metadata for your Azure AI resource and projects:
-
-|Service|What it's used for|Example|
-|-----|-----|-----|
-|Azure Cosmos DB|Stores metadata for your Azure AI projects and tools|Flow creation timestamps, deployment tags, evaluation metrics|
-|Azure AI Search|Stores indices that are used to help query your AI studio content.|An index based off your model deployment names|
-|Azure Storage Account|Stores artifacts created by Azure AI projects and tools|Fine-tuned models|
-
-All of the above services are encrypted using the same key at the time that you create your Azure AI resource for the first time, and are set up in a managed resource group in your subscription once for every Azure AI resource and set of projects associated with it. Your Azure AI resource and projects read and write data using managed identity. Managed identities are granted access to the resources using a role assignment (Azure role-based access control) on the data resources. The encryption key you provide is used to encrypt data that is stored on Microsoft-managed resources. It's also used to create indices for Azure AI Search, which are created at runtime.
-
 ## Customer-managed keys
 
 When you don't use a customer-managed key, Microsoft creates and manages these resources in a Microsoft owned Azure subscription and uses a Microsoft-managed key to encrypt the data. 
@@ -53,14 +39,13 @@ When you use a customer-managed key, these resources are _in your Azure subscrip
 These Microsoft-managed resources are located in a new Azure resource group is created in your subscription. This group is in addition to the resource group for your project. This resource group contains the Microsoft-managed resources that your key is used with. The resource group is named using the formula of `<Azure AI resource group name><GUID>`. It isn't possible to change the naming of the resources in this managed resource group.
 
 > [!TIP]
-> * The [Request Units](/azure/cosmos-db/request-units) for the Azure Cosmos DB automatically scale as needed.
 > * If your AI resource uses a private endpoint, this resource group will also contain a Microsoft-managed Azure Virtual Network. This VNet is used to secure communications between the managed services and the project. You cannot provide your own VNet for use with the Microsoft-managed resources. You also cannot modify the virtual network. For example, you cannot change the IP address range that it uses.
 
 > [!IMPORTANT]
 > If your subscription does not have enough quota for these services, a failure will occur.
 
 > [!WARNING]
-> Don't delete the managed resource group that contains this Azure Cosmos DB instance, or any of the resources automatically created in this group. If you need to delete the resource group or Microsoft-managed services in it, you must delete the Azure AI resources that uses it. The resource group resources are deleted when the associated AI resource is deleted.
+> Don't delete the managed resource group any of the resources automatically created in this group. If you need to delete the resource group or Microsoft-managed services in it, you must delete the Azure AI resources that uses it. The resource group resources are deleted when the associated AI resource is deleted.
 
 The process to enable Customer-Managed Keys with Azure Key Vault for Azure AI services varies by product. Use these links for service-specific instructions: