Skip to content 
Employees are adopting AI tools faster than many companies can approve, monitor or govern them. That creates a new version of shadow IT called shadow AI: the use of AI applications, agents or features outside an organization’s approved technology process.
The problem is not simply that employees are breaking rules. In many cases, they are trying to complete work faster with tools that are easy to access. The security challenge is to make safe AI use easier than unsafe AI use.
What Shadow AI Means in the Workplace
Shadow AI includes any AI service used for work without the organization’s knowledge, approval or appropriate controls.
Examples can include:
- pasting internal documents into a consumer chatbot
- using an unapproved coding assistant with proprietary source code
- connecting an AI agent to company email or cloud storage
- uploading customer data to an external summarization tool
- using browser extensions that send page content to third-party AI services
- creating automated workflows with AI tools that IT does not monitor
The risk varies widely. Asking a public chatbot to rewrite generic text is very different from connecting an autonomous agent to sensitive business systems.
Shadow AI Is Already Common
The exact adoption rate varies by survey and country, but several large studies show that unapproved AI use is not a fringe behavior.
Microsoft reported in a United Kingdom study that 71% of employees surveyed had used unapproved consumer AI tools at work, with 51% saying they did so weekly. IBM separately reported in late 2025 that 80% of U.S. office workers surveyed were using AI at work and only 22% used employer-provided tools exclusively.
Microsoft’s UK shadow AI report
Those surveys should not be treated as universal statistics for every workforce. They do show why companies need a practical governance model rather than assuming employees will wait for formal approval.
Why Employees Use Unapproved AI Tools
The reasons are usually operational.
AI tools are easy to sign up for, many have free plans, and employees can see an immediate benefit for writing, research, coding, analysis and administrative work. Traditional enterprise procurement can take weeks or months, while a consumer AI tool can be opened in seconds.
Employees may also use an unapproved tool because the approved option is difficult to access, lacks a needed feature or has not been explained clearly.
This creates an important governance lesson. A policy that only says “do not use AI” is unlikely to work if employees can see obvious productivity value and have no approved alternative.
The Biggest Risk Is Data Leaving the Intended Boundary
The most serious shadow AI problem is usually data handling.
Employees can accidentally send:
- customer information
- financial records
- source code
- contracts
- internal strategy documents
- credentials or configuration details
- personal or regulated information
to a service that has not been reviewed for security, privacy, retention or contractual use.
The organization may then have little visibility into where the data went, how long it is retained or whether the tool is allowed to process it.
The solution starts with data classification. Employees need simple rules that explain which information can be used with approved AI tools, which information needs extra controls and which information should never be submitted to external services.
AI Agents Increase the Risk Beyond Chatbots
An AI chatbot usually responds to a prompt. An AI agent can be given tools and permissions to perform actions.
That means a shadow AI agent might connect to email, calendars, cloud files, CRM records, code repositories or business applications. If those permissions are too broad, the risk is no longer limited to one pasted document.
Microsoft’s 2026 Cyber Pulse highlighted the governance challenge around unapproved AI agents and warned that organizations need visibility into which agents are being used and what they can access.
Microsoft Cyber Pulse on AI agent governance
For agents, companies should govern identity, permissions and actions just as seriously as they govern the model itself.
Do Not Start With a Blanket Ban
Blocking every AI website can reduce one visible form of shadow AI while pushing employees toward personal devices, browser extensions or less visible tools.
A better approach combines control with usable alternatives.
The organization should publish a short list of approved AI services for common tasks. Employees should know which tool to use for writing, coding, meeting summaries, research or other approved workflows.
When a new tool is requested, provide a fast review path. If the only process is a long procurement queue, employees have an incentive to work around it.
Build an Approved AI Catalog
An approved AI catalog does not need to be complicated. For each tool, document:
| Field | What Employees Need to Know |
|---|---|
| Approved use | Which tasks the tool is allowed to perform |
| Data level | Which types of company data can be entered |
| Login method | Whether company SSO is required |
| Agent access | Which connected systems or tools are permitted |
| Human review | Which outputs or actions must be checked |
| Owner | Who reviews the tool and handles questions |
This gives employees a usable answer instead of a vague policy.
Use Identity and SSO to Reduce Unmanaged Accounts
Approved enterprise AI tools should use centralized identity where possible.
Single sign-on, role-based access and automated offboarding make it easier to control who can use the service. They also reduce the number of personal accounts employees create with corporate data.
For higher-risk AI tools, consider conditional access rules, stronger authentication and tighter permissions for integrations.
The goal is to make access visible and revocable.
Monitor AI Use Without Treating Every Employee as a Threat
Organizations need visibility, but monitoring should be proportionate and transparent.
Depending on the environment, security teams may use browser controls, network telemetry, cloud access security tools, data loss prevention and application discovery to identify unapproved services.
The useful output is not a list of employees to punish. It is a map of where policy and real behavior do not match.
If hundreds of employees are using the same unapproved tool, that may indicate a legitimate workflow need that the approved stack is not meeting.
Focus on High-Risk Data and Actions First
Not all AI use deserves the same control level.
A risk-based model can separate:
- Low risk: public information, generic writing help and non-sensitive brainstorming
- Moderate risk: internal documents, routine operational data and approved code contexts
- High risk: customer data, regulated data, credentials, privileged code, legal material and autonomous actions
Apply the strongest restrictions to the highest-risk data and actions instead of trying to govern every prompt identically.
Train Employees on Real Examples
A one-page AI policy is not enough if employees cannot recognize risky situations.
Training should use practical examples:
- Can I paste this customer email into the approved assistant?
- Can I upload a contract for summarization?
- Can an AI coding tool access a private repository?
- Can I connect an agent to my work email?
- What should I do if the AI output contains confidential information?
- How do I request approval for a new AI tool?
The answers depend on company policy, but employees need clear answers before they are under deadline pressure.
Measure Whether Governance Is Working
Useful metrics include:
- number of discovered unapproved AI tools
- percentage of AI users on approved services
- high-risk data-loss prevention events involving AI
- time required to review a new AI-tool request
- number of agents with high-risk permissions
- inactive AI accounts that should be removed
- employee training completion and policy questions
The objective is not zero experimentation. It is controlled experimentation with clear visibility and boundaries.
A 30-Day Shadow AI Cleanup Plan
Week 1: discover which AI services and agents employees are actually using.
Week 2: classify the tools by data access and business risk. Identify the most common legitimate use cases.
Week 3: publish an approved-tool catalog and simple data rules. Give employees a clear request path for new tools.
Week 4: enforce controls around high-risk services, connect approved tools to centralized identity and begin regular monitoring.
Then review the environment monthly because the AI tool landscape changes quickly.
For a broader governance framework, read our enterprise AI strategy guide and enterprise AI security gaps guide.
Final Takeaway
Shadow AI is not mainly a story about careless employees. It is a sign that useful technology is spreading faster than internal governance.
Companies can reduce the risk by making approved AI easy to use, defining data boundaries, controlling identity and agent permissions, monitoring high-risk activity and giving employees a fast way to request new tools.
The strongest policy is not “no AI.” It is a clear operating model that tells people which AI they can use, what data they can use with it and which actions require additional approval.
Author
Talha Qureshi is the founder and technology writer behind ITechTrove. He covers enterprise AI, cybersecurity, cloud infrastructure, B2B SaaS and emerging technology, focusing on practical guides, analysis and source-based reporting.
