Skip to content

Commit 20b0d30

Browse files
Merge pull request #311279 from tomkerkhove/patch-33
docs: Provide note on Azure Advisor outgoing requests for breaking change (🚧)
2 parents 0f1cfab + 4b25e8f commit 20b0d30

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,12 @@ First, check for an Azure Advisor recommendation:
3737
1. If it does, update the networking configuration to eliminate the dependency on trusted service connectivity. If it doesn’t, proceed to the next step.
3838
1. Disable trusted service connectivity in your API Management gateway.
3939

40+
> [!NOTE]
41+
> Azure Advisor will provide you an indication of outgoing traffic to respective Azure backends from the past day, regardless of the used authentication mechanism.
42+
> This provides an indication of what backend services your API Management service relies on and which ones you must verify.
43+
>
44+
> If not traffic is reported, we recommend monitoring for a few days and proceed with disablement when appropriate.
45+
4046
#### Scenarios that are not affected by the breaking change
4147

4248
All scenarios involving control plane operations that use trusted service connectivity remain supported and aren't affected by the breaking change, including accessing:

0 commit comments

Comments
 (0)