Copilot Studio new experience disappeared from environment; new-experience agents are inaccessible.

Question

Copilot Studio new experience disappeared from environment; new-experience agents are inaccessible.

SamJakub 5

Edit: This is a known issue from Microsoft. Due to some issue with FedRAMP customers
https://admin.preview.powerplatform.microsoft.com/support/knownissues/6628785

One of our environments had the new Copilot Studio Agent and Workflow experiences last week. It now loads the classic experience and the New experience / Try it now option is absent. New-experience-only agents and workflows are inaccessible to their owners. The Default environment in the same tenant still has the new experience. Please advise on how to get the new experience and agents back.

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-08-19T07:20:48.73+00:00

Thank you for reporting this issue.

The new Copilot Studio experience uses the GitHub Copilot harness and is currently provided alongside the standard experience. Microsoft documentation indicates that makers should be able to switch between these experiences using the New experience toggle.

Differences between environments can occur during staged rollout. However, the affected environment previously had the new experience and now no longer displays the toggle, while the Default environment in the same tenant continues to display it. Agents and workflows created with the GitHub Copilot harness are also no longer accessible.

Loss of previously available authoring access is not documented as expected behavior. We are therefore treating this as a potential environment-level service or feature-flag regression rather than closing it as by design.

We will verify environment eligibility, licensing, Copilot Credit configuration, permissions, environment-group governance and service health. If these checks show no relevant configuration change, we will escalate the case for Copilot Studio engineering investigation.

Your answer

Ashlesha Pawar (Tata Consultancy Services Limited) 395 Reputation points Microsoft External Staff

2026-08-19T07:20:48.73+00:00

Thank you for reporting this issue.

The new Copilot Studio experience uses the GitHub Copilot harness and is currently provided alongside the standard experience. Microsoft documentation indicates that makers should be able to switch between these experiences using the New experience toggle.

Differences between environments can occur during staged rollout. However, the affected environment previously had the new experience and now no longer displays the toggle, while the Default environment in the same tenant continues to display it. Agents and workflows created with the GitHub Copilot harness are also no longer accessible.

Loss of previously available authoring access is not documented as expected behavior. We are therefore treating this as a potential environment-level service or feature-flag regression rather than closing it as by design.

We will verify environment eligibility, licensing, Copilot Credit configuration, permissions, environment-group governance and service health. If these checks show no relevant configuration change, we will escalate the case for Copilot Studio engineering investigation.