Am i trying to make Copilot in Excel do too much here?

I'm responsible for a weekly performance pack that goes to a few department heads. Final version's in Excel cause that's what everyone's comfortable with, but the data comes from a mix of places outside 365 - some marketing data, some CRM, some internal numbers from SharePoint.

Right now it's a workbook full of Power Query steps, lookup tables and manual mappings. Technically works but its getting fragile. One source renames a column and half the refresh breaks. Some queries only refresh properly from my desktop, don't ask me why. Credentials randomly need reconnecting. Different sources finish updating at different times so the workbook can look complete while some tabs are still on old data, which is its own fun problem. And Copilot gives a nice summary of it all but unless i check every tab first i don't actually know if its summarizing a fully refreshed file or a half stale one.

Not trying to build a full data platform here, just want one reliable workbook thats ready before the weekly meeting and that Copilot can use without me spending an hour double checking whether the numbers are even current.

Would you keep this in Excel and clean up the Power Query mess, move it into Power BI/Fabric, or separate the data collection from the workbook entirely? Mostly curious how other people handle the Copilot's great but only once the data's actually trustworthy part.

Posted Aug 5, 2026, 1:26 PM UTC

26
Loading comments…