How to inventory AI tools, agents and assistants across your organization
Diesen Beitrag auf Deutsch lesen
Build a current AI inventory from tenant and identity signals, recording ownership, users, data reach and risk for every tool or agent.
TL;DR
Start with Microsoft 365 Copilot licences and usage, Copilot Studio and SharePoint agents, then add Entra ID enterprise applications and licensed services such as Claude Enterprise and ChatGPT Enterprise. Record owners, users, data reach and risk, and refresh the inventory on a fixed cycle because new tools appear monthly.
Original by Rencore, on Rencore. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: Discover Copilot Studio and SharePoint agents, tenant licences, Entra ID applications and licensed external services, then refresh entries on a fixed cycle.
- Security/Compliance: Prioritize ownerless applications with Microsoft Graph permissions and assess each entry by data sensitivity, action breadth and user count.
- Makers: Provide an accountable owner, users, knowledge sources and data reach for every agent so it can be reviewed and governed.
Frequently asked questions
How should an organization discover AI services beyond Microsoft 365 Copilot?
Review consented enterprise applications in Entra ID and add AI services licensed outside Microsoft, including their member lists. Surveys can fill gaps but should not be the foundation.
Which fields belong in an inventory record for a Copilot Studio agent?
Record the owner, users, data reach, capabilities, risk rating and review date. For agents, also capture the environment, knowledge sources and sign in requirement.
Why should Entra ID applications without owners be reviewed first?
Ownerless applications with Microsoft Graph permissions can read company data without anyone accountable for them. They are the first entries to investigate.