Skip to content

Standardize terminology in Traffic Manager documentation - #128665

Open
modaks wants to merge 1 commit into
MicrosoftDocs:mainfrom
modaks:patch-6
Open

Standardize terminology in Traffic Manager documentation#128665
modaks wants to merge 1 commit into
MicrosoftDocs:mainfrom
modaks:patch-6

Conversation

@modaks

@modaks modaks commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Updated terminology for consistency in health check notes.

Updated terminology for consistency in health check notes.
@prmerger-automator

Copy link
Copy Markdown
Contributor

@modaks : 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 4a73dea:

✅ Validation status: passed

File Status Preview URL Details
articles/traffic-manager/traffic-manager-monitoring.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
v-dirichards requested a review from Copilot July 29, 2026 14:56
@v-dirichards

Copy link
Copy Markdown
Contributor

@asudbring

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 Jul 29, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates Azure Traffic Manager monitoring documentation to use more consistent terminology around health checks and endpoint behavior.

Changes:

  • Adjusted wording in a NOTE about health probes and what address spaces Traffic Manager can validate.
  • Standardized references to the “Always serve”/“Always serve traffic” endpoint configuration.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +202 to +204
> Endpoints that resolve to addresses within these network spaces **must be configured as Always Serve endpoints**. Traffic Manager can't perform health validation for these endpoints and therefore can't provide health-based failover.
>
> To ensure consistent behavior, Traffic Manager enforces the **Always serve traffic** configuration for endpoints that resolve to addresses within unsupported network spaces.
> To ensure consistent behavior, Traffic Manager enforces the **Always Serve** configuration for endpoints that resolve to addresses within unsupported network spaces.

> [!NOTE]
> Azure Traffic Manager health probes are designed to monitor endpoints that are reachable by the Traffic Manager probing infrastructure. Traffic Manager isn't designed to probe endpoints that resolve to addresses within private, non-routable, or Microsoft-internal network spaces.
> Azure Traffic Manager health probes are designed to monitor endpoints that are reachable by the Traffic Manager probing infrastructure. Traffic Manager isn't designed to probe endpoints that resolve to addresses within private network spaces.
Comment thread articles/traffic-manager/traffic-manager-monitoring.md
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.

4 participants