On 17 November 2026, Microsoft presented Copilot Workspaces at Ignite as the successor to Copilot Notebooks. The idea is to give a team a shared place to work on a project with Copilot, using the same files and working documents. Microsoft lists the new collaborative experience under its Frontier public preview programme. Microsoft’s Ignite announcement
I would try it on a handover that takes too much explaining. Imagine the colleague who planned a fabrication job is going on leave. Their deputy needs to know which drawing the customer accepted, when the job is due and what still needs chasing. The handover is finished when the deputy can pick up the job and explain what they will do next.
Decide what the deputy needs to know
Sit with the person handing over and ask them to show you where they would look to answer the deputy’s questions. The accepted drawing might be in SharePoint, the promised delivery date in the order system and the reason for a delay in a project note. Agree which record settles each question if the files disagree.
I would write a brief with four fields: the latest agreed position, the next action, who owns it and what is still awaiting confirmation. Give the deputy a link to the record behind each important date or decision. If the order system holds the delivery promise, have someone check it there and record when they checked it.
When you have access to the feature, start the trial with enough material to prepare that brief. A link to an approved drawing and the decision accepting it is a useful starting point. The whole project archive may include superseded drawings and emails that propose changes nobody agreed to. Keep historical records where they belong and make the accepted revision easy to identify.
Check what you’re about to share
Microsoft says existing notebooks will become workspaces automatically. Material already added or created stays in place, and existing sharing continues. Ask whoever manages Microsoft 365 to check the Message centre for your organisation’s rollout details. Microsoft’s guide to the switch from Notebooks to Workspaces
If you plan to reuse a notebook, open it before inviting anyone else. Look through the existing pages as well as the linked files. A working page might already contain an estimate that the project team was never meant to see. Where the old material serves a different audience, I would start with a fresh workspace for the handover.
- Existing notebook contentReview what would come across if you reuse a notebook.
- Files and pagesCheck what the deputy needs and which version they should use.
- People in the workspaceConfirm who needs to take part and check access with their accounts.
Ask the deputy to open the workspace and follow the links from their usual work account. If they cannot open the drawing, ask the file owner whether the deputy should have access and how to grant it through your normal process. Check access to the finished handover brief as well. A draft can carry information from a source that its eventual readers would otherwise have no reason to see.
Try a change the team has to catch
Include a job where something changed late. For the fabrication example, give the team approved test material where a proposed delivery date appears in the notes and a different date was subsequently agreed. See whether the draft distinguishes the two and whether the deputy can find the record that confirms the agreed date.
I would ask the person handing over to check the draft against the named records, then ask the deputy to read it without a running explanation. Can they open the accepted revision? Can they tell what to chase and who has agreed to do it? Any answer that relies on someone remembering a conversation belongs in the handover record.
Decide whether to use it again
During November, pick the next handover and agree a trial date with the people doing the work. While you wait for access, try the same brief in a shared document using the tools you already have. That establishes which records and permissions the handover depends on and gives you a way to compare the two approaches.
When Workspaces is available to your team, compare the time to assemble and check the brief, then ask the deputy which questions still needed a call. I would keep the shared Copilot setup if it makes the handover easier to prepare and easier to use. If the team still has to ring around to establish which drawing was accepted, fix where that decision gets recorded before expanding the trial.