
Nick Ross [MVP] (T-Minus365) published a YouTube video that explains how to get early access to Microsoft’s experimental AI features through the Frontier program. The video walks viewers through what Frontier is, how to enable it in a Microsoft 365 tenant, and how to control which users receive prerelease Copilot features. In short, Ross frames Frontier as the pathway for IT teams and managed service providers to preview capabilities before they reach general availability.
The video defines Frontier as an opt-in early-access channel for new Copilot experiences inside Microsoft 365. Ross shows that Frontier surfaces pre-release features directly in familiar apps such as web-based Word, Excel, and Copilot chat, and that Microsoft sometimes labels those items clearly so users can tell they are previews. Consequently, organizations can test new agents and features in production-like settings without waiting for broad rollout.
Ross also notes that enrollment varies by subscription, licensing, and tenant settings, and he stresses that some preview features target enterprise Copilot licenses while others reach individual subscribers. He observes that Microsoft expands Frontier gradually, so availability depends on the feature and the current deployment phase. As a result, some organizations will see updates weeks or months before others.
The video provides a practical walkthrough for administrators who want to enable Frontier in the Microsoft 365 admin center. Ross explains the basic steps: perform pre-flight checks to ensure tenant readiness, enable Frontier at the tenant level, and then scope access to specific users or groups so previews do not reach everyone immediately. This scoping capability supports staged pilots and reduces the risk of unexpected user exposure.
Ross also covers approval workflows for Microsoft agents and the need to explicitly allow certain preview agents when they appear in the app store or admin settings. He emphasizes that administrators should monitor feature visibility after enabling Frontier since some items can take time to appear due to phased rollouts or service-side conditions. Therefore, patience and systematic checks are part of the process.
According to Ross, Frontier gives IT teams and MSPs a strategic advantage: they can test new AI features before end users begin asking for them. By previewing capabilities early, teams can develop documentation, refine internal workflows, and prepare training materials so adoption is smoother when features reach general availability. This proactive stance reduces last-minute firefighting and improves user experience.
Furthermore, Ross argues that pilot groups help collect meaningful feedback and uncover integration issues in real operations rather than in isolated labs. This feedback loop can influence product fixes and feature design while giving organizations a head start on governance and security controls. Consequently, early adopters often move from reactive to planned deployments.
Ross candidly highlights tradeoffs: early access brings new capabilities but also introduces instability and unpredictability. Preview features may behave differently than final releases, and administrators must balance the desire for early insight with the potential for user confusion or workflow disruption. Thus, organizations need clear communication plans and rollback strategies when enabling Frontier broadly.
Security and compliance are additional challenges because Frontier exposes experimental agents that may interact with data in new ways. Ross recommends assessing the tenant’s security baseline before enabling previews and suggests limiting exposure to a controlled pilot group. Finally, the timing of feature appearance and updates can be uneven, which complicates scheduling and testing priorities for IT teams and MSPs alike.
Ross recommends that organizations create a dedicated pilot group to validate features, document observed behaviors, and develop user guidance prior to broader rollout. He also suggests approving Microsoft agents deliberately and keeping a tight scope at first to limit unintended impacts. Monitoring and logging should be in place so administrators can track usage and detect anomalies quickly.
In addition, Ross encourages teams to use preview periods to design training and support materials, and to simulate common workflows that will rely on new Copilot capabilities. By doing so, IT teams can identify compatibility issues early and prepare mitigation steps. Ultimately, his advice centers on disciplined testing, careful governance, and clear user communication to get maximum value from Frontier while minimizing risk.
Copilot Frontier Program early access, Get Copilot features early, Microsoft Copilot preview access, Copilot beta sign up, Copilot insider program, Join Copilot Frontier, Copilot features walkthrough, Copilot early adopter benefits