Updates 1

Author: Mark Heffernan

articles/search/TOC.yml

@@ -153,7 +153,7 @@
       href: search-howto-schedule-indexers.md
     - name: Map fields
       href: search-indexer-field-mappings.md
-    - name: Connect with managed identities (preview)
+    - name: Connect using managed identities (preview)
       items:
         - name: Managed identities overview
           href: search-howto-managed-identities-data-sources.md

articles/search/search-howto-managed-identities-cosmos-db.md

@@ -90,8 +90,8 @@ The body of the request contains the data source definition, which should includ
 |**type**| Required. Must be `cosmosdb`. |
 |**credentials** | Required. <br/><br/>When connecting using a managed identity, the **credentials** format should be: *Database=[database-name];ResourceId=[resource-id-string];(ApiKind=[api-kind];)*<br/> <br/>The ResourceId format: *ResourceId=/subscriptions/**your subscription ID**/resourceGroups/**your resource group name**/providers/Microsoft.DocumentDB/databaseAccounts/**your cosmos db account name**/;*<br/><br/>For SQL collections, the connection string does not require an ApiKind.<br/><br/>For MongoDB collections, add **ApiKind=MongoDb** to the connection string. <br/><br/>For Gremlin graphs and Cassandra tables, sign up for the [gated indexer preview](https://aka.ms/azure-cognitive-search/indexer-preview) to get access to the preview and information about how to format the credentials.<br/>|
 | **container** | Contains the following elements: <br/>**name**: Required. Specify the ID of the database collection to be indexed.<br/>**query**: Optional. You can specify a query to flatten an arbitrary JSON document into a flat schema that Azure Cognitive Search can index.<br/>For the MongoDB API, Gremlin API, and Cassandra API, queries are not supported. |
-| **dataChangeDetectionPolicy** | Recommended. See [Indexing Changed Documents](#DataChangeDetectionPolicy) section.|
-|**dataDeletionDetectionPolicy** | Optional. See [Indexing Deleted Documents](#DataDeletionDetectionPolicy) section.|
+| **dataChangeDetectionPolicy** | Recommended |
+|**dataDeletionDetectionPolicy** | Optional |
 
 ### 4 - Create the index
 

articles/search/search-howto-managed-identities-data-sources.md

@@ -28,11 +28,9 @@ These concerns can be resolved by using a managed identity to connect to your da
 
 ## Using managed identities
 
-[Managed identities](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) provides Azure services with an automatically managed identity in Azure AD. You can use the identity to authenticate to any service that supports Azure AD authentication. 
+[Managed identities](https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview) is a feature that provides Azure services with an automatically managed identity in Azure AD. Azure Cognitive Search can use this managed identity to allow you to create a data source object with a connection string that does not include an account key or a password. Instead, your Azure Cognitive Search service will connect to the data source using the permissions that you give to its system assigned managed identity.
 
-Azure Cognitive Search can use managed identities to allow you to create a data source object with a connection string that does not include an account key or a password. Instead, the connection string includes a ResourceId and your Azure Cognitive Search service will connect to the data source using the permissions that you give to its system assigned managed identity.
-
-When connecting to a data source using a managed identity, you can change your data source account key or password and your indexers will still be able to connect.
+When connecting to a data source using a managed identity, you can change your data source account key or password and your indexers will still be able to connect. You can also create data source objects in your code without having to include an account key or use Key Vault to retrieve an account key.
 
 ## Next steps