System access has been restored.  At this time, the facts point to no issue with our production code or any changes introduced to the environment by WorkBoard but rather a failure in the Microsoft API layer between Azure services.  As you know, we rely on Microsoft for cloud infrastructure.  The second failure point was in the support SLA from Microsoft which was < 1 hour to critical situations.  Today, it took 90 minutes to get support on a call, and 2 hours to get a capable support person on a call.  Even with those resources, they needed to escalate to engineering and to initiate a reboot of their API layer to mitigate the issue.  That reboot in turn required other services in our environment to be restarted, which relieved the problem.

We are expecting an immediate explanation for why the API layer failed (expected today) and a full root cause analysis from Microsoft (expected in few days).  All parties were focused on resolving the issue and are now turning to diagnosing and preventing further occurance.

While this issue does not appear to be caused by WorkBoard, we understand its full brunt was on you as a customer who relies on the platform and that it comes on the heels of several recent frustrating issues that were our errors. We are actively exploring what additional level of SLA we can purchase (our current level is Premier) and alternative providers that can more rapidly diagnose issues and be more helpful in resolutions on a wider spectrum and productive in preventing issues in the first instance.