Final Update: Tuesday, 24 November 2015 23:36 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 24 Nov 2015 ~21:30 UTC. Our logs show the incident started on 24 Nov 2015 ~17:05 UTC. As of this writing, we are currently working with our partner team to determine the root cause of the AAD latency issue.
We understand that customers rely on VS Online as a critical service and apologize for any impact this incident caused.
Sincerely,
VS Online Service Delivery Team
Final Update: Tuesday, 24 November 2015 23:32 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 24 Nov 2015 21:30 UTC. We are currently working with our partner team to determine the root cause of the AAD latency issue.
We understand that customers rely on VS Online as a critical service and apologize for any impact this incident caused.
Sincerely,
VS Online Service Delivery Team
We’ve confirmed that all systems are back to normal with no customer impact as of 24 Nov 2015 ~21:30 UTC. Our logs show the incident started on 24 Nov 2015 ~17:05 UTC. As of this writing, we are currently working with our partner team to determine the root cause of the AAD latency issue.
We understand that customers rely on VS Online as a critical service and apologize for any impact this incident caused.
Sincerely,
VS Online Service Delivery Team
Final Update: Tuesday, 24 November 2015 23:32 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 24 Nov 2015 21:30 UTC. We are currently working with our partner team to determine the root cause of the AAD latency issue.
We understand that customers rely on VS Online as a critical service and apologize for any impact this incident caused.
Sincerely,
VS Online Service Delivery Team
Initial Update: Tuesday, 24 November 2015 10:30 UTC
We are actively investigating issues with VS Team Services AAD backed accounts. Subset of customers accessing AAD backed accounts in VS Team Services may experience slowness to login.
We are working to resolve this issue and apologize for any inconvenience.
Next Update:Before 20:00 UTC
Sincerely,
VS Online Service Delivery Team