Inherited Oversharing
Internal SharePoint and Teams folders have years of broad ‘company-wide’ links that Copilot will immediately surface in prompts.
CLOSED BY AI ACCOUNTABILITY
✓
AI GOVERNANCE & MICROSOFT 365 COPILOT READINESS
SERVICE FAMILY: AI
Who is responsible for what your AI can see, do and say?
THE WRITTEN PROMISE
Technology is easy. Accountability is harder. We establish permission boundaries, data governance, and adoption ownership before AI licences are switched on.
100% Written Scope Boundary
3 Tiers START · CORE · STRATEGIC
Named Senior Ownership
Designated Layer Mandate
AI Accountability
Contract Family
AI
Delivery Model
Outcome-Based · Fixed Tier
Boundary Status
Inclusions & Exclusions Written
Escalation Point
Senior Cape Town Engineers
OPERATIONAL DIAGNOSTIC
Signs nobody owns this yet
Microsoft 365 Copilot inherits every SharePoint, OneDrive, and Teams permission you have ever granted. Without AI Accountability, rolling out AI exposes historical oversharing immediately.
Shadow AI Usage
Staff paste confidential client, financial, or legal data into unapproved public AI tools because no governed workspace exists.
CLOSED BY AI ACCOUNTABILITY
✓
Licence Spend Without Adoption
AI licences are bought for executives, but nobody owns permission hygiene, prompt governance, or measuring commercial return.
CLOSED BY AI ACCOUNTABILITY
✓
WRITTEN SCOPE ARCHITECTURE
What we own — and what stays separate.
Ambiguity is where IT partnerships break down. We publish both what is included in AI Accountability and what is scoped separately so your team never discovers a gap mid-incident.
[!] WHAT STAYS SEPARATE, AND WHY
Scoped separately: Custom large-language-model (LLM) software development · third-party SaaS AI licences · legal regulatory sign-off · underlying Microsoft 365 Copilot licence fees.
We govern the Microsoft 365 data permissions, security guardrails, and operational readiness around enterprise AI; licence pass-through and custom software engineering are scoped separately.
CONTRACTED INCLUSIONS (5 CORE MANDATES)
FAMILY: AI
- Microsoft 365 data-permission and oversharing assessment across SharePoint, OneDrive, and Teams before AI rollout
- Sensitivity labelling, data classification, and DLP policy enforcement to govern what AI can index and surface
- Acceptable-use policy framework and shadow-AI guardrails aligned to POPIA and corporate confidentiality
- Phased Microsoft 365 Copilot licence readiness, role-based enablement, and executive adoption tracking CORE & UP
- Continuous AI posture governance, access drift reviews, and board-level AI risk reporting STRATEGIC
THE 4 BOARD GOVERNANCE QUESTIONS
1. Who owns the outcomes?
2. Who owns data governance?
3. Who owns staff adoption?
4. Who measures commercial ROI?
OPERATIONAL REALITY CHECK
Coverage and ownership are not the same thing.
GOOD TO KNOW // OPERATIONAL BOUNDARY RULE
Never switch on Microsoft 365 Copilot before auditing SharePoint permissions. Copilot does not create new access leaks — it makes existing permission mistakes instantly searchable by any licensed user. AI Accountability pairs directly with Security Accountability (DEFEND) →.
SERVICE TIER ARCHITECTURE
AI Accountability Stages & Tiers
A structured three-stage progression from permission hygiene to continuous AI governance.
STAGE 1 · READINESS
START: Readiness Audit
Permission hygiene, oversharing discovery, and AI governance baseline before licences go live.
Identifies exposed SharePoint/OneDrive sites, defines acceptable AI use, and establishes a clean pre-deployment boundary.
STAGE 2 · GOVERNED ROLLOUT
RECOMMENDED
CORE: Governed Enablement
Sensitivity labels, DLP technical controls, and structured Microsoft 365 Copilot deployment.
Remediates oversharing, applies information protection policies, and manages phased user onboarding and adoption.
STAGE 3 · CONTINUOUS OVERSIGHT
STRATEGIC: AI Governance
Ongoing permission drift auditing, shadow-AI controls, and executive ROI & risk oversight.
Keeps data boundaries clean as teams create new SharePoint sites and provides board-ready AI governance reporting.
Our services are deliberately modular. Network, backup, security depth, server and cloud are separate commercial decisions — never bundled implicitly into per-user pricing.
CONNECTED ACCOUNTABILITY LAYERS
What connects with AI Accountability
Every layer is modular by design and integrates cleanly with adjacent operational responsibilities.
QUESTIONS & CLARIFICATIONS
AI Accountability FAQs
Why do we need AI Accountability before buying Microsoft 365 Copilot licences?
Because Copilot automatically surfaces any file, email, or Teams chat a user technically has permission to view. In almost every mid-sized organisation, historical SharePoint folders have overly permissive sharing links that must be locked down before AI is enabled.
NEXT STEP