Microsoft big bang = big fail
In my experience with windows 2012 servers on a virtual environment, it is bloody hard to make the time stay accurate +- a lot more than one lousy leap second!
Especially if you have active directory which competes with a myriad of built in 'ms knows best' mechanisms all in competition to set the clock.
I presume they must use third party code to fix it on azure, because ms knowledge base can't even agree on what is the best thing to do.
I'd wager that MS servers will be all over the place time wise for a lot longer than a second. However since they explicitly exclude 'real time' as a thing they can do, what do they care!