Hi,
Yeah, this confusion is pretty common when you start mixing agents with flows across Power Automate, Microsoft Teams, and Microsoft Copilot Studio.
What’s happening is that both approaches use Power Automate, but they operate under different capabilities.
If you’re using Power Automate directly, then yes, you can post messages to:
- Channel
- Group chat
- Individual chat
For example:
This works fine for group chats as long as:
- You specify the chat ID or participants
- The flow has permission to post
But when you bring Copilot Studio (Agents/Bots) into the picture, things change a bit.
Copilot Studio supports proactive messaging, but:
- It is mainly designed for 1:1 conversations (personal chat)
- It does not natively support sending proactive messages to group chats
So even though Copilot Studio uses Power Automate behind the scenes, it still follows bot framework limitations.
That’s why you’re seeing:
- Power Automate docs → group chat supported
- Copilot Studio docs → only personal chat supported
Both are correct, just in different contexts.
If your requirement is:
- Send notification to a group chat → use Power Automate directly
- Send message from an Agent → limited to personal chat
If you really want to combine both:
- Use Copilot Studio for interaction
- Trigger a Power Automate flow
- Let the flow post to Teams group chat
But the message will be posted by the flow/connection, not truly “as the agent in the group chat”.
So basically, agents can talk like a person in 1:1 chats, but for group chat notifications, Power Automate is still the reliable way.
Best regards,
Satyam Pandey
✅ If this helped solve your issue, please mark it as Accepted Solution so others can find it quickly.
❤️ If it was helpful, please click Yes on “Was this reply helpful?” or give it a Like.
🏷️ For follow-ups, feel free to tag @TechFreak
💼 LinkedIn
▶️ YouTube