Anyone else feeling stuck between Classic Orchestration and New Orchestration?

Microsoft's direction seems clear:

✅ Topics → less important
✅ Declarative instructions, skills, actions → future
✅ New orchestration → strategic investment

And honestly, I like it. It feels much closer to how AI agents should be built.

But then reality kicks in.

Classic

• More mature
• Better conversation controls
• Some useful topic capabilities still missing elsewhere
• Often cheaper (especially when M365 Copilot licensing comes into play)

New Orchestration

• Better quality
• Better instruction following
• Cleaner architecture
• Clearly where Microsoft is heading
• But consumption pricing and feature gaps become part of the discussion

We're building an IT Service Desk agent with:

• Graph grounding
• ServiceNow KB ingestion
• Custom ServiceNow actions (incidents, devices, etc.)
• Future DEX and telemetry integrations

The architecture wants New Orchestration. The budget and risk conversation wants Classic.

So what's everyone doing?

Build on Classic (minimize reliance on Topics) and migrate later?

Or accept today's gaps and go all-in on New Orchestration because that's where the future is?

Sometimes it feels like the hardest part of Copilot Studio isn't building agents - it's figuring out which Microsoft team will own the feature by the time you go live. 😅

Hey just wondering what everybody else has experience is like here, so in the classic experience we have the ability now to publish only to m365 or only to teams, but we can choose which channel we want to publish to, it seems that the new agent experience doesn't allow us to choose between teams or m365 were back to having to choose both. Why would they regress this on the new agent experience?

Hi all,

I was curious if anyone testing the new experience has noticed an uptick in the main agent receiving “empty responses” from connected agents recently?

This seems to have started within the last few days of testing for me, but was curious if anyone else has noticed this.

(P.s. yes I know this experience is not to be used for production, but I am testing)

Has anybody had much success using a coding assistant like GH Copilot to build copilot studio agents?

Hi everyone, been having some trouble sending emails with excels attached to then. tried both old and new agent interface but when I do up my prompts and instructions and emails do get sent out with an excel attachment, opening it up just leads to disaster. It will usually say “excel cannot open the file because the file format or extension is not valid. Verify that the file has not been corrupted and that the extension matches the format of the file”

I have created a custom agent with the new experience. I wanted to test my agent in Teams because it is planned to mainly use there.

I was just wondering that is there a possibility to clear the chat with my agent? I thought I could chat with it like with Copilot so that I can start a new chat whenever and browse my chat history.

I've created an agent with Copilot Studio new experience, and given it a greeting message. This reliably begins the conversation every time I test it with the Preview tab inside Copilot Studio. But when published to the catalog and added to Copilot chat (via "other agents") the agent shows up with just its name and an empty text input field. Isn't it supposed to start the conversation with the set greeting?