Power QueryExercises

Power Query in Excel for Mac: what works and what doesn't

Explainer · By Tahir Nas · Examples run in our simulator · Published · Updated

11 min read

Power Query works in Excel for Microsoft 365 for Mac: you can import data, shape it in the Power Query Editor and refresh it, using the same M language as Excel for Windows. What differs is the list of data sources, which Microsoft says is not the same across Excel versions, and a few details such as file paths when a workbook moves between Windows and macOS.

Where Power Query on the Mac stands

Microsoft's overview of Power Query has a table of products and the parts of Power Query each one includes. Excel for Mac is listed with the M engine and Power Query Desktop, and without Power Query Online or dataflows, exactly as Excel for Windows is (What is Power Query?, Microsoft Learn). In other words, the Mac runs the same engine and offers the desktop editing experience, not a cut-down viewer.

Microsoft's "where to get data" page gives one set of steps for both platforms: on the Data ribbon, select Get Data, then choose a connector. The same page adds that "Not all Excel versions support all of the same Power Query connectors" and points to a support article with the full list per version (Where to get data, Microsoft Learn).

Power Query on the Mac arrived in stages, and the Excel team's announcements show the order:

What arrivedVersion named by MicrosoftSource
Refresh of existing queries from Text, CSV, XLSX, XML and JSON files16.26 (Beta Channel)A journey to Power Query in Excel for Mac
Refresh from SharePoint files, SharePoint lists, SharePoint folders and OData16.41 (Insiders)Journey to Power Query in Excel for Mac continues
Power Query Editor, generally available16.69 (23010700)Shape data with Power Query Editor in Excel for Mac
Import from XML, JSON, OData, SharePoint Online List, Blank Query and Blank Table16.69 (23010700)Import data from additional data sources

The practical message is simple: if your Mac runs a current Excel for Microsoft 365, you have the editor. If you can't find Get Data (Power Query) on the Data tab, check your version under Excel > About Excel first. Microsoft's posts also note that features roll out gradually (Shape data with Power Query Editor in Excel for Mac), so two Macs on similar versions can briefly differ.

Microsoft's own support article for the Mac gives the same route, Data > Get Data (Power Query) and then Launch Power Query Editor, and the same minimum version, 16.69 (23010700). The same article also contains one sentence saying that authoring in the Power Query Editor "is not available in Excel for Mac" and that VBA supports authoring instead (Import and shape data in Excel for Mac, checked 8 November 2026). That contradicts the rest of the article and the Excel team's announcement, so if the editor is missing on your Mac, check your version and channel before assuming it is unsupported. The guide to Power Query in Excel for Windows, Mac and the web compares all three platforms side by side.

What works the same as on Windows

The things that make Power Query worth learning carry over unchanged, because they belong to the engine rather than to the host:

  • Applied steps and refresh. Each transformation is recorded as a step and replayed on refresh. Microsoft's Excel team describes refreshing with Data > Refresh All on the Mac (A journey to Power Query in Excel for Mac).
  • The M language. A query is M code whichever machine runs it. The Mac's editor writes M in the same way, and Microsoft lists Blank Query among the sources you can start from on the Mac.
  • Transformations. Microsoft's announcement of the Mac editor describes "hundreds of transformations available in Power Query Editor in Excel for Mac". Filtering, splitting, merging, grouping, pivoting and unpivoting are all M functions, not Windows features.
  • Loading. Close & Load on the Home tab loads the result to a new sheet (Shape data with Power Query Editor in Excel for Mac).

Here is a cleaning query that behaves identically on both platforms. It trims a text column and converts day-first dates and comma-thousands amounts with an explicit culture:

let
    Source = #table(
        {"Order", "Customer", "Order date", "Amount"},
        {{"1001", " Acme ", "03/02/2026", "1,250.50"}, {"1002", "Birch Ltd", "28/02/2026", "980"}}
    ),
    Trimmed = Table.TransformColumns(Source, {{"Customer", Text.Trim, type text}}),
    Typed = Table.TransformColumnTypes(Trimmed, {{"Order date", type date}, {"Amount", type number}}, "en-GB")
in
    Typed

Result

OrderCustomerOrder dateAmount
1001Acme2026-02-031250.5
1002Birch Ltd2026-02-28980

Output produced by the Power Query Exercises simulator, an independent implementation of a documented subset of M.

"03/02/2026" becomes 3 February 2026 and "1,250.50" becomes 1250.5. Stating the culture in the step matters more when a workbook is shared across machines, because without it the conversion follows the regional settings of whoever refreshes. Table.TransformColumnTypes takes the culture as an optional third argument (Table.TransformColumnTypes, Microsoft Learn). The lesson convert dates and numbers with a locale explains which culture to pick.

What is different or missing

Data sources

The connector list is the main difference. Based on Microsoft's February 2023 announcement, Excel for Mac can import from Excel workbooks, Text and CSV files, XML and JSON files, OData feeds, SharePoint Online lists, Blank Query and Blank Table. The editor announcement also names SharePoint folders, local tables and ranges, and Microsoft SQL Server among the sources the Mac editor works with.

Some connectors that Windows users take for granted were not on the Mac when those posts were written. In the comments on the February 2023 post, the Excel team said the From Web connector was on its backlog without "a solid timeline". Lists like this change between releases, so treat any list, including this one, as a starting point. For the full, current list, the Learn page above points to the support article Power Query data sources in Excel versions, which Learn describes as covering all versions of Excel for Windows and Excel for Mac. The Excel team posts quoted here all refer to Excel for Microsoft 365 for Mac.

When we checked that support article on 8 November 2026, its Mac columns listed Text and CSV, Excel workbook, XML, JSON, SharePoint List, OData Feed, Blank Query and Blank Table, plus partial entries for SharePoint Folder, SQL Server, Table/Range and Local Folder (Power Query data sources in Excel versions). The Mac article itself says SQL Server import is still in the Insiders Beta. Web was not in the Mac list.

The Data Model

If your workbook loads queries to the Data Model and builds PivotTables on top of it, test that workbook on a Mac before you depend on it. In the same comment thread, the Excel team said Data Model support for the Mac was being tracked but had no timeline. A query that loads to a worksheet table is the portable choice. The post on loading to a table or the Data Model compares the two.

File paths

A query built on Windows stores Windows paths such as C:\Users\sam\Reports\sales.csv. That path means nothing to macOS, so the refresh fails on the Mac until the path is changed. The same applies to any query that gets data from another Excel workbook by path. Microsoft's first Mac announcement, from 2019, describes the fix: Data > Connections, then Change File Path (A journey to Power Query in Excel for Mac). With the editor now available you can also open the query and edit its Source step.

Privacy levels

Microsoft's privacy levels page states plainly that "Excel on the Mac doesn't currently support privacy levels" (Privacy levels in Power Query, Microsoft Learn). On Windows, privacy levels decide whether Power Query may combine data from two sources, and the setting lives in Data > Get Data > Data Source Settings. If a workbook built on Windows relies on those settings to combine sources, test it on a Mac before you share it. The lesson on privacy levels and the formula firewall explains what they do.

Make a workbook that refreshes on both platforms

The most reliable pattern is to keep the path in one place. Put it in a cell of a small Excel table that the query reads (local tables and ranges are among the Mac editor's listed sources), or in a parameter, so moving between Windows and a Mac means changing one value instead of editing the Source step of every query:

let
    FilePath = "/Users/sam/Reports/sales.csv",
    Source = Csv.Document(File.Contents(FilePath), [Delimiter = ",", Encoding = 65001]),
    Promoted = Table.PromoteHeaders(Source, [PromoteAllScalars = true])
in
    Promoted
Shown for Excel and Power BI Desktop only: this code needs a data source or language feature the simulator doesn't run, so no output is shown.

This query reads a real file, so it only runs in Excel. In a shared workbook, FilePath would come from that settings table or from a separate parameter query; the lesson parameters: one value, many queries shows how to set one up, and the exercise switch the source query with a parameter practises it. Better still, if your organisation uses SharePoint or OneDrive for work or school, a SharePoint source avoids local paths entirely, and Microsoft lists SharePoint sources among those the Mac can refresh.

Three more habits make cross-platform workbooks less fragile:

  1. Use only connectors both platforms support. If a colleague on Windows adds a connector the Mac lacks (From Web was missing when Microsoft's posts were written), Mac users can't refresh that query.
  2. State cultures in type conversions, as in the example above, so dates and decimals don't depend on each machine's settings.
  3. Add a check query. A small query that lists column names, types and row count lets you compare a refresh on each machine at a glance.
let
    Output = Table.TransformColumnTypes(
        #table({"Order", "Order date", "Amount"}, {{"1001", "2026-02-03", "1250.5"}, {"1002", "2026-02-28", "980"}}),
        {{"Order date", type date}, {"Amount", type number}},
        "en-GB"
    ),
    Schema = Table.SelectColumns(Table.Schema(Output), {"Name", "Kind"}),
    WithRows = Table.AddColumn(Schema, "Rows", each Table.RowCount(Output), Int64.Type)
in
    WithRows

Result

NameKindRows
Orderany2
Order datedate2
Amountnumber2

Output produced by the Power Query Exercises simulator, an independent implementation of a documented subset of M.

The check shows Order date as date and Amount as number, each with 2 rows, and Order as any because no type was set for it. That last line is the kind of gap a check query catches: an untyped column takes whatever the source supplies, so later steps and lookups can't rely on its type. The lesson inspect column types with Table.Schema goes further, and the guide to moving queries between Excel and Power BI covers the same portability problem between hosts.

Should you learn Power Query on a Mac?

Yes. The skills that take time to learn, such as choosing the right transformation, reading M, handling types and errors, and building queries that survive refresh, are identical on both platforms. The lesson Power Query in Excel and Power BI: same engine, different hosts explains why skills move between hosts. What you can't practise on a Mac is any connector it lacks, and for most learners that list doesn't matter while they are learning the transformations.

If you want to practise without worrying about your Excel version at all, the exercises on Power Query Exercises run in the browser, so they behave the same on a Mac, a Windows PC or a Chromebook. A good first one is clean and summarise a sales export.

Frequently asked questions

Which version of Excel for Mac do I need for the Power Query Editor?

Microsoft's Excel team announced the editor as generally available in Excel for Microsoft 365 for Mac version 16.69 (23010700) or later. You can see your version under Excel > About Excel.

Can I open a Windows workbook with Power Query queries on my Mac?

Yes. The queries are stored in the workbook as M. Whether they refresh depends on their sources: file paths need changing to Mac paths, and any connector the Mac lacks will fail to refresh. Keeping the path in an Excel cell read as a parameter makes that change one edit.

Sources

About the author

Tahir Nas, software engineer, writes and reviews the lessons, guides and exercises on Power Query Exercises. Tahir has 8 years of experience in tech, working across system administration, cloud architecture, QA, scripting and automation, and software engineering in many languages and mainstream databases. GitHub profile. Every M example shown with a result was run in the site's simulator when the page was built, and the output is that run's result; examples marked for Excel and Power BI only are shown without output. How content is tested.

Keep reading

Practise Power Query in the browser with graded exercises checked against fresh data.

Power Query Exercises is an independent educational platform and is not affiliated with, endorsed by, sponsored by, or approved by Microsoft Corporation. All third-party trademarks belong to their respective owners.