Sample domain · public signals only · no internal access
Shadow AI is the use of AI assistants and automation tools with work email, files, calendars, or chat without the organization's approval or governance.
Shadow AI is an ownership question before it is a tool question.
Short answer: Shadow AI is the use of AI assistants and automation tools that nobody in IT approved, most often connected to a company's email, calendar and files by an employee clicking "accept" on a sign-in prompt. The risk is not the AI itself. It is the standing permission the employee granted, which can keep working after the password changes and which nobody reviews. For an MSP, a list of the AI tools already connected to a prospect's tenant is one of the most concrete things you can put on the table in a first meeting.
How shadow AI gets in
Nobody installs shadow AI. An employee signs in to a new assistant with their work account, sees a screen asking for access to mail and files, and clicks yes because that is what the screen is for. The tool now holds a token with whatever it asked for. Multiply that by every curious person in a thirty-seat office and you have a tenant full of connections the owner has never heard of.
Kaseya's 2026 SaaS Security Report, built from 27.6 billion security events across more than 50,000 small-business environments in 2025, names this as one of its six major findings: AI assistants, automation tools and collaboration apps are spreading through business tenants on single sign-in grants, and each one is another connection into email, files, calendars and chat.
The report makes a point every MSP should repeat to clients: a grant of this kind can stay active through its token after the user's password is changed or reset. Resetting the password after a scare does not close the door the app came through.
Why MSPs keep underselling it
Clients want this conversation. In Kaseya's 2026 State of the MSP Report, a survey of 1,061 MSPs, 48 percent said AI and automation will be their clients' top IT need this year, ahead of security at 42 percent. Yet only 13 percent of those MSPs said AI and automation is a meaningful revenue source today.
That gap is a packaging problem. Most MSPs are waiting for a client to ask for "AI services." The owner is not going to ask for a product category. The owner will react to a sentence like "four AI tools have standing access to your finance manager's mailbox, and two of them were approved by people who no longer work here."
The same survey found 34 percent of MSPs expect AI to increase security risk for their business in 2026. Shadow AI is where that risk shows up first in a small tenant, and it is the easiest AI conversation to start because it begins with something the client already did.
What to look for in a tenant
Four questions cover most of it. Which third-party apps hold consented access, and to what (mail, files, calendar, directory). Who granted each one, and is that person still employed. When each app last signed in. Whether any grant is broader than the tool plausibly needs, such as a note-taking assistant with read access to every mailbox.
Kaseya's recommendations line up with that list: audit connected apps and remove the unused ones, hold third-party permissions to least privilege, require review before new connections are approved, and watch for unusual consent requests.
None of this requires opening a single email or document. The grants, the scopes and the sign-in dates are configuration. That matters when you are asking a prospect for access before they are a client.
Turning the finding into a service
Once the list exists, the service writes itself. A one-time cleanup: revoke stale and over-scoped grants, set consent so new connections need approval. A policy: which AI tools the company endorses and what data they may touch. A monthly review: new grants since last month, reported to the owner in plain language. That is a defined AI governance offering with a scope and a price, which is exactly the packaging the 13 percent revenue figure says most MSPs have not built yet.
Frequently asked questions
What is shadow AI?
Shadow AI is the use of AI tools inside a business without IT approval or oversight, usually by employees connecting AI assistants to their work email, files or calendar through a sign-in consent screen.
Why is shadow AI a security risk?
Connected AI apps can hold standing access to business data through tokens that stay valid after a password change, according to Kaseya's 2026 SaaS Security Report. If an app is malicious, compromised or simply over-permissioned, that access is invisible to anyone not reviewing the tenant's app grants.
How common is AI demand among MSP clients?
In Kaseya's 2026 State of the MSP Report, 48 percent of 1,061 MSPs named AI and automation as their clients' top IT need for 2026, yet only 13 percent reported AI as a meaningful revenue source.
How do you find shadow AI in Microsoft 365?
Review the third-party applications with consented permissions in the tenant, the scopes each one holds, who granted it and when it last signed in. This is configuration data and does not require reading any mail or files.
How can an MSP sell AI governance?
Start from the prospect's actual connected-app list, then offer a defined cleanup, an approved-tools policy and a recurring review. A concrete finding gives the owner a reason to buy that a generic "AI services" pitch does not.
How SCOUTz gets you there
SCOUTz is prospect intelligence for MSPs, and shadow AI is one of the findings it was built to surface. With a prospect's read-only consent, SCOUTz lists the third-party and AI applications connected to their tenant, what each one can reach, who granted it and whether it is still in use, and it reads configuration only, never mailbox or file content. The result lands in a branded report in your MSP's name with a work plan attached, so your first AI conversation starts from the prospect's own tenant instead of a slide about trends. Point it at any client and walk out with a deal. The open beta is free for thirty days at scoutzsecurity.io.