How to Send Outlook Automatic Replies using Power Automate?

5.5K

Businesses and individuals use automatic replies in Outlook to let senders know how their messages were received or give them further details. The common practice is to use Shared Mailboxes for these automatic replies by enabling the Out of Office.

But the Out of Office (OOF) agent only sends automatic replies once to every sender. If the mailbox receives another message from the same sender, it will not automatically reply to the sender anymore. And that feature limitation is by design.

Why Outlook Out of Office Replies Only Once

Keep in mind that Exchange Online and Outlook Out of Office (OOF) replies are intentionally designed to send only one automatic reply per sender during a configured OOF period. This behavior exists to prevent:

• auto-reply loops
• email storms
• mailbox spam
• excessive outbound email traffic

For example, in case the same sender sends 10 emails during your Out of Office period, Exchange Online normally sends only one automatic reply. This limitation is built directly into Exchange Online and cannot be changed using standard OOF settings.

Power Automate works differently because it processes every incoming email individually through workflow automation logic.

As a result, Power Automate can send automatic replies for every received message instead of only once per sender.

So what’s the workaround? That’s where Power Automate comes in handy. Power Automate is a cloud-based service that allows you to automate workflows between different apps and services, including Outlook. In this blog post, we’ll create a Power Automate Outlook flow that sends automatic replies to each message it receives.

Requirements

• Administrator access to the Microsoft 365 tenant.
• An Exchange Online mailbox. This post will use a shared mailbox.
• Power Automate license (licensing requirements may vary depending on tenant config and Microsoft licensing changes).
• The shared mailbox is used only as a target mailbox (not as an authentication identity).

Use Delegated Access for Shared Mailbox

A shared mailbox should not be used as the authentication identity for this Power Automate flow. Instead, you should use a licensed user account with delegated access to the shared mailbox. The shared mailbox itself does not need a separate Power Automate license for this case. Follow these steps to set up the mailbox:

1. First, you need to create/confirm shared mailbox. Log in to the Exchange Admin Center. Here you need to ensure shared mailbox exists (no sign-in required).
2. Next, assign delegated permissions to a real user instead of enabling sign-in. Grant a real user access Full Access, Send As.
   

   Here is a PowerShell example:

   Add-MailboxPermission -Identity "Customer Service" -User user@domain.com -AccessRights FullAccess
   Add-RecipientPermission -Identity "Customer Service" -Trustee user@domain.com -AccessRights SendAs

3. You should use user account in Power Automate. Instead of logging into shared mailbox, you should use licensed user account. Create Flow under that user and in the trigger, specify the shared mailbox address in the Original Mailbox/Mailbox field (depending on connector config). The flow still runs under the licensed user identity.

Note that shared mailboxes in Microsoft 365 are not intended for interactive sign-in. Power Automate flows should run under a licensed user identity with delegated access to the mailbox.

Security note. Keep in mind that enabling sign-in on a shared mailbox increases the attack surface. You should consider enabling MFA where possible.

Security justification (best practice)

• No shared mailbox passwords
• No interactive login
• Works with Conditional Access policies
• No attack surface expansion
• Aligns with Microsoft recommended architecture

Does a Shared Mailbox Require a Power Automate License?

Note that by default, shared mailboxes in Microsoft 365 do not require separate licenses for basic Exchange functionality. However, Power Automate flows run under a user identity.

• Shared mailboxes in Microsoft 365:
  – do not require sign-in
  – do not use passwords
  – are not used as authentication identities in Power Automate
• Power Automate flows run under a licensed user account
• Shared mailbox is accessed through delegated permissions (Full Access/Send As)

This ensures compatibility with Conditional Access policies and aligns with Microsoft recommended security architecture for Exchange Online and Power Automate.

Keep in mind that in case you don’t have a Power Automate license, the flow may fail to authenticate/execute correctly.

In small environments, the Power Automate Free license is often sufficient for simple Outlook automation flows. Enterprise cases may require premium licensing depending on:

• connectors used
• flow frequency
• API usage
• tenant policies

Create the Power Automate Flow

Now that the Power Automate shared mailbox is ready, let’s create the Power Automate Flow needed to monitor the mailbox for new messages and send automatic replies.

1. Open a new browser window and navigate to Power Automate Sign In page.
2. Sign in using a licensed user account that has delegated access to the shared mailbox.
   

   

3. Once logged in, click Create on the left side. There are many blank flows and templates. But in this example, click the Automated Cloud flow, which is correct for this use case.
   

   

Create the Flow Trigger

1. On the Build an automated cloud flow pop-up, enter the Flow name. In this example, the flow name is Customer Service Auto Reply.
2. Under “Choose your flow’s trigger,” select “When a new email arrives (V3)”, and click Create. The flow runs under the licensed user identity, while monitoring a shared mailbox through delegated access.
   

   

3. In the “To” box, enter the shared mailbox email address. The flow will be triggered only when the “To” recipient in the new message matches this email address.
   Click New step.
   

   

Add the Flow Action

1. Search for “reply to email” and select “Reply to email (V3)” under Actions.
   

   

2. Click the “Message Id” box and select “Message Id” from the list.
   

   

3. Type the automatic reply message in the “Body” box.
4. In the “Original Mailbox Address,” enter the shared mailbox email address. This address will be the sender of the automatic reply message. Click Save.
   

   

Add a Condition to Prevent Auto-Reply Loops

Before sending automatic replies, we recommend you to add a Condition step in order to avoid mail loops and replies to automated systems.

Click New step and select Condition.

You can create conditions such as:

• Ignore messages where the Auto-Submitted header equals auto-replied
• Ignore sender addresses containing noreply, no-reply, donotreply

This will help you to prevent situations where 2 automated systems continuously reply to each other.

For example, you can config the flow logic as described below:

When a new email arrives
↓
Condition:
Sender does not contain noreply/no-reply
AND
Auto-Submitted header is not auto-replied
↓
Reply to email (V3)

Note that this is especially important in enterprise environments that are using ticketing systems, monitoring platforms, and automated notification services.

How the Power Automate Auto-Reply Flow Works

The workflow logic is very simple:

• Power Automate monitors the shared mailbox
• A trigger activates when a new email arrives
• The workflow extracts the Message ID
• Power Automate generates a reply to that specific email
• The sender receives the automatic response

Keep in mind that unlike Outlook Out of Office replies, the workflow processes every email independently. This allows repeated replies to the same sender whenever a new message arrives.

Preventing Auto-Reply Loops and Spam

Note that during configuration of the automatic reply workflows in Power Automate, you should avoid creating reply loops/generating excessive automatic responses. We recommend adding conditions to ignore:

• automatic replies
• mailing lists
• system-generated messages
• spam/junk messages
• internal monitoring alerts

Keep in mind that without proper filtering, 2 automated systems may continuously reply to each other and generate email loops.

You can reduce this risk by checking message headers/using conditions such as:

• Ignore emails where Auto-Submitted header exists
• Ignore messages marked as bulk mail
• Ignore messages from specific domains/senders

Note that this is especially important in enterprise environments with ticketing systems, monitoring platforms, and automated notification services.

Limiting Automatic Replies to Internal or External Senders

Power Automate allows you to control who receives automatic replies. For example, you can config the flow to:

• reply only to internal users
• reply only to external senders
• exclude specific domains
• ignore vendor notifications
• skip noreply mailboxes

You can do this by using Conditions in the workflow based on:

• sender domain
• email headers
• recipient type
• message subject

This will help you to reduce unnecessary automated replies and improves security.

Test the New Flow

The flow is ready, but it is recommended to test whether it works. This way, you can confirm whether the flow is as expected or if you’ve missed a step.

1. Click the Test button.
   

   

2. On the Test Flow fly-out, choose Manually and click Test.
   

   

   
   You’ll see a banner like the one below. This means the flow is waiting for a new message to arrive in the mailbox.
   

   

3. Send a message to the shared mailbox using your (or another) mailbox.
   

   

4. Wait a few moments, and you should receive the automatic reply from the Power Automate Outlook flow.
   

   

5. Go back to the Power Automate Flow, and you will see the confirmation banner saying, “Your flow ran successfully.”
   

   

Power Automate and Exchange Online Limitations

Keep in mind that Microsoft 365 and Power Automate apply various service limits and throttling protections. Note that large mail volumes may affect:

• flow execution speed
• API requests
• automatic reply delivery
• connector throttling

In case you have very high-volume shared mailboxes, you may require:

• premium licensing
• dedicated service accounts
• more advanced automation architectures

For enterprise-scale customer service systems, we recommend you to evaluate dedicated ticketing/CRM platforms instead of simple auto-reply workflows.

Best Practices for Outlook Auto Reply Flows

We recommend you to follow these best practices:

1. You should use shared mailboxes instead of personal accounts
2. You need to avoid replying to spam/junk messages
3. You should exclude automated senders
4. Use clear support contact info
5. You need to monitor flow execution history regularly
6. You should secure mailbox credentials properly
7. You need to avoid hardcoded credentials
8. You need to follow document automation logic

Note that in enterprise environments, you should always test flows in non-production mailboxes before deployment.

Conclusion

When setting up automatic replies in Outlook, Microsoft Power Automate can provide significant advantages over the traditional Out of Office (OOF) agent.

Step	Action
1	Use shared mailbox with delegated access (no sign-in)
2	Assign appropriate Power Automate license to the user account (Free/Premium depending on your environment)
3	Create Automated Cloud Flow with “When a new email arrives (V3)” trigger
4	Add “Reply to email (V3)” action
5	Add conditions to prevent reply loops
6	Test manually before deployment