Skip to content

Commit 32a6bd3

Browse files
Merge pull request #120689 from nthewara/patch-11
Add ExpressRoute to KV Trusted Services List
2 parents d2c0ba6 + 562b219 commit 32a6bd3

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,7 @@ Here's a list of trusted services that are allowed to access a key vault if the
6565
| Azure Disk Encryption volume encryption service|Allow access to BitLocker Key (Windows VM) or DM Passphrase (Linux VM), and Key Encryption Key, during virtual machine deployment. This enables [Azure Disk Encryption](../../security/fundamentals/encryption-overview.md).|
6666
| Azure Disk Storage | When configured with a Disk Encryption Set (DES). For more information, see [Server-side encryption of Azure Disk Storage using customer-managed keys](../../virtual-machines/disk-encryption.md#customer-managed-keys).|
6767
| Azure Event Hubs|[Allow access to a key vault for customer-managed keys scenario](../../event-hubs/configure-customer-managed-key.md)|
68+
| Azure ExpressRoute | [When using MACsec with ExpressRoute Direct](../../expressroute/expressroute-howto-macsec.md)|
6869
| Azure Firewall Premium| [Azure Firewall Premium certificates](../../firewall/premium-certificates.md)|
6970
| Azure Front Door Classic|[Using Key Vault certificates for HTTPS](../../frontdoor/front-door-custom-domain-https.md#prepare-your-key-vault-and-certificate)
7071
| Azure Front Door Standard/Premium|[Using Key Vault certificates for HTTPS](../../frontdoor/standard-premium/how-to-configure-https-custom-domain.md#prepare-your-key-vault-and-certificate)

0 commit comments

Comments
 (0)