Azure Traffic Manager will stop automatically enabling, disabling, or deleting endpoints for Azure Cloud Services on May 1, 2019
Microsoft retired this Cloud Services and Traffic Manager feature on 1 May 2019.
Retirement1 version
Facts
- Microsoft id
azure-atm-automanagent-cloudservice-endpoints- Products
- Cloud Services, Traffic Manager
- Update type
- Retirements, Services
- Product categories
- Compute, Management and governance, Networking
- Retirement
- 1 May 2019
- Status pages
- Azure Cloud Services status, Azure Traffic Manager status
- First captured by us
- (from our first import of this list)
- Microsoft last modified
- Source
- Azure Updates · open the original at Microsoft
Microsoft says
Currently, Azure Traffic Manager can automatically enable, disable, or delete endpoints when starting, stopping, or deleting the corresponding cloud service.
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 timestamp · Microsoft's page
Related changes
Other changes for Azure Cloud Services, Azure Traffic Manager
- Retirement: Azure Cloud Services Guest OS Families 2, 3, and 4
- General availability: Reserved namespaces for subdomains · Launched
- General availability: Enhanced IPv6 functionality for MultiValue profiles in Azure Traffic Manager · Launched
- Generally available: DNS reservations to prevent subdomain takeover in Cloud Services deployments · Launched
- Public preview: Announcing platform support migration of Azure Cloud Services (classic) to Azure Resource Manager · In preview
- General availability: Transition to Cloud Services (extended support) with new migration tool · Launched
- Cloud Services (classic) deployment model is retiring on 31 August 2024
- Cloud Services (classic) deployment model is retiring on 31 August 2024