We finally received both confirmation from Microsoft of the issue as well as an update on the fix in our support ticket:
The cause of the issue has been identified, and a fix has been rolled out. It is expected to be fully deployed by early next week. We apologize for the disruption this has caused.