Define the clock the business means

Write the requirement as “daily at 09:00 in the London time zone”, not “every 24 hours from now”. Agree who checks late or missing briefings and what delivery delay is acceptable. Scheduled execution is a target, not a guarantee that an email reaches a mailbox at that exact second.

For the expressions below, the source is a confirmed UTC timestamp ending in Z. Do not assume every connector returns UTC. Inspect the original output and its documentation. A date-only value, such as a training expiry date, is not automatically a midnight UTC event.

Test conversion without sending messages

Create an Instant cloud flow with a manual trigger. Add a Compose action, rename it SourceUtc and enter 2026-07-15T08:00:00Z as plain text. Add another Compose named UkDisplay. In its Expression editor, paste:

convertTimeZone(
  outputs('SourceUtc'),
  'UTC',
  'GMT Standard Time',
  'dd/MM/yyyy HH:mm'
)

Add UkDate as a third Compose, using this expression for an ISO-style local date:

convertTimeZone(outputs('SourceUtc'),'UTC','GMT Standard Time','yyyy-MM-dd')

Paste expressions without a leading @ or surrounding quotes in the Expression editor. Name SourceUtc before referencing it. Microsoft supports convertTimeZone and the built-in Convert time zone action; GMT Standard Time is the Windows identifier associated with London. Despite its name, it is not simply a fixed UTC offset.

The summer fixture should return 15/07/2026 09:00 and 2026-07-15. Run all seven fixtures below by replacing SourceUtc. See Microsoft's conversion guidance and Windows time-zone identifiers .

Configure the daily recurrence

Create a separate scheduled cloud flow and open its Recurrence trigger. Set Frequency = Day, Interval = 1, select the London time-zone entry, and set At these hours = 9 and At these minutes = 0. In the classic designer these fields are under advanced options; the new designer exposes trigger parameters.

Choose a future first occurrence. Check the saved recurrence settings, including the zone and schedule, rather than relying on the creation dialogue alone. The fragment below illustrates the intended recurrence object; it is not an importable flow package. Replace the example start date with a future date when you build it.

{
  "frequency": "Day",
  "interval": 1,
  "startTime": "2026-10-19T09:00:00",
  "timeZone": "GMT Standard Time",
  "schedule": {
    "hours": [9],
    "minutes": [0]
  }
}

Power Automate's scheduling guidance links to advanced recurrence documentation , which explains zone and start-time behaviour. Keep outbound actions absent while checking the first scheduled run; an unexpected diagnostic run should not send anything.

Capture one run timestamp

In the scheduled flow, add Compose RunUtc with the expression utcNow(). Add Compose RunUk using:

convertTimeZone(
  outputs('RunUtc'),
  'UTC',
  'GMT Standard Time',
  'dd/MM/yyyy HH:mm'
)

Keep RunUtc as the original evidence. RunUk is human-readable text and carries no UTC offset in this chosen format. If you later add a message, an example subject expression is:

concat(
  'Operations briefing — ',
  convertTimeZone(outputs('RunUtc'),'UTC','GMT Standard Time','dd/MM/yyyy')
)

Capture once and reuse it so a run crossing local midnight does not build different date labels in separate actions. RunUtc records when that Compose executes; it is not proof of the trigger's intended start or of delivery. Label the message time as UK local time, not “GMT” throughout summer.

Verify the trigger and delivery separately

First compare the conversion outputs with the fixture table. Then observe real scheduled diagnostic runs and compare their UTC run-history evidence with the intended UK time. Fixed input tests prove conversion, not recurrence. Finally, add a controlled test recipient and verify message arrival before enabling business recipients.

Record the configured schedule, actual run time, conversion output and delivery result separately. Review the first run after the October change. Agree a fallback for a missed briefing; do not assume a missed run will automatically be replayed.