Skip to content

Commit f43f129

Browse files
authored
Update articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md
1 parent 2a152dc commit f43f129

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
@@ -54,7 +54,7 @@ If your API Management service has an established networking line of sight to th
5454

5555
For backup and restore and custom hostname certificates, you need to ensure the target key vault or storage account is publicly accessible or you need to preserve its trusted connectivity setting to allow traffic from API Management resources, even if your API Management service has a networking line of sight established with it.
5656

57-
If you are using workspace-based gateways, you are not affected given they [do not support managed identity](../workspaces-overview.md).
57+
APIs in workspaces aren't affect by this change, since they [do not support managed identity](../workspaces-overview.md).
5858

5959
### Step 1: Does my API Management gateway rely on trusted service connectivity?
6060

0 commit comments

Comments
 (0)