I've used that technique in products I built. Not speaking for MS but in my case the UUID was either written into some server log (to hopefully be used to diagnose the problem if reported), or matched diagnostic statements in our source code (so the problem could be diagnosed in conjunction with the code). Using a unique identifier helps prevent the kind of confusion caused when 3 different developers all decide that "this can't happen" is a good diagnostic message to display to the user.

Fwiw the identifier you posted isn't a UUID but the same justification applies.