Preview enrolment deserves the same ownership as a production release decision. It affects what employees see, what the service desk must support and which workflows need early validation. Microsoft’s October announcement makes this a useful time to revisit who participates and why.
What was announced in October
On 26 October, Microsoft announced that Frontier would expand in November to eligible previews for new Outlook for Windows, OneDrive, SharePoint and Teams. Participation is an optional administrator-controlled choice for selected users or groups, separate from Standard and Deferred release preferences for generally available features. [1]
Microsoft says existing Frontier participants will receive eligible previews across the expanded products without re-enrolling. Targeted release users are not automatically enrolled in Frontier. Product licensing still applies; a Copilot licence is not a universal prerequisite for joining the programme. [1]
The distinction matters: this is an October announcement about a planned November expansion, not a claim that every preview was available in every tenant during October.
Review membership before expanding the pilot
Start by documenting the pilot’s current purpose. A group created to explore AI features may have a different risk profile when it also receives collaboration and file-management previews. Ask the group owner to review business roles, support needs and the data used for testing.
I would include an administrator, a service-desk representative and business users with clearly defined workflows. Avoid a pilot made entirely of enthusiastic technology specialists: it can miss everyday usability problems. Keep membership deliberate and review it when people change roles.
Maintain one preview register
Use a simple register with the feature, announcement date, expected rollout, licensing dependency, affected users, test owner and decision date. Separate what Microsoft has announced from what is actually observed in your tenant. An unavailable feature should be recorded as pending, rather than marked as a failed test.
For each selected preview, define the business question. Examples include whether a workflow reduces manual steps, whether support staff can diagnose a failure and whether the feature fits existing information-handling rules. This gives the pilot an outcome beyond collecting screenshots.
Agree evidence and stop criteria
- Usability: can the representative user complete the task without undocumented workarounds?
- Access: does the experience respect the intended content and user boundaries in the test scenario?
- Operations: can support identify the preview participant and reproduce the issue?
- Recovery: is there a documented way to stop participation or recover the affected workflow, with any limitations understood?
Use non-sensitive examples when a production dataset is unnecessary. Preserve the original business artefact before testing editing or automation behaviour. Define which failures stop the pilot and which can be accepted temporarily with a workaround.
Make a documented November decision
My recommended output is a short decision record: retain the existing group, narrow it or expand it for a stated purpose. Include who approved the scope, the next review date and how participants should report issues. Explain that leaving a preview may not undo content changes already made.
Check tenant Message centre communications before implementation. Release preferences, pilot enrolment and application update channels should each have an explicit owner; avoid assuming one setting expresses every aspect of the organisation’s release strategy.
For the broader governance approach, see Prepare, secure and adopt Microsoft 365 Copilot.
Microsoft references
Sources checked 2 November 2026. Coverage focuses on October announcements through 31 October. Recommendations are proposed implementation practices; validate availability, licensing and requirements in your tenant before rollout.