THE QUESTION THIS NOTE ANSWERS
Your Clients Already Connected AI. Here’s What the Tenant Can Prove.Every MSP is preparing for the conversation where clients ask about adopting AI. I have news: the adoption already happened. It just didn't go through you,…
RELATED REAL EXAMPLE · NOT A NEW SCAN
Administrator authentication methods need review.
Owner-supplied real Microsoft 365 review · October 16, 2026 · client details removed. This example illustrates the evidence workflow, not the full scope of this article.
Means
Registration and enforcement need separate evidence; a missing method does not by itself prove every sign-in is unprotected.
Do
Validate the condition and context, agree an authorized change, then verify the relevant observation.
Worth
Review the LOE in hours. Your hourly rate configured in Settings × agreed LOE gives the estimate—not guaranteed revenue.
EXPLANATORY DIAGRAM · EVIDENCE AND LIMITS
Connected app → granted access → evidence to investigate.
Inventory
Identify the app, publisher and owner from supported sources. Presence alone is not misuse.
Access type
Separate delegated permissions from application permissions; review consent and resource scope.
Credentials
Review supported credential metadata and expiry. A user password reset does not revoke every app credential.
Decision
Confirm business purpose, activity evidence and the owner before agreeing a change.
Every MSP is preparing for the conversation where clients ask about adopting AI. I have news: the adoption already happened. It just didn't go through you, or through anyone.
It went through a consent screen. Somebody in accounting found an AI tool that summarizes spreadsheets. Somebody in sales connected a meeting notetaker. Somebody in operations signed up for an assistant that reads email and drafts replies. Each time, a screen appeared listing permissions in gray text, and each time, a busy person clicked accept in roughly three seconds, the same way we've all accepted terms of service since the internet began.
Read those permission lists sometime. Read your files. Read your mail. Access your calendar. Maintain access to data you have given it access to. That last one matters more than people realize: the grant persists. The notetaker from a webinar in March still holds its permissions in November. Multiply that by every employee who ever tried an AI tool, and the average SMB tenant now has a population of AI vendors holding standing access to company data, none of it inventoried, none of it approved by anyone with authority to approve it.
I want to be careful here, because the wrong response is panic. Most of these tools are legitimate. Employees connected them to work faster, not to exfiltrate anything, and blanket-banning AI is both futile and bad for the business. The right response is the boring one: know what's connected. You cannot govern what you haven't inventoried.
Availability note: This workflow depends on supported, customer-approved collector coverage. When that coverage is activated, the review can use available grant metadata to build a vendor matrix: which AI companies, holding which permissions, granted by whom, and when. It remains a configuration-and-metadata review; it does not inspect prompts, employee content, or private files.
For the MSP, that matrix opens the most current conversation in business right now. Not "should you adopt AI," which is settled, but "your people already adopted it, here's the map, let's decide together what's sanctioned." Which tools get blessed and centrally managed. Which get removed. What the approval path looks like going forward so the map stays clean.
That's AI governance as a service, and it starts with a single page most owners have never seen: the list of who they've already let in.
