At this time, we have not yet identified the cause of this issue, but system admins are currently investigating with Microsoft assistance. Thank you for your patience as we work to resolve this issue as soon as possible.