Skip to content

APIM virtual network reference - Describe more restricted outbound TCP access to port 12000#128416

Open
prutsert wants to merge 1 commit intoMicrosoftDocs:mainfrom
prutsert:main
Open

APIM virtual network reference - Describe more restricted outbound TCP access to port 12000#128416
prutsert wants to merge 1 commit intoMicrosoftDocs:mainfrom
prutsert:main

Conversation

@prutsert
Copy link
Copy Markdown

Moved reference to outbound TCP connections on port 12000 to Azure Monitor Service Tags specific outbound rules.

According to the "Virtual network configuration reference: API Management" documentation, there is a requirement to "Allow outbound TCP access on port 12000 for diagnostics" without mentioning a specific destination.
According to this question/answer, opening this port is only needed for AzureMonitor Service Tags.

@prmerger-automator
Copy link
Copy Markdown
Contributor

@prutsert : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit b066214:

✅ Validation status: passed

File Status Preview URL Details
articles/api-management/virtual-network-reference.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner
Copy link
Copy Markdown
Contributor

@dlepow

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Apr 15, 2026
@prmerger-automator
Copy link
Copy Markdown
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @dlepow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants