Commercial licenses are long and frequently contain terms that are unintuitive or ambiguous which are trivial to violate when most of the employees using the software aren't aware they exist.

And the easiest way to violate them is simply to have installed more copies than you're licensed for, which is an issue the GPL doesn't have.

Trying to figure out exactly which production licenses were needed to be in compliance used to be a recurring nightmare back in the day when I did B2B bespoke system rollouts. A licensing guide, not the license itself but the document trying to explain which licenses have to be acquired under which circumstances, could run well over 100 pages. Microsoft had licensing specialists that the channel could call for help, but if you called them twice or more for the same case you would never get the same answer twice. It was that complex, their own specialists couldn't make heads from tales on it.

>Microsoft had licensing specialists that the channel could call for help, but if you called them twice or more for the same case you would never get the same answer twice.

Do they preface with a "I'm not a lawyer" disclaimer and claim that anything they say is non binding?

And that service only exists as leadgen.

Unless it's with Oracle.