Back to Blog

    Microsoft Copilot

    Rolling out Microsoft 365 Copilot: our six-phase approach

    How we roll out Microsoft 365 Copilot: prerequisites, six phases with durations, a pilot with 25–50 people, champions and an FADP checklist.

    April 15, 20263 min read
    CNEXT

    CNEXT

    CNEXT GmbH, Bern

    mail@cnext.ch
    CNEXT AI Agent
    In this article

    Microsoft 365 Copilot requires a Copilot licence and an eligible base licence; for email grounding, the primary mailbox must be in Exchange Online. From there we roll out Copilot in six phases, from use-case analysis through a permissions review and a pilot with 25–50 people to ongoing governance.

    What Microsoft 365 Copilot is

    Microsoft 365 Copilot is the generative AI capability built into Microsoft 365 in Word, Excel, Outlook, Teams, SharePoint and PowerPoint. Copilot accesses emails, documents, chats and calendars through Microsoft Graph and can summarise, create or rework content. It is not the same as Microsoft Copilot Studio: Copilot is the application for employees, while Copilot Studio is the tool for building your own agents.

    Prerequisites

    • Licences: Microsoft requires a Copilot licence and an eligible base licence. The possible combinations change; the current Microsoft licensing overview is authoritative.
    • Technical: Microsoft's technical minimum requirements apply. For email grounding, the primary mailbox must be in Exchange Online.
    • Permissions: Copilot works with the existing permissions; it does not fix overbroad sharing. Long-established SharePoint permissions, open sharing links and groups such as ‘Everyone except external’ should therefore be reviewed before the pilot.

    Our six-phase approach

    1. Discovery and licence analysis (1 week)

    • Identify the top 20 use cases per department
    • Plan licences by persona, as not everyone needs Copilot
    • Build the business case on your own baseline: record effort and quality for the key tasks before the pilot

    2. Tenant readiness (2–4 weeks)

    • Permissions audit in SharePoint with our SharePoint Storage Monster and Microsoft Purview
    • Revise open sharing links
    • Enable Restricted SharePoint Search where needed

    3. Data classification and sensitivity labels (3–6 weeks)

    The scope and depth of this phase depend on the organisation's requirements. Typical building blocks:

    • Define a label taxonomy, for example Public / Internal / Confidential / Highly confidential
    • Auto-labelling policies for sensitive content such as personal data, financial data and patents
    • DLP rules for Copilot and, where needed, retention policies

    4. Pilot with 25–50 people (4 weeks)

    • Pilot group from 3–4 departments with a defined use-case catalogue
    • Check in advance whether pilot users can access the relevant SharePoint, OneDrive and Exchange content
    • Check answers against the source material; record errors, rework and non-use
    • Gather feedback via Microsoft Viva Pulse or Forms
    • Weekly office hours

    Based on these observations, you decide on further users, training and governance.

    5. Adoption and scaling (ongoing)

    • Persona-based training; our workshops are available in German, English and French
    • Champions programme with one champion per 25 users
    • Prompt libraries on the intranet
    • Measuring success with the Microsoft Copilot Dashboard

    6. Governance and optimisation (ongoing)

    • Quarterly audits
    • Adoption metrics such as DAU/MAU and use-case coverage
    • Ongoing tenant hygiene

    Measuring the benefit

    The benefit is measured against the baseline from phase 1: effort and quality for the same tasks before and after the pilot. This is set against the total effort, including licences, preparation, training and operations.

    Data protection: our Swiss FADP (nDSG) checklist

    • Clarify data residency for SharePoint, Exchange and OneDrive (see our guide to data residency in Microsoft 365)
    • Keep the current DPA with Microsoft to hand
    • Extend the record of processing activities under Art. 12 nDSG to cover Copilot
    • Inform employees in line with Art. 19 nDSG

    Limits

    • Copilot's licence combinations, features and technical requirements change; the linked Microsoft pages are authoritative.
    • The durations in weeks are guide values from our approach.

    Sources

    Microsoft 365Microsoft CopilotSchweiz
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    CNEXT

    CNEXT

    CNEXT GmbH, Bern

    Plan a Copilot rollout

    We support you from the pilot to the organisation-wide rollout, with workshops in German, English and French.