u/PowerPlatformRookie

Has anyone managed to get the Sales Qualification Agent fully working in a Dynamics 365 Sales trial environment?

In my case, the agent is handling leads and appears in the environment, but it keeps failing during execution. What’s confusing is that during setup I was never asked to link a Copilot credits license or configure billing.

I also tried enabling PAYG billing, but my trial environment does not appear in the PAYG setup list for some reason, so I can’t even connect it.

Another issue: the Sales Research Agent constantly returns “Something went wrong, please try again later.”

So now I’m wondering:

• Do Sales Qualification / Research Agents actually work in trial environments?
• Are Copilot credits mandatory even for trials?
• Is the missing PAYG environment a known limitation or bug?
• Has anyone found a workaround for this?

Would appreciate any insights from people who tested these agents recently.

Has anyone faced an issue where the Sales Opportunity Agent does not appear in the environment, even though other (Sales Close/Sales Qualification) Copilot agents and features are showing correctly?

I’m following the official Microsoft documentation:
https://learn.microsoft.com/en-us/dynamics365/sales/open-sales-close-agent-research-settings

The environment is properly configured and other agents are visible and working, but this specific agent/settings page is missing entirely.

Things I already checked:

• Copilot enabled
• Security roles/admin access verified

Still no Sales Close Agent / Research settings appearing.

Has anyone encountered this and does know how can i enable this specifc agent ?

I’m attaching a screenshot for reference.

Any help or insights would be appreciated.

https://preview.redd.it/lfjafsmqs32h1.png?width=1645&format=png&auto=webp&s=5d40d6cd3e2d0eabcdda69e431e07aca36cd2885

I’m currently testing different approaches in Microsoft Copilot Studio / Power Automate for an email-processing use case (email received → AI extraction → Dataverse record creation).

One thing I noticed is that an Agent Flow seems to consume Copilot Credits even when the logic itself is relatively simple. In my case, the flow includes:

• AI Builder actions (OCR + prompt)
• Copilot agent actions
• Dataverse actions

From what I understand, AI Builder and agent runtime both consume billable Copilot Credits.

My question is:
If I rebuild the exact same process using a standard Power Automate cloud flow instead of an Agent Flow while still keeping the same AI Builder actions would the Copilot Credit consumption be lower?

In other words:

• Does Agent Flow itself add additional Copilot runtime costs?
• Or would the billing remain almost identical because the expensive part is mainly the AI Builder / LLM actions?
• Is it considered best practice today to keep orchestration in standard Power Automate and only use AI Builder / Copilot actions where strictly needed, to minimize Copilot Credit consumption?

For context, my tests showed that calling a Copilot agent from an Agent Flow seems to add extra runtime consumption on top of the AI actions already executed.

Curious to know how others are architecting these solutions in production and how you optimize Copilot Credit costs.

We noticed something inconsistent with Copilot Studio Agent Flow billing behavior and wanted to see if others experienced the same.

We tested 2 very similar Agent Flow scenarios:

• Both were Copilot Studio Agent Flows (not Power Automate cloud flows)
• Both used the exact same trigger: “When a new email arrives”
• Both were executed through real incoming emails (not from the Test Pane)
• Both accounts had active M365 licenses

However, the credit consumption behavior was different:

• In one case (M365 license in an DEV environment), executions consumed non-billable Copilot credits
• In the other case (M365 license in a Sandbox environment), executions consumed billable Copilot credits

The flows themselves were almost identical, so the only major difference seems to be the environment type.

Has anyone else noticed that Sandbox environments label Agent Flow credits as billable even when a Copilot license is assigned?

Trying to understand if this is expected behavior, an environment limitation, or potentially unstable/inconsistent billing logic.