Microsoft released two AI updates this month that land on the same IT desk. Copilot got context-aware. Data Formulator got persistent database connectors. Both need governance you probably don’t have yet.
\n\n\n\nThe May 2026 Copilot update adds Memory and Personalized Insights in Word, drawing on your recent document activity and prior interactions. It surfaces relevant content without being asked, which means fewer manual prompts and more exposure risk. If your SharePoint permissions are sloppy, Copilot will surface documents to people who shouldn’t see them.
\n\n\n\nSeparately, Microsoft Research shipped Data Formulator 0.7: a free, open-source Python tool for enterprise analytics. It drops the old workflow of downloading CSVs and re-uploading them into BI tools. Instead, Data Connectors hold persistent authentication to your databases, warehouses, and BI systems. AI agents inside the tool then transform and visualize data without requiring SQL or code from the analyst.
\n\n\n\nTwo tracks, opposite operational models
\n\n\n\nCopilot is a licensed SaaS product that reads your productivity data inside Microsoft’s cloud. Data Formulator is a Python package you host yourself, with persistent connections into your backend systems. The operational models pull in opposite directions.
\n\n\n\nIf your team deploys both, you’re now managing a context-sniffing productivity assistant alongside agent-driven data connectors that hold long-lived credentials. Copilot’s reduced prompting will increase adoption and helpdesk tickets. Data Formulator’s connectors will quietly multiply unless someone inventories them. The gap between these two surfaces is where things break.
\n\n\n\n\n\n\n\nData Connectors support governed, reusable connections across databases, warehouses, BI systems, object stores, and local files, reducing integration work for platform teams.
What MSPs and IT teams should do now
\n\n\n\nFor Copilot: audit permission boundaries before the May update reaches your tenants. The new context-awareness will expose over-permissioned SharePoint sites and Teams channels. You don’t want a client calling because Copilot summarized an HR file for someone in sales.
\n\n\n\nFor Data Formulator: treat its Data Connectors like service principals. Inventory every connector, rotate credentials on a schedule, and log what data each agent can reach. If someone deploys Data Formulator as a “quick visualization tool” without these controls, you’ve just opened governed database access to an ungoverned AI agent.
\n\n\n\nMicrosoft is giving away the data integration layer to accelerate enterprise AI adoption. That’s good for adoption. It’s also a governance liability if you treat Data Formulator like a dashboard widget instead of what it actually is: a persistent data access layer.
\n