Shadow AI & agent governance
Find the shadow AI tools that have your company data, and decide which ones stay.
Staff may be using unapproved chatbots, agents and connected applications. Review the tools visible in your available logs, what data they can access and who is responsible for each one.
What this looks like in real life
Someone mentions in passing that the month-end close is "so much faster now with the AI". Nobody in IT approved any AI. A look at app-consent and cloud-app reporting turns up chatbots in regular use, a spreadsheet plugin wired to an external model, and an automation an analyst built that emails customer data to a tool nobody recognizes. Each was adopted with good intentions, and each is a door out of the tenant that nobody owns.
What was at risk
- Customer and financial data pasted into consumer chatbots with no retention control.
- An unsanctioned agent moving data to a third party nobody vetted.
- No answer for an auditor asking which AI tools touch company data.
The work that resolves it
a read-only inventory of the AI applications and connectors visible in the available tenant evidence. Each entry has an owner or an unresolved-owner flag, a recommended allow, watch or block decision and its supporting evidence. The client confirms those decisions. Consent revocation, blocking and an approval workflow are scoped separately; tools used entirely outside company accounts and devices may be invisible.
The relevant scope
Start with a defined piece of work
The scope, the price, and how you will know it is finished are agreed in writing before anyone is given access. Review the engagement below for its deliverables, responsibilities and acceptance criteria.
The engagement
Shadow AI and Agent Discovery Audit
A read-only inventory of discovered tools with evidence, ownership and recommended allow, watch or block decisions. You receive a prioritized correction plan; enforcement and an approval workflow are separately scoped. Coverage follows the available evidence and ongoing governance remains with your internal team or MSP.
What you walk away with
What the evidence looks like
What you receive · illustrative sample
An inventory your team can act on.
Illustrative read-only discovery record. Recommendations do not revoke or block access during the audit.
| Discovered tool | Evidence and reach | Recommended decision |
|---|---|---|
| Sample reporting assistant | OAuth grant; selected business data | Review with named owner |
| Sample document helper | Available application inventory | Confirm purpose and licensing |
| Unattributed connector | Consent exists; owner unresolved | Investigate before changing access |
A representative deliverable. Yours is built on your own tenant.
Result tested before handoff
Every change is checked against what was agreed before the work is signed off, by the one engineer who scoped it and ran it.
Changes in approved windows
Nothing changes until the scope is agreed in writing. Changes to live systems run in windows the business approves, with the way back agreed before the window opens.
Fixed scope
A defined deliverable and a written test for when it is finished, agreed before anything starts.
Not sure this is the one?
Describe what happened, in a paragraph. A reply comes within one business day with the most direct next step, or a clear answer that AZ Innovations is not the right fit.
Discuss the scope and quoteWhat happens next
- 1Describe what happenedA few short fields: company size, environment, and what is going wrong.
- 2A reply within one business dayThe most direct next step, or a clear answer that AZ Innovations is not the right fit.
- 3A fixed-fee proposalNamed scope, price, and how you will know it is finished. No obligation.