%3CLINGO-SUB%20id%3D%22lingo-sub-1266182%22%20slang%3D%22en-US%22%3EAzure%20Lab%20Services%20outage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1266182%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20wanted%20to%20share%20about%20what%20happened%20regarding%20the%20recent%20outage%20in%20Azure%20Lab%20Services.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%2C%20we%20are%20very%20conscious%20of%20the%20impact%20of%20the%20outage%20in%20the%20current%20context%2C%20and%20we%20are%20deeply%20sorry.%26nbsp%3B%20It%20should%20not%20have%20happened%2C%20but%20it%20did.%26nbsp%3B%20We%20will%20share%20learnings%20and%20preventative%20steps%20for%20the%20future%20once%20we%20are%20back%20to%20expected%20level%20of%20service%20for%20all%20Labs.%26nbsp%3B%20In%20the%20meantime%2C%20at%20the%20risk%20of%20oversharing%2C%20this%20is%20what%20happened.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20way%20the%20service%20works%20is%20that%20we%20have%20VMs%20and%20related%20resources%20capacity%20pre-assigned%20to%20our%20service%20in%20Azure.%26nbsp%3B%20We%20have%20monitoring%20in%20place%20that%20allows%20us%20to%20augment%20our%20capacity%20as%20we%20need.%20%26nbsp%3BIn%20normal%20conditions%2C%20this%20process%20allows%20us%20to%20maintain%20a%20healthy%20reserve%20as%20we%20grow.%26nbsp%3B%20We%20are%20no%20longer%20in%20normal%20conditions.%20%26nbsp%3BThe%20world%20has%20had%20to%20go%20to%20remote%20working%20and%20learning%20in%20a%20very%20short%20term.%26nbsp%3B%20So%20our%20priority%20over%20the%20last%20weeks%20has%20been%20to%20provide%20Labs%20to%20customers%20needing%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETeams%2C%20Windows%20Virtual%20Desktops%20and%20other%20services%20also%20needed%20more%20capacity%20to%20meet%20the%20increased%20demand.%26nbsp%3B%20In%20Labs%2C%20we%20had%20unused%20capacity%20we%20could%20reclaim%20from%20Labs%20and%20VMs%20no%20longer%20in%20use%20that%20customers%20never%20deleted.%26nbsp%3B%20In%20our%20pricing%20model%2C%20we%20only%20charge%20for%20active%20hours%2C%20so%20many%20customers%20do%20not%20delete%20their%20Labs%20and%20VMs%20once%20they%20no%20longer%20need%20it.%26nbsp%3B%20%26nbsp%3BIn%20the%20last%20year%20we%20focused%20on%20implementing%20features%20and%20improving%20the%20quality%20of%20the%20experience%20and%20delayed%20implementing%20reclaiming%20procedures.%26nbsp%3B%20%26nbsp%3BThis%20seemed%20to%20be%20the%20right%20trade-off%20for%20where%20we%20are%20in%20the%20service%20life%20cycle.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%2C%20over%20the%20last%20week%2C%20we%20implemented%20a%20reclaiming%20process%20to%20liberate%20the%20unused%20capacity.%26nbsp%3B%20We%20started%20by%20removing%20Labs%20that%20%E2%80%9Creserved%E2%80%9D%20capacity%20but%20never%20were%20published%2C%20then%20VMs%20that%20were%20never%20started%20followed%20by%20VMs%20in%20Labs%20that%20had%20seen%20no%20usage%20in%20a%20long%20time.%26nbsp%3B%20We%20added%20the%20information%20in%20the%20UI%20and%20sent%20emails%20to%20the%20owners%20of%20Labs%20to%20be%20reclaimed%20so%20that%20they%20could%20have%20a%20chance%20to%20keep%20them%20if%20needed.%26nbsp%3B%20In%20Labs%20we%20reclaimed%2C%20we%20kept%20the%20Template%20VM%20in%20case%20they%20would%20need%20to%20be%20republished.%26nbsp%3B%20It%20has%20been%20very%20front%20of%20mind%20to%20make%20sure%20that%20there%20would%20be%20no%20loss%20of%20data%20to%20anyone.%26nbsp%3B%20We%20also%20had%20a%20pocket%20of%20capacity%20that%20we%20could%20reclaim%20more%20aggressively%20from%20the%20various%20Labs%20we%20create%20for%20ourselves%20to%20test%20and%20reproduce%20issues%20in%20isolated%20subscriptions%20kept%20for%20that%20purpose.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20ran%20these%20procedures%20gradually%2C%20region%20to%20region%2C%20and%20scenario%20by%20scenario.%26nbsp%3B%20%26nbsp%3BThe%20program%20worked%20and%20we%20reclaimed%20enough%20capacity%20to%20put%20us%20in%20a%20good%20position%20to%20meet%20demand.%26nbsp%3B%20We%20were%20in%20a%20good%20place%2C%20or%20so%20we%20thought.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20realized%20that%20some%20of%20the%20%E2%80%9Cinternal%E2%80%9D%20subscriptions%20actually%20contained%20customer%20Labs%20and%20that%20we%20deleted%20them%20along%20with%20ours.%20%26nbsp%3BIt%20should%20not%20have%20happened.%20It%20did.%26nbsp%3B%20When%20a%20user%20creates%20a%20Lab%2C%20our%20allocation%20algorithm%20decides%20in%20which%20specific%20subscription%20to%20create%20the%20lab%20based%20on%20current%20usage%2C%20unpublished%20labs%2C%20expected%20lab%20size%2C%20and%20a%20few%20other%20factors.%26nbsp%3B%20%26nbsp%3BWe%20had%20a%20few%20%E2%80%9Cinternal%E2%80%9D%20subscriptions%20mistakenly%20configured%20to%20be%20part%20of%20the%20pool.%26nbsp%3B%20So%2C%20when%20we%20applied%20the%20much%20more%20aggressive%20criteria%20to%20%E2%80%9Cinternal%E2%80%9D%20subs%2C%20we%20deleted%20Labs%20we%20should%20not%20have%20deleted.%26nbsp%3B%20Again%2C%20it%20should%20not%20have%20happened.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOver%20the%20last%20few%20days%2C%20we%20have%20been%20heads%20down%20trying%20to%20recover%20these%20Labs.%26nbsp%3B%20They%20basically%20fit%20in%202%20categories%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ELabs%20that%20could%20be%20recovered.%3C%2FSTRONG%3E%26nbsp%3B%20In%20some%20region%20we%20were%20able%20to%20find%20the%20disks%20still%20intact%20and%20have%20recreated%20these%20labs.%26nbsp%3BAccess%20to%20the%20lab%20should%20have%20resumed%20by%20now.%26nbsp%3B%20The%20only%20impact%20to%20these%20Labs%20is%20that%20in%20the%20event%20you%20need%20to%20increase%20the%20VM%20pool%2C%20you%20will%20need%20to%20re-publish%20the%20Lab%20first.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ELabs%20that%20cannot%20be%20recovered.%26nbsp%3B%20%3C%2FSTRONG%3EThese%20will%20need%20to%20be%20recreated.%26nbsp%3B%20If%20they%20were%20published%2C%20this%20means%20loss%20of%20data%20from%20the%20students.%26nbsp%3B%20We%20cannot%20say%20how%20much%20this%20pains%20us.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20your%20Lab%20was%20not%20recovered%2C%20it%20will%20be%20identified%20in%20the%20Labs%20UI.%26nbsp%3B%20Very%20shortly%2C%20you%20will%20be%20able%20to%20open%20your%20Lab%20in%20read%20only%20mode%20and%20you%20will%20be%20able%20to%20view%20the%20roster%2C%20schedule%2C%20quota%20and%20other%20configurations.%26nbsp%3B%20You%20will%20also%20be%20able%20to%20delete%20your%20Lab%20once%20you%20no%20longer%20need%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20understand%20this%20requires%20potentially%20significant%20effort.%26nbsp%3B%20You%20can%20contact%20us%20at%26nbsp%3B%3CA%20href%3D%22mailto%3AAzLabsCOVIDSupport%40microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzLabsCOVIDSupport%40microsoft.com%3C%2FA%3E%26nbsp%3Bfor%20any%20question%20or%20help.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20trying%20to%20meet%20demand%2C%20we%20ran%20faster%20on%20the%20reclaiming%20than%20we%20should%20have%2C%20and%20we%20missed%20the%20issue%20before%20it%20was%20too%20late.%26nbsp%3B%20We%20will%20extract%20the%20learnings%20and%20improve%20our%20internal%20processes%20to%20prevent%20anything%20similar%20happening%20again.%26nbsp%3B%26nbsp%3BAs%20mentioned%20already%2C%20this%20should%20not%20have%20happened%2C%20and%20we%20are%20very%20sorry.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20do%20not%20hesitate%20to%20contact%20us%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Labs%20team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1266182%22%20slang%3D%22en-US%22%3E%3CP%3EDetails%20about%20the%20Lab%20outage%20that%20just%20concluded%20and%20next%20steps%20for%20the%20labs%20that%20were%20adversely%20affected.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1266182%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELab%20Services%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

We wanted to share about what happened regarding the recent outage in Azure Lab Services.

 

First, we are very conscious of the impact of the outage in the current context, and we are deeply sorry.  It should not have happened, but it did.  We will share learnings and preventative steps for the future once we are back to expected level of service for all Labs.  In the meantime, at the risk of oversharing, this is what happened.

 

The way the service works is that we have VMs and related resources capacity pre-assigned to our service in Azure.  We have monitoring in place that allows us to augment our capacity as we need.  In normal conditions, this process allows us to maintain a healthy reserve as we grow.  We are no longer in normal conditions.  The world has had to go to remote working and learning in a very short term.  So our priority over the last weeks has been to provide Labs to customers needing them.

 

Teams, Windows Virtual Desktops and other services also needed more capacity to meet the increased demand.  In Labs, we had unused capacity we could reclaim from Labs and VMs no longer in use that customers never deleted.  In our pricing model, we only charge for active hours, so many customers do not delete their Labs and VMs once they no longer need it.   In the last year we focused on implementing features and improving the quality of the experience and delayed implementing reclaiming procedures.   This seemed to be the right trade-off for where we are in the service life cycle. 

 

So, over the last week, we implemented a reclaiming process to liberate the unused capacity.  We started by removing Labs that “reserved” capacity but never were published, then VMs that were never started followed by VMs in Labs that had seen no usage in a long time.  We added the information in the UI and sent emails to the owners of Labs to be reclaimed so that they could have a chance to keep them if needed.  In Labs we reclaimed, we kept the Template VM in case they would need to be republished.  It has been very front of mind to make sure that there would be no loss of data to anyone.  We also had a pocket of capacity that we could reclaim more aggressively from the various Labs we create for ourselves to test and reproduce issues in isolated subscriptions kept for that purpose.

 

We ran these procedures gradually, region to region, and scenario by scenario.   The program worked and we reclaimed enough capacity to put us in a good position to meet demand.  We were in a good place, or so we thought.

 

We realized that some of the “internal” subscriptions actually contained customer Labs and that we deleted them along with ours.  It should not have happened. It did.  When a user creates a Lab, our allocation algorithm decides in which specific subscription to create the lab based on current usage, unpublished labs, expected lab size, and a few other factors.   We had a few “internal” subscriptions mistakenly configured to be part of the pool.  So, when we applied the much more aggressive criteria to “internal” subs, we deleted Labs we should not have deleted.  Again, it should not have happened.

 

Over the last few days, we have been heads down trying to recover these Labs.  They basically fit in 2 categories:

 

Labs that could be recovered.  In some region we were able to find the disks still intact and have recreated these labs. Access to the lab should have resumed by now.  The only impact to these Labs is that in the event you need to increase the VM pool, you will need to re-publish the Lab first.  

 

Labs that cannot be recovered.  These will need to be recreated.  If they were published, this means loss of data from the students.  We cannot say how much this pains us. 

 

If your Lab was not recovered, it will be identified in the Labs UI.  Very shortly, you will be able to open your Lab in read only mode and you will be able to view the roster, schedule, quota and other configurations.  You will also be able to delete your Lab once you no longer need it.

 

We understand this requires potentially significant effort.  You can contact us at AzLabsCOVIDSupport@microsoft.com for any question or help.

 

In trying to meet demand, we ran faster on the reclaiming than we should have, and we missed the issue before it was too late.  We will extract the learnings and improve our internal processes to prevent anything similar happening again.  As mentioned already, this should not have happened, and we are very sorry. 

 

Please do not hesitate to contact us,

 

The Labs team