Skip to content

Commit 9642c84

Browse files
authored
Update articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md
1 parent 7d1e53f commit 9642c84

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ You can configure the networking of target resources to one of the following opt
112112
- [How to front a network security perimeter-protected Azure resource with Azure API Management](../using-network-security-perimeter.md)
113113

114114
> [!IMPORTANT]
115-
> Customers can remain on 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.
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.
116116
>
117117
> Example - You can have trusted service enable on Azure Storage, and use Network Security Perimeter to allow Azure API Management with migration applied to still access the resource.
118118

0 commit comments

Comments
 (0)