I completely agree... Folks should start moving off of the remotewebaccess.com Microsoft personalized domain names in order to avoid these types of (frequent and lengthy) interruptions and switch over to using their very own custom/vanity domain name instead.
I have a step-by-step writeup on how to do just that in Windows Server Essentials (using either a user-purchased SSL certificate or a free Let's Encrypt SSL certificate) posted on my website over here:
How To Manually Set Up A Custom / Vanity Domain Name In Windows Server Essentials
When you manually set up your own domain in Anywhere Access, you are in full control of it, and so you no longer need to worry about things going down on Microsoft's end (as you do when relying on a remotewebaccess.com Microsoft personalized domain name). ;-)