@timbray
“UUID should be represented by the "hex-and-dash" string format consisting of multiple groups of uppercase or lowercase alphanumeric hexadecimal characters “
Every time I’m handling uuids in code I need to remember to think about case. I have seen resource IDs in azure recently consisting of multiple uuids in the one resource ID string. where some UUIDs are in caps and others are lower case. In the same ID string. But if you were building that resource ID string to use in an azure SDK you would have to respect which UUIDs are in caps and which are lc otherwise it will not be useable. It’s an absolute nightmare.
because the standard allows both and some library code has not implemented the standard correctly, we get issues with case. #Azure#UUID