With a large enough employees table, Azure SQL could parallelize the scan operation, in which case the ordering would not necessarily be maintained.

Reminded me of Steve Mould's explanation of Entropy (using the example of a Sterling Engine). https://www.youtube.com/watch?v=w2iTCm0xpDc