Context was retrieved when the question was asked

Microsoft's May update described federated Copilot connectors retrieving live data from services including HubSpot, Notion, LSEG and Moody’s through MCP while maintaining existing access controls. Project teams could combine documents with operational status without first copying everything into one index. An answer consequently depended more on time, permissions and the source system's current state.

Copilot Notebooks continued to support shared working context, while Word surfaced recent changes and comments in chat. This could shorten meeting preparation, but project leaders still had to distinguish a current snapshot from an approved baseline. A live answer needed links, a timestamp and the decision it supported.

Access had to match the action

Gartner warned on 26 May against uniform governance for all agents. It distinguished ability to act from scope of access and forecast that governance failures could cause many autonomous agents to be demoted or retired. The forecast was uncertain, but the distinction was useful: an agent reading project data needed different limits from one updating a plan or sending tasks.

A data map could record source owner, refresh frequency, sensitivity and fields available to the agent. An agent register could distinguish reading, proposing and acting, with an approver for every level. Automation and analysis would then use the same access model as collaboration.

The project log connected evidence with the decision

The team could test one decision type, such as whether a delivery was ready for the next phase. The answer needed sources, last update and variance from baseline. The project log recorded the accountable approver and selected action. Stale references, missing access and reversed decisions provided a better quality measure than the number of Copilot questions.

Controls in practice

Federated access reduced copying but made availability more dynamic. A source could be unavailable, return different results to another user or change after a decision. The project therefore needed to retain the figures and document versions actually used while linking to the live source for later checking.

Gartner's governance model considered both autonomy and trust boundary. A project could use a simple matrix: read public material, read internal data, propose a change and execute a change. Every level received its own permissions, evaluation requirement and approver. One agent could then expand gradually without granting every agent the same broad mandate.

Sources

Microsoft 365 Copilot Blog: What’s new in Microsoft 365 Copilot – May 2026, 29 May 2026.

Microsoft 365 Copilot Blog: Federated Copilot connectors, 5 May 2026.

Microsoft 365 Copilot Blog: What’s new in Notebooks – May 2026, 26 May 2026.

Gartner: Governance must reflect agent autonomy and scope, 26 May 2026.

For discussion

Which live data sources does the project need, and who owns the definition when an answer changes?