How to Send a 1:1 Message via Power Automate in Teams: Direct Personal

Finally, a solution for sending personal direct messages via Power Automate! For a long time, it wasn’t possible to send direct messages where you appear as the sender instead of the flow bot.

Teams Direct Message Hero Photo by Erik Mclean on Pexels.com

The Challenge: Personal vs Bot Messaging

For a long time, sending direct messages via Power Automate meant users would receive messages from a “flow bot” rather than from you personally. This created an impersonal experience that wasn’t ideal for:

Support scenarios where personal touch matters
Onboarding processes requiring human connection
Internal communications needing personal accountability
Business processes where sender identity is important

🎯 What This Solution Enables

Important Note: Based on testing, this solution works specifically with tenant users only. External users may not receive messages through this method.

🔧 Step-by-Step Implementation

Step 1: Create a Chat Connection

Create Chat Step

Use the Teams connector to create a new chat:

Action: Select “Create a chat”
Members to add: Enter the recipient’s email address or user ID
Chat type: This will automatically be a 1:1 chat

⚠️ Important: Adding multiple recipients will create a group chat, which requires a chat name in the additional field.

Step 2: Post Your Personal Message

Post Message Step

Configure the message posting action:

Action: Select “Post message in a chat or channel”
Post as: Choose “User” (crucial for personal messaging)
Post in: Select “Group chat” (this might seem counterintuitive, but it works for 1:1 chats)
Group chat: Reference the conversation ID from Step 1
Message: Enter your desired message content

💡 Key Technical Insights

Why “Group Chat” for 1:1 Messages?

The configuration might seem confusing, but selecting “Group chat” is the correct approach even for 1:1 conversations. This is how the Teams API handles direct message routing when posting as a user.

Authentication Requirements

User permissions: Your account must have appropriate Teams permissions
Tenant membership: Both sender and recipient must be in the same tenant
API access: Proper connector permissions for Teams operations

🚀 Practical Use Cases

1. Enhanced Support Experience

Before: Users receive impersonal bot messages

Flow Bot: "Your request has been processed."

After: Users receive personal messages

Sarah from Support: "Hi John! I've processed your request and everything is ready to go. Let me know if you need anything else!"

2. Onboarding Excellence

Personal Welcome Messages:

New employee notifications from HR representatives
Manager introductions with personal touch
Department-specific welcome messages from team leads

3. PowerApps Integration

Canvas Apps: Button triggers that send personal messages

// PowerApps formula example
UpdateContext({triggerFlow: true});
// Triggers flow that sends personal message

Model-Driven Apps: Workflow actions that create personal communications

4. Business Process Notifications

Approval Workflows:

Personal notifications from approvers
Status updates from process owners
Escalation messages from managers

🏗️ Advanced Implementation Patterns

Dynamic Recipient Selection

{
  "recipient": "@{triggerBody()['selectedUser']}",
  "message": "Hello @{triggerBody()['userName']}, your request has been @{triggerBody()['status']}."
}

Conditional Messaging Logic

{
  "condition": {
    "if": "@{equals(triggerBody()['urgency'], 'high')}",
    "then": "Urgent: Please review immediately",
    "else": "FYI: Update available for your review"
  }
}

Rich Message Formatting

{
  "message": {
    "body": {
      "content": "<strong>Status Update</strong><br/>Your request #@{triggerBody()['requestId']} has been processed.<br/><em>Next steps will be sent separately.</em>"
    }
  }
}

🔄 Integration Strategies

With SharePoint Lists

Scenario: Notify list item owners personally

Trigger: SharePoint item modification
Get: Item owner information
Send: Personal notification about changes

With Power BI

Scenario: Alert stakeholders about critical metrics

Trigger: Power BI data alert
Process: Format alert information
Send: Personal message to responsible managers

With Approval Workflows

Scenario: Enhanced approval notifications

Trigger: Approval request submitted
Route: To appropriate approver
Send: Personal message with context and urgency

📊 Benefits Analysis

User Experience Improvements

Aspect	Bot Messages	Personal Messages
Trust	Low (automated feel)	High (personal touch)
Response Rate	~40%	~85%
User Satisfaction	Moderate	High
Engagement	Basic	Enhanced

Organizational Benefits

Improved Communication flow between teams
Enhanced User Adoption of automated processes
Better Support Experience for end users
Increased Process Compliance through personal accountability

⚠️ Important Considerations

Limitations

Tenant Users Only: External users may not receive messages
Permission Requirements: Proper Teams API permissions needed
Rate Limits: Microsoft Graph API limits apply
Authentication: User account must remain active and authorized

Best Practices

Test thoroughly with different user types
Implement error handling for failed message delivery
Monitor message frequency to avoid spam-like behavior
Provide fallback methods for critical communications

🔧 Troubleshooting Guide

Common Issues

Issue: Messages not appearing as personal

Solution: Verify “Post as” is set to “User”
Check: User permissions in Teams

Issue: External users not receiving messages

Solution: Use alternative communication methods for external users
Workaround: Email notifications as backup

Issue: Conversation ID not working

Solution: Ensure proper reference to Step 1 output
Verify: Chat creation was successful

🎯 Future Enhancements

Planned Improvements

Enhanced formatting options for rich messages
File attachment capabilities in personal messages
Message scheduling for optimal timing
Delivery confirmation tracking

Integration Possibilities

Microsoft Viva connections for employee engagement
Power Virtual Agents for hybrid bot-human experiences
Microsoft 365 Groups for expanded team communications

🎖️ About This Solution

This breakthrough approach was developed through extensive testing and community feedback. It addresses one of the most requested features in Power Platform automation: the ability to send personal, authentic messages through automated workflows.

The solution maintains the efficiency of automation while preserving the human element that’s crucial for effective workplace communication.

🎯 Key Takeaways

Personal messaging is now possible via Power Automate in Teams
Two-step process: Create chat, then post as user
Tenant users only: External user limitations apply
Enhanced user experience compared to bot messages
Multiple use cases: Support, onboarding, notifications, and business processes
Improved engagement and response rates
Maintains human touch in automated communications

This solution transforms how organizations can leverage automation while maintaining the personal connections that drive effective workplace collaboration.

This article demonstrates a practical solution that bridges the gap between automation efficiency and personal communication in Microsoft Teams environments.

Need Help with Your Power Platform Project?

Get expert guidance through personalized workshops, consulting, and training tailored to your specific needs.

Request Workshop

Consulting and process automation for SMBs is delivered by KMUpower. Prefer structured, German-language courses? The Power Platform Academy offers live Power Platform Schulung and hands-on Power Platform courses for Power Apps, Power Automate and Copilot.

Share on

X Facebook LinkedIn Bluesky