AzureTrafficManager (Azure Government)
Microsoft lists 10 IPv4 and 6 IPv6 prefixes for the service tag AzureTrafficManager in Azure Government (all regions).
1 version
Facts
- Microsoft id
government:AzureTrafficManager- Products
- AzureTrafficManager
- Cloud
- Azure Government
- Region
- All regions
- System service
- AzureTrafficManager
- Platform
- Azure
- Network features
- API, FW, NSG, UDR
- Change number
- 5
- IPv4 prefixes
10 entries
13.72.186.25/3220.141.127.34/3220.141.81.44/3223.97.16.0/3223.97.22.130/3251.54.51.128/2652.227.168.90/3252.244.202.176/3262.11.111.128/2662.11.172.192/26
- IPv6 prefixes
- 2001:489a:3102:4::29/128, 2001:489a:3103:7::4c0/122, 2001:489a:3400::1/128, 2001:489a:3403:7::2c0/122, 2001:489a:3600:1::6b/128, 2001:489a:3604:7::80/122
- Status pages
- Azure Traffic Manager status
- First captured by us
- (from our first import of this list)
- Microsoft last modified
- –
- Source
- Azure service tags · open the original at Microsoft
Microsoft says
Microsoft published no description with this item.
What Microsoft changed
One version so far. If Microsoft edits it, each change shows here with what was removed and added.
First version we captured ·
The text as we first saw it
Seen by us · Microsoft's page
Related changes
Other changes for Azure Traffic Manager
- General availability: Enhanced IPv6 functionality for MultiValue profiles in Azure Traffic Manager · Launched
- Azure Traffic Manager: Additional IP addresses for endpoint monitoring service. · Launched
- Azure DNS: Getting ready for DNS Flag Day · Launched
- AzureTrafficManager (Public cloud)
- AzureTrafficManager (Azure China)
- Azure Traffic Manager will stop automatically enabling, disabling, or deleting endpoints for Azure Cloud Services on May 1, 2019
- Azure Traffic Manager real user measurements · In preview
- Azure Traffic Manager traffic view · In preview