I wrote a book. I hope you like it. https://t.co/rz5gctPaVf

Best analogy I can muster: Microsoft combing through customer cloud data because it might be inflammatory or illegal—legitimate concern but insufficient to overcome the interest in shielding enterprise data from 3rd parties. On this, Microsoft has a clear and correct policy:

I deserve no credit for flagging this issue. The concern was flagged for me by a law firm denied an exemption. I simply ran it down because their commendable commitment to reading the fine print’s fine print sparked my curiosity and sense of duty.

Small share ≠ zero. I have found law departments, law firms, and legaltech vendors painfully aware of abuse monitoring. Some have been granted exemptions. Most have been denied exemptions because they are “unmanaged.”

Microsoft Copilot is on a relatively short (not blank) list of exemptions. Some anecdata from talking to law departments, law firms, and legaltech vendors about this subject indicate:

Seems like a bad look. Further, I would be willing to wager a not insubstantial sum that Microsoft has exempted Microsoft—i.e., as an enterprise—from abuse monitoring (pure speculation).

https://t.co/8TMbIFtbIY

But you know who does qualify to turn off abuse monitoring, and has, in fact, opted out of abuse monitoring by Microsoft employees? ‍ ‍Microsoft Specifically, Microsoft Copilot

Absent anything official from Microsoft, my only option is to fall back on anecdote as the best available evidence. Based on the conversations I’ve had thus far, it seems very few customers and partners are managed and, therefore, eligible to turn off abuse monitoring.

And this, dear reader, is where my search skills reach their limit. What are the eligibility criteria and process for becoming a “managed customer” or a “managed partner” and therefore eligible to have abuse monitoring turned off? ¯\_(ツ)_/¯

Again, like turning off abuse monitoring, this appears, superficially, to merely be a matter of paperwork. An enterprise can register for Limited Access, BUT only if they are a managed account—a status for which they cannot register, per the same Limited Access resource:

https://t.co/wgXfPqb17R

This “managed customers” language is similarly present in the accompanying resource on Limited Access.

https://t.co/Ksdyn4iWtZ

"Limited Access criteria" starts to come into focus in the Azure OpenAI Limited Access Review form used to apply for “modified abuse monitoring”—also sometimes termed an “exemption” and meaning that abuse monitoring is turned off for specific use cases.

I underestimated how few would read down and take the steps necessary. AndI failed to read the fine print’s fine print to understand how few enterprises—clients, law firms, and legaltech companies—meet the “additional Limited Access eligibility criteria.”

Candidly, I had seen this before. But I did not think much of it because there is a mechanism for turning off abuse monitoring. I figured everyone would turn it off, and that would be that. How wrong I was.

If a prompt or generated content triggers the abuse monitoring system, the prompts and generated content are subject to human review by a Microsoft employee.

Excellent. But fine print follows. Below the blue box, we eventually learn that Microsoft has setup a process for “abuse monitoring.” Under their abuse monitoring program, Microsoft stores all prompts and generated content for 30 days.

https://t.co/gqNjF52cil

For most law departments, law firms, and legaltech vendors I have spoken to, this translates into an (erroneous) assumption that there is no added risk of disclosure when pairing AOAIS with private company data already stored on Azure—the same misimpression I was under.