Policy and register
Write an AI acceptable-use policy that fits how you work, and build a register of AI tools and agents with owners, data and purpose.
AI governance does not have to be a 60-page framework. We give you an AI acceptable-use policy, an AI app and agent register, an approval flow for new tools, staff guidance and the Microsoft controls that back it up, including governance for Copilot and AI agents.

For leadership teams, IT heads and compliance owners who need AI used safely across the business without slowing people down. We begin with the business context and the systems already in place, then shape a delivery path around what needs to work.
Most growing companies have AI everywhere and governance nowhere: no written rule, no list of tools, no owner for the AI agents people build. Customers, auditors and insurers have started asking how AI is controlled. A practical governance program answers them with a short policy, a register, an approval flow and technical controls that match what the policy says.
For leadership teams, IT heads and compliance owners who need AI used safely across the business without slowing people down. The first useful step is to define what needs to change, how the current environment shapes the work and which outcome the team needs to be able to assess.
The exact scope depends on your systems and constraints. These workstreams describe common parts of this solution area.
Write an AI acceptable-use policy that fits how you work, and build a register of AI tools and agents with owners, data and purpose.
Back the policy with Microsoft controls: DLP for AI, app approval, Entra ID access, agent identities and audit logs.
An approval flow for new AI tools, staff guidance, quarterly reviews and evidence your auditors and customers can see.
AI questions now appear in security questionnaires, vendor reviews and audit requests. A short, real governance program answers them, and protects the business while people keep using AI.
Enterprise customers ask which AI tools touch their data and how that is controlled.
ISO 27001 and SOC 2 auditors ask how AI tools fit into access control, data protection and supplier management.
Privacy laws such as GDPR and the DPDP Act apply to personal data whether it goes into a spreadsheet or an AI prompt.
Copilot Studio and other agents act on company data. Each one needs an owner, an identity and limits.
AI subscriptions and usage spread across teams with no view of what is spent or why.
One leaked customer file in a public AI tool is enough to lose a contract.
We keep it proportionate to your size. The documents are short enough that people read them, and every rule has a control behind it.
Which AI tools are approved, what data may go into them, what needs approval and who to ask.
Every AI tool and agent with owner, purpose, data, users, account type and review date.
A simple request and review process for new AI tools and agents, with a risk checklist.
Agent identities and permissions with Entra ID, Copilot Studio controls and, where available, Microsoft Agent 365 (some features in preview).
DLP for AI, app approval in Defender for Cloud Apps, admin consent for AI add-ons and audit logs.
A short training session and a one-page guide on using AI safely at work.
We do not certify you. We map your AI controls to the frameworks you are working towards and give your auditor clear evidence.
The AI management system standard: policy, risk assessment, AI inventory and lifecycle controls, used as a readiness guide.
AI tools and agents brought into access control, supplier management, logging and data protection controls.
Govern, map, measure and manage, used as a simple structure for AI risk decisions.
Personal data in AI tools handled in line with GDPR, the DPDP Act and similar rules.
A practical starting point for a company of 20 to 500 people.
Request an assessmentMove from a defined initiative to an operating system through focused, reviewable stages.
Agree on the users, business context, systems and constraints that define the initiative.
Connect architecture, integrations, data, security and delivery decisions to the needs already identified.
Deliver and review the system in stages so the work can respond to product and operational feedback.
Consider ownership, monitoring, support and the next improvements as part of the delivery plan.
AI governance is the set of policies, roles and controls that decide which AI tools and agents a company uses, with what data, under whose ownership, and how that is checked.
Yes, in proportion. A short policy, an AI register, an approval flow and a few technical controls cover most of the risk, and answer customer and auditor questions.
Approved tools, data that must never go into AI, rules for personal accounts, how to request new tools, human review of AI output, and who owns the policy. Our free template covers each of these.
Each agent gets an owner, a purpose, a list of data sources and actions, its own identity with least-privilege access, and logging. On Microsoft 365 we use Entra ID, Copilot Studio controls and, where available, Agent 365.
We do not issue certifications. We help you put the AI policies and controls in place and prepare evidence; an accredited certification body performs the audit.
A governance program usually takes three to six weeks, depending on how many AI tools and agents are already in use.