Copilot Studio

Outlook Trigger Not Firing in Copilot Studio – PAYG Enabled but Flow Not Triggered

(0) Share

Report

Posted on by GH-10041152-0

Hello community,

I have a question and hope someone here might have experienced this or can point me in the right direction.

Problem Summary

An Outlook (Microsoft 365) trigger is not firing when the flow is used in Copilot Studio.

The flow is a standard cloud flow using the Microsoft 365 Outlook connector (no custom trigger).

A Copilot Studio subscription is active.

Azure Pay‑as‑you‑go (PAYG) has been fully configured:
- Valid Azure subscription
- Payment method added
- Billing policy saved
- Budget configured

Despite this, Flow validation still reports:
- “Insufficient Copilot credits in this environment” (warning)
- “There is a problem with the trigger of this flow” (error)

The trigger was previously working and shows a last successful run, but new emails no longer trigger the flow.

Expected Behavior

The Outlook Microsoft 365 trigger should behave as a normal standard Power Automate trigger, independent of Copilot credits or PAYG configuration.

Actual Behavior

When the flow is associated with Copilot Studio, the Outlook trigger does not fire, even though PAYG is enabled and billing is correctly set up.

Categories:

Calling actions from Copilot Studio

Copilot Studio skills development

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

frago 226 on at

Like (1)

Report
Copy link

Link copied!
Hi @GH-10041152-0

When you connect the flow to Microsoft Copilot Studio, it’s no longer treated like a normal Power Automate flow.

Because of that:

The Microsoft 365 Outlook trigger can stop firing

The “insufficient credits” warning can actually block the flow (it’s not just a warning)

Why it worked before: it was a standard flow

Why it fails now: Copilot adds its own rules (credits + environment)

What to do:

Test the flow without Copilot → it should work

If yes, keep Outlook-triggered flows separate from Copilot

Or rebuild the flow inside Copilot instead of reusing the old one

👉 In short: Copilot changes how the flow runs, and Outlook triggers may stop working because of that.

------------------------------------------------------------

If this solved your issue, please mark it as ✅ Accepted Answer.
If it helped, feel free to give it a 🩷 Like!

Best regards,
Piotr

Was this reply helpful? Yes No
GH-10041152-0 5 on at

Like (1)

Report
Copy link

Link copied!

Hi @frago, thanks for the clarification 👍

In Power Automate it works perfectly.
After a quick refresh/update, the flow runs again without any issues.

Appreciate your support!

Was this reply helpful? Yes No