If the “New experience” toggle on your Copilot Studio home page has started disappearing and reappearing without any obvious trigger, you are not imagining it. Reports from makers and admins describe the same pattern: the toggle is there on one visit, gone on the next, and back again later with no action taken in between.
This is worth understanding now rather than dismissing as a one-off glitch, because it touches how makers in your tenant access two genuinely different Copilot Studio experiences: the standard harness and the newer GitHub Copilot harness. If your organization is mid-rollout on the new experience, an intermittently missing toggle can quietly steer makers back onto the older interface without anyone deciding that should happen.
What is actually going missing
Copilot Studio’s home page normally shows a toggle or banner inviting makers to try the new experience, which switches the interface from the classic topic-based builder to the newer agent-and-skills model built on the GitHub Copilot harness. The issue reported is that this control does not consistently render. Sometimes it is visible on load, sometimes it is missing entirely, and it can come back later with no clear cause: no cache clear, no re-authentication, no new browser session that reliably explains the change.
That intermittency is the detail that matters for admins. A control that fails consistently is easy to diagnose and route around. A control that fails at random usually points to a server-side rollout, feature-flag, or caching condition rather than anything wrong with an individual user’s browser or account.
What does and does not fix it
The standard first-line troubleshooting steps largely fail here. Closing and reopening the browser, signing out and back in, and starting a fresh browser session have all been reported as ineffective on their own. Two workarounds have surfaced instead, and both come with caveats worth knowing before you point a maker at them.
- Navigate directly to the environment URL. Going straight to the environment-scoped home page, in the form copilotstudio.microsoft.com/environments/[EnvironmentID]/home, has restored the toggle for some users. This is not universal. Other users following the same steps have landed on the classic Copilot Studio interface instead of the new GitHub Copilot harness experience, which does not solve the actual problem if the goal is to reach the new build tools.
- Check the Agents area instead of Home. When the “Try the new experience” prompt is missing from the home page, it has still appeared under the Agents section in the left-hand navigation for some users. If a maker reports the toggle has vanished, having them check Agents before escalating is a low-cost first step.
Neither workaround is a guaranteed fix, and that is consistent with a server-side cause rather than a client-side one.
A likely rollout-list explanation, and why it needs admin confirmation
Community responses point to an open item in the Power Platform admin center’s known issues list, logged in mid-August 2026, describing tenants or users being excluded from seeing the new experience prompt as part of the staged rollout. The workaround described alongside that item is unusually procedural: a tenant admin has to submit a written request through Microsoft’s standard support channel to have the exclusion reviewed and, where appropriate, removed.
Treat that specific detail as a lead rather than a confirmed fact until you have checked it directly. Known issues entries in the admin center are updated or closed as rollouts progress, and a support-forum summary of one is not a substitute for reading the live entry. If you manage a Power Platform tenant, the practical move is to have your admin search the known issues list in the Power Platform admin center for “New experience” or “Copilot Studio home page” and read the current status and workaround language yourself before communicating anything to your maker community.
Why this matters beyond a missing button
Preview and staged-rollout features change access paths in ways that are easy to overlook from a governance standpoint. Copilot Studio’s new experience is not a cosmetic reskin. It removes the topic-based conversation model in favor of skills and agent flows, and it changes how connector permissions and end-user authentication are evaluated at publish time. A maker who is silently bounced between the classic and new interfaces because of a rendering issue may build or troubleshoot an agent under a different permission and tooling model than they think they are using, and support conversations can go sideways quickly if nobody realizes which experience produced the behavior being described.
Until the toggle stabilizes, it is worth doing three things inside your tenant.
- Ask makers to note, when reporting an issue, whether they were in the classic or new Copilot Studio experience at the time. It is not always obvious from a screenshot alone.
- Have your admin check the Power Platform admin center known issues list directly rather than relying on secondhand summaries, since status and workaround guidance can change as Microsoft progresses the rollout.
- Share the Agents-page workaround with makers as a first response, since it is the lower-risk of the two reported options and does not risk dropping someone into the wrong interface.
This is a preview-stage rollout issue, and Microsoft’s own documentation frames the new experience as an evolving option alongside the standard harness rather than a finished replacement for it. Expect the toggle behavior to change again before it settles, and treat any workaround here as temporary rather than a permanent fix.
Verification flag: the admin center known issue referenced above should be confirmed directly in your tenant’s Power Platform admin center before being cited to end users, since its status and workaround text are subject to change as the rollout continues.