Schedule an Outlook Email to Send Every Week

Outlook’s built-in Schedule Send feature sends a message once; it does not repeat it every week. To send a recurring weekly email, create a scheduled cloud flow in Microsoft Power Automate, set its Recurrence trigger to run weekly, and add the Office 365 Outlook action Send an email (V2).

Outlook’s scheduled send is a one-time feature

Outlook can hold a message until a later date and time, which is useful for sending a reminder or choosing a better delivery time. That is different from a recurring schedule: after the message is sent, Outlook does not automatically send it again the following week. Scheduling a new copy each time is possible, but it requires repeating the process manually.

In new Outlook for Windows and Outlook on the web, compose the message and use the arrow beside Send to choose Schedule send, then select a suggested time or a custom time. In classic Outlook for Windows, compose the message and open Options > Delay Delivery. Select Do not deliver before, choose a date and time, close the properties window, and click Send. The message remains pending until the selected time. These controls schedule a single message, not a repeating series.

Outlook for Mac also offers scheduled sending in supported versions, though the control’s position and availability can differ. If you only need one delayed message, use the scheduling feature in the Outlook version you have. If you need the same message every Monday, or on another weekly schedule, use an automation flow instead.

Set up a weekly flow in Power Automate

A scheduled cloud flow runs on Microsoft’s service rather than relying on a recurring message saved in the Outlook application. To create one, sign in to Power Automate with the account you want to use, then follow these steps. Labels and the arrangement of controls can change slightly as Microsoft updates the interface.

Choose Create, then Scheduled cloud flow. Give the flow a clear name, such as Weekly team update.
Set the start date and time, and configure the repeat interval. Choose Week as the frequency and 1 as the interval for a weekly run. If the trigger offers particular days of the week, select the day you want.
Choose the time zone and save or create the flow. Confirm that the displayed next run is the intended local day and time.
Add a new step and search for Office 365 Outlook. Select Send an email (V2), then sign in or select the connection for the mailbox that should send the message.
Fill in the To, Subject, and Body fields. Add Cc or Bcc only if needed. Save the flow, make sure it is turned on, and use a test run or wait for its first scheduled run to check the result.

For example, a team lead could configure a flow for every Friday at 3:00 p.m., address it to the team, and use a subject such as Friday project summary. The flow will send the configured content on each run. It does not need Outlook to be open on a computer, but it does depend on the flow and its connected account remaining in good standing.

Choose the right day, time, and time zone

Set the schedule based on the recipient’s working day, not just the time that is convenient for the sender. A weekly report sent at the start of Monday may be more useful than one delivered late Friday. If recipients are spread across regions, consider whether a single delivery time is reasonable for everyone or whether separate flows are justified.

Pay particular attention to the time-zone setting. A flow configured with the wrong zone can run at an unexpected local hour. Daylight-saving changes can also affect the relationship between a chosen local time and UTC. Review the flow’s next-run information after saving, and check it again when changing the schedule or time-zone setting. Do not assume that a time written in the email body automatically controls the trigger; the trigger schedule is configured separately.

A weekly recurrence usually means a calendar-based weekly interval, not a fixed number of hours between sends. If the flow needs to run on a specific weekday, check that the selected weekday is part of the trigger configuration. After editing the recurrence, save the flow and verify its next run rather than relying on memory of the old setting.

Make the recurring message useful

A fixed subject and body are appropriate for a stable reminder, such as a weekly office-hours notice. For a report that changes, a static message may become misleading. For example, a body that says This week’s deadline is Friday will be wrong if the deadline changes and nobody updates the flow.

Power Automate actions can use dynamic content from earlier steps, and a flow can include additional actions to retrieve or prepare information before sending. That can support messages that contain current data, but it adds setup and maintenance. For a simple announcement, keep the flow short; for a status report, check the source data and date logic before relying on automatic delivery.

Use a subject that makes the recurring purpose clear, such as Weekly service reminder.
Keep recipient lists current, especially when people change roles or leave a team.
Review the wording periodically so references to dates, deadlines, or events do not go stale.
Send a test to yourself or a small internal group before using a broad distribution list.

Reliability, permissions, and account ownership

Cloud automation avoids one common weakness of classic Outlook delay delivery: the user’s computer does not have to be running at send time. It is not a guarantee that every email will arrive. A flow can fail if its Outlook connection expires, the account loses access, an administrator blocks a connector, or a service or mail policy prevents the message from being sent. Check the flow’s run history when a message is missing; it can show whether a run succeeded or identify an error.

Think carefully about ownership. If the flow belongs to an employee’s account, changes to that account or its permissions can affect the automation. For a business-critical message, use an approved organizational account and make sure an appropriate colleague or administrator can maintain the flow, where organizational policy allows. Do not put confidential information into a message or flow unless the recipients, storage, and access arrangements are appropriate.

Power Automate availability and licensing depend on the account, organization, connectors, and plan. The Office 365 Outlook connector is commonly available in Microsoft 365 work environments, but an organization may restrict its use or require a particular license. Check the licensing details and your administrator’s policies before depending on a flow, especially if it uses premium connectors or processes sensitive data.

Alternatives and how they compare

Power Automate is generally the practical Microsoft option for a weekly email that should send automatically from an Outlook-connected mailbox. It provides a schedule and can later be extended with data or conditions. The trade-off is that it must be set up and monitored as an automation, rather than being a normal message in the Outlook Sent Items workflow that you manually schedule each week.

If the email is important but does not need automation, create a recurring calendar reminder to prepare and send it manually. This gives a person a chance to update the content and check the recipients each week. A recurring calendar event is a reminder, not an email-sending schedule.

Classic Outlook rules are designed to process incoming or outgoing mail according to conditions; they are not a straightforward weekly timer for composing and sending the same email. Third-party scheduling products may offer recurring delivery, but review their permissions, data handling, cost, and compatibility with your organization before granting mailbox access. Avoid relying on an unsupported workaround that requires leaving a computer running unless you understand how it behaves and can maintain it.

Common problems and checks

If the flow does not send, first open Power Automate and inspect its run history. A failed run may point to an expired connection, an invalid recipient, a required field left empty, or a policy restriction. Repair the connection or correct the action, save the flow, and test it again. A successful run means the action completed, but it is still worth checking the recipient’s mailbox and any quarantine or junk-mail controls if the message is not visible.

If it runs on the wrong day or at the wrong hour, review the recurrence frequency, interval, selected weekday, start time, and time zone. Check the next scheduled run after saving. If recipients receive duplicates, check whether more than one active flow or another automation is sending the same message. Turn off obsolete copies rather than merely changing one and assuming the others are inactive.

If you are using classic Outlook’s Delay Delivery for a one-off message, remember that this is not the cloud-flow method. A message may remain in the Outbox until Outlook can process it, depending on the account and client state. For reliable repeating delivery without keeping a desktop Outlook session available, configure and monitor a cloud flow instead.

Frequently Asked Questions

Can Outlook send the same email automatically every week?
Not through Outlook’s ordinary Schedule Send control, which schedules one message. Use a weekly Power Automate recurrence trigger with the Send an email (V2) action for automatic repeats.

Does my computer need to be on for a Power Automate email?
No. A scheduled cloud flow runs in the cloud, so Outlook does not need to be open on your computer. The flow still needs a valid connection, permission to send, and an active schedule.

Can I send a different message each week?
Yes, but the basic flow sends the content you configure each time. To change it automatically, add suitable steps or dynamic content that obtains current information, and test the result so that dates and details are accurate.

Can I schedule a weekly email in Outlook without Power Automate?
You can schedule one message at a time with Outlook’s built-in send-later feature, or set a calendar reminder to send it manually each week. Outlook’s standard scheduling control does not create a repeating email series.

Why did my scheduled email not arrive?
Check the Power Automate run history, connection status, recipient address, and flow status. Also verify the recurrence time zone and inspect junk or quarantine folders. A failed run or a policy restriction may prevent delivery even when the schedule looks correct.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.