Hi all,

Recently I have been experience extremely slow deployments to the cloud. I publish my cloud web app through VS2013. Uploading is fast (about 1-2 minutes), but Creating the instances can take up to 45 - 60mins and a minimum of 25 mins. May I know if anyone has similar experiences and any solutions available? I can replicate this issue from my office as well as home machines. No errors are thrown, portal shows The deployment is being created. 

Cheers,

Kevin

• Edited by Kevin W K Friday, July 03, 2015 2:49 AM

Latest error:

11:49:34 PM - Error: A security token validation error occured for the received JWT token.  Http Status Code: Unauthorized  OperationId: 

Hi Kevin,

If this is affecting your production, I would suggest you create a support ticket and have a support professional look into this issue. It could be related to Azure Fabric or some other networking issue etc. In order to determine the root cause , we will have to look into the backend logs and your deployment details.

Regards,
Prasandhi Kumar

• Proposed as answer by Nithin.RathnakarMicrosoft contingent staff, Moderator 11 hours 46 minutes ago

Hi Kevin,

If this is affecting your production, I would suggest you create a support ticket and have a support professional look into this issue. It could be related to Azure Fabric or some other networking issue etc. In order to determine the root cause , we will have to look into the backend logs and your deployment details.

Regards,
Prasandhi Kumar

• Proposed as answer by Nithin.RathnakarMicrosoft contingent staff, Moderator Wednesday, July 08, 2015 7:31 PM

Hi Kumar!

I would subscribe if only MS hadn't impose a minimum technical support subscription term of 6 months. I don't think I have that many problems to solve haha.

Cheers!

I haven't solved the errors, but I found out that deploying to staging would cut down deployment times a fair bit, and then swapping VIPs. Deploying into the production containing instances would always take more than 40 mins.

Cheers,

Kevin

I haven't solved the errors, but I found out that deploying to staging would cut down deployment times a fair bit, and then swapping VIPs. Deploying into the production containing instances would always take more than 40 mins.

Cheers,

Kevin

• Marked as answer by Prasandhi KumarMicrosoft contingent staff, Moderator 23 hours 3 minutes ago

I haven't solved the errors, but I found out that deploying to staging would cut down deployment times a fair bit, and then swapping VIPs. Deploying into the production containing instances would always take more than 40 mins.

Cheers,

Kevin

• Marked as answer by Prasandhi KumarMicrosoft contingent staff, Moderator Thursday, July 09, 2015 8:16 AM