Skip to content

Commit 7ff4a51

Browse files
committed
Changed name from Azure Super Transport (XT) to Azure Import/Export per @alkohli's request
1 parent f5b03ac commit 7ff4a51

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/key-vault/key-vault-overview-vnet-service-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Here's a list of trusted services that are allowed to access a key vault if the
7272
|Azure Data Factory|[Fetch data store credentials in Key Vault from Data Factory](https://go.microsoft.com/fwlink/?linkid=2109491)|
7373
|Azure Event Hubs|[Allow access to a key vault for customer-managed keys scenario](https://docs.microsoft.com/azure/event-hubs/configure-customer-managed-key)|
7474
|Azure Service Bus|[Allow access to a key vault for customer-managed keys scenario](https://docs.microsoft.com/azure/service-bus-messaging/configure-customer-managed-key)|
75-
|Azure Super Transport (XT)| [Use customer-managed keys in Azure Key Vault for Import/Export service](https://docs.microsoft.com/azure/storage/common/storage-import-export-encryption-key-portal)
75+
|Azure Import/Export| [Use customer-managed keys in Azure Key Vault for Import/Export service](https://docs.microsoft.com/azure/storage/common/storage-import-export-encryption-key-portal)
7676

7777
> [!NOTE]
7878
> You must set up the relevant Key Vault access policies to allow the corresponding services to get access to Key Vault.

0 commit comments

Comments
 (0)