Azure Cloud Service VIP Swap Issue During Deployment — Traffic Not Moving to Target Deployment

JulianPisoni-6917 0 Reputation points
2026-09-27T02:32:01.16+00:00

Problem description

I am experiencing an issue during the VIP swap process in deploying my Azure Cloud Service (Extended Support) with web and worker roles. The swap becomes stuck before completion, and the traffic continues to remain on the existing Production deployment instead of shifting to the target deployment. The start time of the operation is approximately 20260926222414, and no explicit error message or code is available in the logs.

Environment

Azure Cloud Service (Extended Support) with web and worker roles, region not specified, deployment flow using staging and Production slots with VIP swap.

What I've already tried

I reviewed the initial troubleshooting steps, which did not include detailed role-instance status checks. I confirmed that the deployment and application code are consistent with a previous deployment that succeeded on another subscription. I also verified that the load balancer was created successfully and checked the activity logs, which show no errors. Additionally, I examined the health of role instances and they appear healthy, and no deployment updates or upgrades are currently in progress.

Current status

The VIP swap is still pending, and the target deployment has not been promoted to Production. I am seeking guidance on further troubleshooting steps or configurations needed to resolve the VIP swap failure.

Azure Cloud Services
Azure Cloud Services

An Azure platform as a service offer that is used to deploy web and cloud applications.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. VarunTha 15,095 Reputation points Microsoft External Staff Moderator
    2026-10-02T16:20:54.2966667+00:00

    Hello JulianPisoni-6917,

    Thank you for sharing the details.

    A VIP swap in Azure Cloud Services (Extended Support) can remain pending when one or more role instances are not fully ready, another deployment operation is still being processed, the two cloud services are not correctly configured as swappable, or the associated public IP configurations do not meet the swap prerequisites.

    Please ensure that:

    • All web-role and worker-role instances in both deployments are running and ready.
    • No deployment update, upgrade, autoscale, deletion, guest OS update, or service-healing operation is in progress.
    • Each cloud service identifies the other as its Swappable cloud service.
    • If reserved or static public IP addresses are used, both cloud services have compatible public IP configurations.
    • No additional modifying operation is initiated while the current VIP swap remains pending.

    Since the standard health and Activity Log checks have already been completed, further investigation may require secure review of the underlying operation details.

    We will continue supporting and investigating this issue through the existing DFM support ticket.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.