No incidents reported
This issue has now been resolved.
There is currently an issue with the 2016 exchange server, we are looking into the issue