Same issue here. Odd thing is it was working last week with beta 5, and the same app version (16.52). Looks like a potential server side change on the office365 might have caused this issue.