Updated TOC and anchor links

Author: seesharprun

articles/cosmos-db/cassandra/TOC.yml

@@ -415,7 +415,9 @@
         - name: Restrict user access to data operations only
           href: ../how-to-restrict-user-data.md
         - name: Configure customer-managed keys
-          href: ../how-to-setup-cmk.md
+          href: ../how-to-setup-customer-managed-keys.md
+        - name: Configure cross-tenant customer-managed keys
+          href: ../how-to-setup-cross-tenant-customer-managed-keys.md
         - name: Use a managed identity
           href: ../how-to-setup-managed-identity.md
     - name: Monitor

articles/cosmos-db/graph/TOC.yml

@@ -314,7 +314,9 @@
         - name: Restrict user access to data operations only
           href: ../how-to-restrict-user-data.md
         - name: Configure customer-managed keys
-          href: ../how-to-setup-cmk.md
+          href: ../how-to-setup-customer-managed-keys.md
+        - name: Configure cross-tenant customer-managed keys
+          href: ../how-to-setup-cross-tenant-customer-managed-keys.md
         - name: Use a managed identity
           href: ../how-to-setup-managed-identity.md
     - name: Manage Azure Cosmos DB resources

articles/cosmos-db/how-to-setup-cross-tenant-customer-managed-keys.md

@@ -93,7 +93,7 @@ Register-AzResourceProvider @parameters
 
 Up to this point, you've configured the multi-tenant application on the service provider's tenant. You've also installed the application on the customer's tenant and configured the key vault and key on the customer's tenant. Next you can create an Azure Cosmos DB account on the service provider's tenant and configure customer-managed keys with the key from the customer's tenant.
 
-You must use an existing user-assigned managed identity to authorize access to the key vault when you configure customer-managed keys while creating the Azure Cosmos DB account. The user-assigned managed identity must have appropriate permissions to access the key vault. As the key vault is on another tenant, we'll use the multi tenant application created previously and register the user assigned managed identity as a federated identity of this multi-tenant application. For more information, see the [Phase 3 - The service provider encrypts data in an Azure resource using the customer-managed key](#phase-3---The-service-provider-encrypts-data-in-an-azure-resource-using-the-customer-managed-key) section of this article.
+You must use an existing user-assigned managed identity to authorize access to the key vault when you configure customer-managed keys while creating the Azure Cosmos DB account. The user-assigned managed identity must have appropriate permissions to access the key vault. As the key vault is on another tenant, we'll use the multi tenant application created previously and register the user assigned managed identity as a federated identity of this multi-tenant application. For more information, see the [Phase 3 - The service provider encrypts data in an Azure resource using the customer-managed key](#phase-3---the-service-provider-encrypts-data-in-an-azure-resource-using-the-customer-managed-key) section of this article.
 
 Whenever a new version of the key is available in the key vault, it will be automatically updated on the Azure Cosmos DB account.
 

articles/cosmos-db/mongodb/TOC.yml

@@ -469,7 +469,9 @@
         - name: Restrict user access to data operations only
           href: ../how-to-restrict-user-data.md
         - name: Configure customer-managed keys
-          href: ../how-to-setup-cmk.md
+          href: ../how-to-setup-customer-managed-keys.md
+        - name: Configure cross-tenant customer-managed keys
+          href: ../how-to-setup-cross-tenant-customer-managed-keys.md
         - name: Use a managed identity
           href: ../how-to-setup-managed-identity.md
     - name: Monitor

articles/cosmos-db/sql/TOC.yml

@@ -1073,7 +1073,9 @@
             - name: Use Always Encrypted
               href: ../how-to-always-encrypted.md
             - name: Configure customer-managed keys
-              href: ../how-to-setup-cmk.md
+              href: ../how-to-setup-customer-managed-keys.md
+            - name: Configure cross-tenant customer-managed keys
+              href: ../how-to-setup-cross-tenant-customer-managed-keys.md
             - name: Access Azure Key Vault with managed identity
               href: ../access-key-vault-managed-identity.md
         - name: Managed Identity

articles/cosmos-db/table/TOC.yml

@@ -352,7 +352,9 @@
         - name: Restrict user access to data operations only
           href: ../how-to-restrict-user-data.md
         - name: Configure customer-managed keys
-          href: ../how-to-setup-cmk.md
+          href: ../how-to-setup-customer-managed-keys.md
+        - name: Configure cross-tenant customer-managed keys
+          href: ../how-to-setup-cross-tenant-customer-managed-keys.md
         - name: Use a managed identity
           href: ../how-to-setup-managed-identity.md
     - name: Enterprise readiness