The gap between what Mac Excel can do and what Power Query promises is not a minor inconvenience. It is a real, present limitation that will surface exactly when you need it most, usually in the middle of a shared workflow. The user who posted this question is not asking for a feature wishlist. They are building a process for a team, and one person on that team uses a Mac. That single detail changes everything. If you are that person, or if you are the one supporting them, the practical takeaway is simple: do not assume parity. Test every step of your query on the machine that will actually run it.
What is missing is not a single headline feature but a collection of small, frustrating absences. Some connectors are unavailable. Certain transformations behave differently. The Power Query editor itself may not support the same visual interface or advanced scripting options you rely on daily. The user who asked this question is smart to ask early, because the cost of discovering a missing function is not a quick fix. It is a redesign of the process, a rework of the data model, or a fallback to manual steps that defeat the purpose of automation.
The deeper issue here is about trust. When you build a solution in a tool, you assume the tool is consistent across platforms. That assumption is wrong in this case, and it is wrong in a way that punishes collaboration. Teams do not work in isolation. They share files, they pass queries back and forth, and they expect the same results on a MacBook as on a Windows desktop. When that expectation fails, it is not just a technical hiccup. It is a breakdown in the collaborative promise of the tool itself.
So what should you do? Before you invest hours in a query, run a compatibility check on the Mac. Open the file there. Click through every step. Try the connectors you plan to use. If something breaks, you have two options: find a workaround that stays within the limits of the Mac version, or accept that your process may require a Windows environment for full functionality. Neither option is elegant, but both are honest. The user who posted this question is already ahead of the curve because they asked before they built. That is the right instinct. Carry it forward, and you will save yourself the most valuable resource you have: time.