%3CLINGO-SUB%20id%3D%22lingo-sub-1790061%22%20slang%3D%22en-US%22%3E%5BResolved%5D%20Azure%20Lab%20Services%20Outage%3A%20Unable%20to%20connect%20to%20VMs%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1790061%22%20slang%3D%22en-US%22%3E%3CP%3ECustomers%20may%20have%20been%20unable%20to%20connect%20to%20their%20lab%20virtual%20machines%20(VMs)%20between%20Oct%2013%2C%202020%20and%20Oct%2015%2C%202020.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ECause%20of%20the%20outage%3A%3C%2FSTRONG%3E%3CBR%20%2F%3EAzure%20Lab%20Services%20manages%20the%20customers'%20VMs%20within%20internal%20Azure%20subscriptions%20that%20the%20service%20owns%20(more%20details%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Flab-services%2Fclassroom-labs-fundamentals%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eservice's%20architecture%20fundamentals%20here%3C%2FA%3E).%20For%20internal%20subscriptions%2C%20Microsoft%20runs%20regular%20organizational%20security%20rules.%20Due%20to%20recent%20configuration%20changes%2C%20an%20internal%20security%20rule%20got%20applied%20to%20the%20customer%20VMs%20inside%20our%20subscriptions%20that%20blocked%20VM%20connections%20that%20came%20from%20external%20to%20Microsoft.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EResolution%3A%20%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20internal%20security%20rules%20that%20were%20blocking%20customers'%20access%20to%20the%20VMs%20have%20been%20removed%2C%20and%20we%20have%20ensured%20that%20the%20internal%20configurations%20will%20no%20longer%20be%20applied%20to%20our%20service's%20subscriptions%20that%20host%20customer%20VMs.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EThis%20outage%20has%20been%20resolved%20and%20customers%20can%20now%20connect%20to%20their%20VMs.%3C%2FSTRONG%3E%20If%20you%20were%20affected%20by%20the%20issue%2C%20please%20try%20starting%20and%20connecting%20to%20the%20VMs%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20apologize%20for%20the%20inconvenience.%20If%20you%20have%20any%20questions%2C%20please%20leave%20us%20a%20comment%20below.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Azure%20Lab%20Services%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1790061%22%20slang%3D%22en-US%22%3E%3CP%3ECustomers%20may%20have%20been%20unable%20to%20connect%20to%20their%20lab%20virtual%20machines%20(VMs)%20between%20Oct%2013%2C%202020%20and%20Oct%2015%2C%202020.%26nbsp%3B%3CSTRONG%3EThis%20outage%20has%20been%20resolved%20and%20customers%20can%20now%20connect%20to%20their%20VMs.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1790061%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELab%20Services%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Customers may have been unable to connect to their lab virtual machines (VMs) between Oct 13, 2020 and Oct 15, 2020.

 

Cause of the outage:
Azure Lab Services manages the customers' VMs within internal Azure subscriptions that the service owns (more details on the service's architecture fundamentals here). For internal subscriptions, Microsoft runs regular organizational security rules. Due to recent configuration changes, an internal security rule got applied to the customer VMs inside our subscriptions that blocked VM connections that came from external to Microsoft.


Resolution:
The internal security rules that were blocking customers' access to the VMs have been removed, and we have ensured that the internal configurations will no longer be applied to our service's subscriptions that host customer VMs.


This outage has been resolved and customers can now connect to their VMs. If you were affected by the issue, please try starting and connecting to the VMs again.

 

We apologize for the inconvenience. If you have any questions, please leave us a comment below.

 

- Azure Lab Services Team