Alliance corporate platform
Our own bilingual corporate platform: five practice sites, projects, insights, search and lead capture on an edge-hosted, near-zero-JavaScript architecture.
Client engagement · Professional services
A tenant secured and cleaned up before AI arrived, so Copilot could be switched on without surfacing what it should not.
01
A professional services firm wanted to adopt Microsoft 365 Copilot but was concerned about what it might surface. Years of project work had left client files shared more widely than intended across SharePoint, OneDrive and Teams.
We secured the tenant and cleaned up access first, then rolled out Copilot to a pilot group with guidance, measurement and a clear path to wider adoption.
02
Years of ad-hoc sharing had left sensitive client files reachable by far more people than intended. Leadership wanted Copilot, but not until the data underneath it was under control.
Many sites had been shared with the whole organisation for convenience, and anyone-with-the-link sharing had been used for external collaboration. Several project teams no longer had an active owner.
Sign-in security was inconsistent: some administrators used the same account for daily email and tenant administration, and legacy authentication was still allowed for a handful of older devices.
03
04
Tenant security review covering identity, devices, sharing settings, external access and audit logging, plus reporting on overshared sites, broad links and sensitive content.
Phishing-resistant MFA for administrators, separate admin accounts, conditional access policies, blocking of legacy authentication and compliant-device requirements for sensitive apps.
Broad and anonymous links removed from sensitive libraries, owners assigned to every team and site, inactive sites archived, and high-risk sites excluded from organisation-wide discovery while they were fixed.
A small set of sensitivity labels, from Public to Highly Confidential, with defaults applied at site level for client matters so staff did not have to label every file by hand.
Copilot enabled for a cross-department pilot group with role-based prompting guides, office hours and feedback loops, followed by a phased rollout plan.
05
06
Matter-level access was reviewed with practice leads so that ethical walls and client restrictions were reflected in permissions before Copilot went live.
Data handling for Copilot was documented against the firm’s privacy obligations under PIPEDA and, for Quebec clients, Law 25.
Permission changes were communicated to affected teams in advance, with a simple route to request access back where it was genuinely needed.
07
Copilot went live on a tenant with clear ownership and labelled data, and the permission clean-up improved security for every user, not only those with AI licences.
08
A quarterly access review, alerts on new broad-sharing links in sensitive sites and usage reporting keep the tenant in good shape as Copilot use expands.
Our own bilingual corporate platform: five practice sites, projects, insights, search and lead capture on an edge-hosted, near-zero-JavaScript architecture.
One accountable IT team for several plants and a head office: monitoring, patching, identity security and a helpdesk that knows the shop floor.
An AI agent that reads incoming tickets, classifies and routes them, and drafts first responses for a technician to approve.
Talk to us
A 30-minute consultation with a senior consultant. You leave with a clear next step — whether or not it involves us.