Skip to content
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

[pull] master from MicrosoftDocs:master #7

Merged
merged 28 commits into from
May 9, 2019
Merged

[pull] master from MicrosoftDocs:master #7

Changes from 2 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
82e439b
Update nested-virtualization.md
gaubert-ms Mar 1, 2019
cff3f35
Add FQDN to TM endpoint options
ryanborMSFT Apr 8, 2019
3e65655
Fix error in example code
Apr 13, 2019
81740c7
Update virtual-nodes-cli.md
richeney Apr 17, 2019
4771bdd
Missing some Container initialization
RodrigoRVieira Apr 26, 2019
0c22c46
Update how-to-connect-device-writeback.md
SanDeo-MSFT Apr 29, 2019
577e52a
Update expand-disks.md
timbasham May 2, 2019
e85ef0f
Added PHP PDO sample code
alexander7567 May 3, 2019
903d060
Update http links
nxtn Feb 16, 2019
52d9db2
Update analysis-services-datasource.md
jonburchel May 8, 2019
392155b
Minor spelling correction
paulkel May 9, 2019
12ee57a
typo: Double word "and"
nschonni May 9, 2019
3b1e5ba
typo: Double word "an"
nschonni May 9, 2019
b1d68b0
fixed typo (proejct -> project)
PhonicCanine May 9, 2019
78d15e5
Merge pull request #30909 from PhonicCanine/patch-1
American-Dipper May 9, 2019
09ab313
Merge pull request #30893 from nschonni/double-and
American-Dipper May 9, 2019
91d7b44
Merge pull request #30879 from paulkel/patch-30
American-Dipper May 9, 2019
dd47b8f
Merge pull request #30843 from jonburchel/patch-3
American-Dipper May 9, 2019
330298c
Merge pull request #30894 from nschonni/double-an
rjagiewich May 9, 2019
3bf7960
Merge pull request #30569 from alexander7567/master
rjagiewich May 9, 2019
eeada98
Merge pull request #30504 from timbasham/patch-1
rjagiewich May 9, 2019
769fbae
Merge pull request #26007 from gaubert-ms/patch-3
rjagiewich May 9, 2019
c346e62
Merge pull request #30759 from NextTurn/http-16
rjagiewich May 9, 2019
23385c5
Merge pull request #30282 from deosandeep/patch-17
rjagiewich May 9, 2019
a25d198
Merge pull request #30176 from RodrigoRVieira/patch-2
rjagiewich May 9, 2019
51af948
Merge pull request #29588 from richeney/patch-5
rjagiewich May 9, 2019
09b6d53
Merge pull request #29348 from paulinoj/fix-example-code
rjagiewich May 9, 2019
2a054d7
Merge pull request #28998 from ryanborMSFT/patch-8
rjagiewich May 9, 2019
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
4 changes: 2 additions & 2 deletions articles/traffic-manager/traffic-manager-endpoint-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Microsoft Azure Traffic Manager allows you to control how network traffic is dis

There are three types of endpoint supported by Traffic Manager:
* **Azure endpoints** are used for services hosted in Azure.
* **External endpoints** are used for IPv4/IPv6 addresses, or, for services hosted outside Azure that can either be on-premises or with a different hosting provider.
* **External endpoints** are used for IPv4/IPv6 addresses, FQDNs, or for services hosted outside Azure that can either be on-premises or with a different hosting provider.
* **Nested endpoints** are used to combine Traffic Manager profiles to create more flexible traffic-routing schemes to support the needs of larger, more complex deployments.

There is no restriction on how endpoints of different types are combined in a single Traffic Manager profile. Each profile can contain any mix of endpoint types.
Expand All @@ -41,7 +41,7 @@ When using Azure endpoints, Traffic Manager detects when a 'Classic' IaaS VM, cl

## External endpoints

External endpoints are used for either IPv4/IPv6 addresses, or, for services outside of Azure. Use of IPv4/IPv6 address endpoints allows traffic manager to check the health of endpoints without requiring a DNS name for them. As a result, Traffic Manager can respond to queries with A/AAAA records when returning that endpoint in a response. Services outside of Azure can include a service hosted on-premises or with a different provider. External endpoints can be used individually or combined with Azure Endpoints in the same Traffic Manager profile except for endpoints specified as IPv4 or IPv6 addresses which can only be external endpoints. Combining Azure endpoints with External endpoints enables various scenarios:
External endpoints are used for either IPv4/IPv6 addresses, FQDNs, or for services outside of Azure. Use of IPv4/IPv6 address endpoints allows traffic manager to check the health of endpoints without requiring a DNS name for them. As a result, Traffic Manager can respond to queries with A/AAAA records when returning that endpoint in a response. Services outside of Azure can include a service hosted on-premises or with a different provider. External endpoints can be used individually or combined with Azure Endpoints in the same Traffic Manager profile except for endpoints specified as IPv4 or IPv6 addresses which can only be external endpoints. Combining Azure endpoints with External endpoints enables various scenarios:

* Provide increased redundancy for an existing on-premises application in either an active-active or active-passive failover model using Azure.
* Route traffic to endpoints that do not have a DNS name associated with them. In addition, decrease the overall DNS lookup latency by removing the need to run a second DNS query to get an IP address of a DNS name returned.
Expand Down