I'm really glad Google pointed me to this question. I got the same error literally 2 minutes after you posted this question...
It seems to have been a Microsoft server-side error, as it has corrected itself for me since I started typing this answer.