So in troubleshooting this:
I can in Arc Map do this:
Which gets me to the offending row, from which I can figure out what is wrong with an attribute or geometry that's causing the issue. From there I can make a decision to delete the feature, go under the hood in SQL to edit something, edit it in SDE, or create a local copy. Take home message is, via the feature service, I can sort on GlobalID.
In Pro...cannot sort GlobalID from a feature service. I can from a .geodatabase or a feature class, both of which take time and more mouse clicks to bring into a map but not a feature service. Is there a valid reason why this capability was removed?