Streamlining your tech stack for maximum efficiency

Learn, explore, and grow with our knowledge hub.

Automate Excel Reports with Power Automate: Step-by-Step | Smart Statistics
Power Automate Tutorial

Automate Excel Reports to Email with Power Automate

Turn a repetitive Excel reporting routine into a controlled Microsoft 365 workflow that prepares information, distributes it automatically and leaves a clear operational trail.

Weekly Reporting Control Workflow ready
Reporting rows 124 Data available
Recipients 8 Configured
Flow status Ready Scheduled
Reporting activity
87%
Excel
Automate
Email
Illustrative workflow dashboard
Scheduled workflow Run reporting automatically when the business needs it.
Structured Excel data Read controlled tables from Microsoft 365.
Consistent delivery Send the right reporting output to the right people.
Better control Use run history, monitoring and failure handling.
The business problem

Your team should not be the reporting scheduler.

Excel remains central to reporting in many UK businesses. The difficulty is often not the workbook itself. It is the repetitive manual process surrounding it.

A finance manager may update a workbook every Friday, prepare an email and distribute figures to several managers. An operations team may repeat the same reporting process every morning. A sales manager may manually send a pipeline summary at the end of every week.

Each task may appear small in isolation. Repeated across weeks, departments and reporting cycles, however, it becomes administrative overhead and creates additional opportunities for inconsistency.

  • Less manual administration: reduce repetitive preparation and distribution.
  • More consistency: use the same controlled workflow every reporting cycle.
  • More time for analysis: allow people to focus on exceptions and decisions.
Weekly Operations Summary Ready
Department Open Done Status
Operations 14 87 On track
Finance 6 42 On track
Sales 21 64 Review
Decision-ready reporting

Automation should reduce handling without removing the controls required to trust the output.

Solution architecture

What we are going to build

We will create a scheduled Power Automate cloud flow that retrieves structured reporting information from Excel, converts it into an email-friendly output and distributes the report through Microsoft 365 Outlook.

Scheduled trigger Starts the reporting process automatically.
Excel Online Retrieves rows from the reporting table.
Email delivery Sends the controlled reporting output.
Before you start

Three things your workflow needs

A small amount of preparation makes the automation easier to build, troubleshoot and maintain.

Cloud-based workbook

Store the workbook in SharePoint or OneDrive for Business so Power Automate can work with it through the Microsoft 365 connector.

Structured Excel table

Put the reporting data inside a proper Excel Table. Avoid relying on arbitrary worksheet ranges if the flow needs predictable structured data.

Correct Microsoft 365 access

Confirm that the account used by the flow has access to the workbook, Power Automate and the services required by the workflow.

Step-by-step tutorial

Build the Power Automate workflow

The following pattern gives you a practical starting point for a recurring management or operational report.

Prepare the Excel reporting table

Start by making the workbook automation-friendly. Suppose an operations report contains the following columns.

Department OpenItems Completed Status
Operations 14 87 On Track
Finance 6 42 On Track
Sales 21 64 Review

The figures above are illustrative and are included only to demonstrate the workflow.

Select the range in Excel and use Insert → Table. Give the table a meaningful name such as tblWeeklyReport.

Use descriptive object names.

Names such as tblWeeklyReport are much easier to understand and maintain than generic names such as Table1.

Create a Scheduled cloud flow

In Power Automate, create a Scheduled cloud flow. Give it a name that describes the business process, not merely the technology.

Weekly Operations Report Distribution

Configure the recurrence for the required reporting cycle. For example, a weekly management report might run every Monday morning.

The schedule should reflect the availability of the underlying data. There is little value in distributing a report at 07:00 if an upstream process does not finish preparing the source data until 07:30.

Retrieve the Excel rows

Add the Excel Online (Business) action List rows present in a table.

Configure the location, document library, workbook and the tblWeeklyReport table.

Think about data volume.

If your reporting table is becoming large, review pagination, filtering and whether Excel is still the right operational data store.

Convert the rows into an email-friendly output

Add the Data Operations action Create HTML table and use the value array returned by the Excel action as the input.

Automatic columns are useful when prototyping. For production reporting, custom columns usually create a cleaner management output because you decide which fields appear and how they are labelled.

Design for the decision, not the workbook.

If Excel contains 25 columns, that does not mean all 25 should appear in a management email. Surface what the recipient actually needs to understand or act upon.

Generate the reporting date dynamically

Do not manually update the reporting date every week. Power Automate can create it dynamically.

formatDateTime(utcNow(),'dd MMMM yyyy')

The expression takes the current UTC timestamp and formats it into a readable date.

A subject line can therefore follow a pattern such as:

Weekly Operations Report – @{formatDateTime(utcNow(),'dd MMMM yyyy')}

Where local business time is operationally important, explicitly account for the appropriate UK timezone rather than assuming UTC always represents the intended reporting date.

Send the report through Microsoft 365 Outlook

Add the Outlook Send an email (V2) action. Configure the recipients, subject and body, then insert the HTML table output.

<p>Good morning,</p> <p>Please find below this week's operations summary.</p> [HTML table output] <p>The detailed workbook is available in the reporting area.</p>

Keep recipients configurable where practical. Embedding a large collection of addresses directly inside a complex workflow can make future changes harder than necessary.

Test failure scenarios, not just the happy path

A successful test run proves that the workflow can work. It does not prove that it will behave correctly when something unexpected happens.

Test the workflow with realistic scenarios including:

  • normal reporting data;
  • an empty reporting table;
  • unexpected or missing values;
  • a renamed or moved workbook;
  • authentication problems;
  • recipient changes; and
  • larger-than-normal data volumes.
Production quality

Make the automation reliable, not merely automatic

The difference between a useful prototype and a dependable business process is usually found in monitoring, ownership and maintainability.

Handle failures explicitly

Important workflows should notify the appropriate owner when the reporting process fails.

Separate configuration

Consider storing frequently changed recipients and settings outside the core workflow.

Document ownership

Record who owns the flow, workbook and underlying business process.

Monitor the process

Use run history and appropriate operational checks so problems are visible rather than silent.

Architecture matters

Know when Excel automation is no longer enough

Automating an Excel process does not mean that every process should remain in Excel indefinitely.

01

Excel + Power Automate

Suitable for controlled lightweight workflows with structured workbook data.

02

SharePoint / Lists

Useful when structured multi-user records and simpler operational controls are required.

03

Dataverse / SQL

Consider more structured data platforms as process complexity, relationships and governance increase.

04

Power BI / Fabric

Use a broader analytics architecture when reporting, modelling and governed insight become the priority.

Choose the technology around the process.

Smart Statistics helps organisations identify where lightweight automation is appropriate and where a more structured data solution would provide better reliability, scalability and governance. Explore our data, reporting and automation services .

Frequently asked questions

Excel reporting automation FAQs

Can Power Automate automatically email an Excel report?

Yes. A scheduled cloud flow can access structured Excel data stored in SharePoint or OneDrive for Business and distribute reporting information through Microsoft 365 Outlook.

Does the Excel workbook need to be in OneDrive?

For the cloud-based approach described here, the workbook would normally be stored in OneDrive for Business or SharePoint so the Excel Online (Business) connector can access it.

Can different managers receive different information?

Yes. Conditions, filters and configuration data can be used to control which information goes to particular recipients. If the solution becomes increasingly complex, however, review whether Power BI or a more structured reporting architecture would be easier to maintain.

What happens if the Power Automate flow fails?

Power Automate provides run history for diagnosing workflow failures. For an important business process, build explicit failure handling and notifications rather than relying on somebody noticing that an expected email never arrived.

Should every recurring Excel report be automated?

No. Automation is most valuable when the process is sufficiently stable and the underlying data is reliable. If the reporting process itself is poorly defined, automating it may simply make a weak process run faster.

Smart Statistics

Turn repetitive reporting into a reliable business process.

If your team is repeatedly refreshing workbooks, preparing the same outputs and distributing the same reports, Smart Statistics can help you identify what should be automated and design a solution that is controlled, maintainable and appropriate for your business.