Skip to content

Commit 7cbf3e9

Browse files
Merge pull request #311603 from tomkerkhove/patch-33
docs(apim): Add note about APIM + trusted service, no disable required on target
2 parents 33590c1 + e51553d commit 7cbf3e9

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,11 @@ You can configure the networking of target resources to one of the following opt
111111

112112
- [How to front a network security perimeter-protected Azure resource with Azure API Management](../using-network-security-perimeter.md)
113113

114+
> [!IMPORTANT]
115+
> Customers can continue using trusted services on the target Azure service for non-Azure API Management scenarios. However, Azure API Management will no longer support it so the gateway needs alternative ways to communicate and have network line-of-sight.
116+
>
117+
> For example, you can enable trusted service connectivity for an Azure Storage resource and use Network Security Perimeter to access it from API Management's gateway.
118+
114119
### Step 3: Disable trusted service connectivity in API Management gateway
115120

116121
After ensuring that your API Management gateway doesn't access other Azure services using trusted service connectivity, you must explicitly disable trusted connectivity in your gateway to acknowledge you have verified that the service no longer depends on trusted connectivity.

0 commit comments

Comments
 (0)