Skip to content

Standardize terminology in Traffic Manager documentation #128665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Sami Modak (modaks) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Standardize terminology in Traffic Manager documentation #128665

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions articles/traffic-manager/traffic-manager-monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,11 +197,11 @@ See the following example:
> - Endpoints that are configured to always serve traffic are billed for [basic health checks](https://azure.microsoft.com/pricing/details/traffic-manager/).

> [!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.
>
> Endpoints that resolve to addresses within these network spaces **must be configured as Always serve traffic endpoints**. Traffic Manager can't perform health validation for these endpoints and therefore can't provide health-based failover.
> 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.
Comment on lines +202 to +204
Comment thread
v-dirichards marked this conversation as resolved.

## Firewall Setup for Health Checks

Expand Down