Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Hello jogender yadav,
Please find the details below.
Q1 — M365 Copilot coverage for Power Automate–triggered runs: The M365 Copilot license only applies to interactive use within M365 Copilot platforms such as Teams, Copilot Chat, Word, and Outlook. Since your agent is triggered through Power Automate's Execute Agent action, each run is considered autonomous and will use Copilot Credits from your 25k tenant pack.
Q2 — Reason for the "premium license required" warning: The HTTP action is considered a premium feature, which is why the warning appears for makers. While your tenant credit pack covers runtime, the warning is based on the maker's license. To resolve this, assign yourself the Copilot Studio User license (at no cost); this enables you to author premium features, but does not affect runtime billing.
Q3 — HTTP / Graph as a premium connector and credit consumption: The HTTP action is a premium capability and will consume credits on every run, regardless of your M365 Copilot license, because:
- The trigger is autonomous (via Power Automate), so it’s always metered.
- Premium features are metered even outside autonomous scenarios.
The Copilot Studio User license is only for authoring premium features, not for runtime usage.
Recommendation:
- Continue using your credit pack for billing.
- Assign the Copilot Studio User license to yourself to remove the maker warning.
- Monitor usage in Power Platform Admin Center → Copilot Studio → Capacity.
If you expect to exceed the 25k credit limit, consider switching to Pay-as-you-go.
If you found the information above helpful, I would appreciate it if you could share your feedback.
Your feedback is important to us. Please rate us: 🤩 Excellent 🙂 Good 😐 Average 🙁 Needs Improvement 😠 Poor