Microsoft Excel Adds Federated Financial Connectors and Copilot Skills

Per a Microsoft Excel blog post (May 28, 2026), Copilot in Excel can now pull live data from LSEG and Moody's using federated connectors built on the Model Context Protocol. The blog describes a workflow where users connect via the Sources menu with provider credentials, enable the source toggle, and Copilot retrieves data at query time, asking users to confirm the data source before inserting results into the sheet. For finance teams and data practitioners, query-time access to institutional market data in spreadsheets reduces manual copy-paste, shortens refresh cycles, and raises new questions about governance and entitlements.
What happened
Per a Microsoft Excel blog post on the Microsoft Tech Community (May 28, 2026), Copilot in Excel can now connect to institutional data from LSEG and Moody's using federated connectors. The post states these connectors are built on the emerging industry standard Model Context Protocol and that Copilot will query the source systems at the moment a request is made, returning the latest available data. The blog also documents an in-app flow: open the Sources menu, connect to the provider with credentials, turn the source toggle on, and have Copilot request confirmation before incorporating provider data into the workbook.
Technical details
Per the Microsoft Excel blog, the LSEG connector exposes market data including foreign exchange rates, equities, and pricing via a standardized, AI-ready interface while preserving governance and entitlements. The post describes the connectors as "federated" because they retrieve context from the provider at runtime rather than copying static snapshots into the service. The blog emphasizes use cases such as updating hedging models or checking current credit ratings where query-time freshness matters.
Industry context
Practical implications
What to watch
Editorial analysis
The move aligns with a broader industry pattern toward runtime data integration for AI assistants, where standardized protocols such as Model Context Protocol aim to make external, institutional datasets available to models without breaking existing enterprise controls. Companies and practitioners integrating third-party market data into analytic workflows often balance the benefits of fresher inputs against governance, entitlement checks, and audit logging requirements.
For data teams, embedding federated connectors into spreadsheets shifts some data validation and lineage work upstream, which can simplify analyst workflows but also requires revisiting access controls and data provenance processes. Observability and reproducibility of workbook-driven analyses become more important when results depend on live, external queries.
Observers should look for additional provider integrations beyond LSEG and Moody's, vendor support for Model Context Protocol across platforms, and product-level details on entitlements, logging, and repeatable extraction for testing and audit scenarios.
Key Points
- 1Federated connectors bring query-time institutional data into spreadsheets, reducing manual ingestion delays and improving finance model inputs.
- 2Standardizing on Model Context Protocol enables multiple providers to expose AI-ready context while preserving governance and entitlements.
- 3Embedding live data into Copilot workflows raises operational needs for provenance, access controls, and reproducible workbook analytics.
Scoring Rationale
Notable product update extending MCP-based federated data connectors to LSEG and Moody's in Excel Copilot, improving analyst workflows for enterprise finance users. Impact is real but specialized to the M365 Copilot and institutional finance segment; broader AI/ML practitioners are adjacent, not primary, beneficiaries.
Sources
Primary source and supporting public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems
