got a response from Microsoft. It's fixed now.