Based on our internal testing, Microsoft has now fixed this issue. Please try again when you have a chance!