Skip to content

Commit bfc38c9

Browse files
committed
[APIM] Cred mgr in VNet
1 parent c1cec04 commit bfc38c9

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

articles/api-management/credentials-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about using credential manager in Azure API Management to cre
44
author: dlepow
55
ms.service: azure-api-management
66
ms.topic: concept-article
7-
ms.date: 09/25/2025
7+
ms.date: 04/10/2026
88
ms.author: danlep
99
ms.custom: references_regions
1010
---
@@ -129,9 +129,9 @@ At runtime, API Management can't fetch new tokens, and an error occurs.
129129

130130
* If the connection is of type *client credentials*, the client secret needs to be updated on the connection level.
131131

132-
### Is this feature supported using API Management running inside a VNet?
132+
### Is this feature supported using API Management running inside a virtual network?
133133

134-
Yes, as long as outbound connectivity on port 443 is enabled to the **AzureConnectors** service tag. For more information, see [Virtual network configuration reference](virtual-network-reference.md#required-ports).
134+
Requests for tokens need to go out of the customer's network to the credential manager endpoint, which remains in a Microsoft network. If the API Management instance is running inside a virtual network, credential manager is supported as long as outbound connectivity on port 443 is enabled to the **AzureConnectors** service tag. For more information, see [Virtual network configuration reference](virtual-network-reference.md#required-ports).
135135

136136
### What happens when a credential provider is deleted?
137137

0 commit comments

Comments
 (0)