Enablement · 10
Check the account before you book the class
A training session for Microsoft Copilot fails in a dull way. The person has a device licence, or no Exchange Online mailbox, or a network that blocks the Copilot endpoints, or third-party cookies off in the browser so Word, Excel and PowerPoint for the web cannot run Copilot. Microsoft Learn lists those as requirements. They are also the attendance list.
What to check before the invite
Learn says users need a work or school account in Microsoft Entra ID. Mailbox-grounded experiences need a primary mailbox in Exchange Online, and Copilot is not available in a group mailbox. Desktop app experiences need Microsoft 365 Apps, and the Office Feature Updates task has to be able to run. OneDrive is required for some features.
The new address has to resolve
Learn notes that the Copilot app's primary URL is moving to copilot.cloud.microsoft, and that blocking the wider cloud.microsoft domain is not a supported way to pick and choose. If your proxy blocks it, the class will watch an error. Fix the path, or do not book the hour.
Personal and work stay apart
The updated app can show both accounts and still keep the data separate. Teach people to look at the account chip before they paste. FrontierOrg, a fiction, marks simulated screens as simulated so nobody confuses a story for access. Your screen is real. The account chip is the check.
Monday
Run Learn's lens on the ten people invited to the next session: Entra account, mailbox, app, and whether copilot.cloud.microsoft opens. Drop anyone who fails. Tell them why.
Who is about to be trained on a machine that cannot reach the service?
Sources: Microsoft Learn, Microsoft Copilot requirements (opens in a new tab). Microsoft Support, Copilot app updates for personal, work and school accounts (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.