SharePoint

Agents, Governance and "Show-Your-Work" AI: What Microsoft Shipped This Week

Content type Blog Post

Author Anouck Fierens

Publication Date 3 Nov, 2026

Reading Time 6 minutes

Contents

Introduction
1. Power Platform: Can IT finally see — and govern — everything makers have built?
2. SharePoint & Teams: What is actually changing in the day-to-day experience?
3. Governance: How do I keep AI and agents under control as they spread?
4. Copilot: Is it ready for high-stakes, verifiable work?
The bottom line
SOURCES
About the author

Introduction
1. Power Platform: Can IT finally see — and govern — everything makers have built?
2. SharePoint & Teams: What is actually changing in the day-to-day experience?
3. Governance: How do I keep AI and agents under control as they spread?
4. Copilot: Is it ready for high-stakes, verifiable work?
The bottom line
SOURCES
About the author

Introduction

A week of Microsoft blog posts points to one theme — the company is racing to make Copilot and its agents trustworthy enough for regulated, high-stakes work, while handing IT the controls to keep up.

Reviewing the past week across Microsoft’s official product blogs — the Microsoft 365 Blog, the Power Platform Blog, and the SharePoint and Teams channels on the Tech Community — a clear pattern emerges. Almost every announcement is now framed around two questions: can you trust what the AI did, and can IT govern where it went?

Here are the four questions that matter most right now — one each for Power Platform, SharePoint & Teams, Governance, and Copilot.

1. Power Platform: Can IT finally see — and govern — everything makers have built?

For years the answer was “not easily.” The June 2026 Power Platform feature update changes that. The enhanced Power Platform Inventory, in public preview since June 2, now captures the connectors and connector operations used by every canvas app, model-driven app, cloud flow, agent flow, Microsoft 365 agent flow, and agent in a tenant.

In practice, an admin can pinpoint every resource affected by a connector deprecation, a security issue, or a licensing-tier change in seconds rather than weeks — the kind of visibility that matters now that agents, not just apps, are part of the inventory.

Two more updates round out the release: a new release planner code app from the Power CAT team (built on Power Apps code apps, React, and custom connectors) for tracking upcoming features across Power Platform, Dynamics 365, and Copilot, and version comparison in Power Automate for desktop, so makers can see exactly what changed between two versions of a flow.

Why it matters: governance has shifted from afterthought to headline feature. As low-code agents proliferate, the platform’s value increasingly rests on being able to account for what they touch.

2. SharePoint & Teams: What is actually changing in the day-to-day experience?

On the SharePoint side, a new look and feel is rolling out across key surfaces — reduced visual noise, better readability, and more consistency, while preserving the branding investments organizations already made. At the same time, Copilot in SharePoint moved to an opt-out preview: from mid-June, Copilot capabilities began appearing across sites, pages, libraries, lists, and chat for licensed users unless an admin explicitly opts the organization out.

Teams is in a season of retirements and refreshes. Teams Live Events retires June 30, with Microsoft steering customers to town halls, and the classic Together mode is being phased out in favor of gallery view. New arrivals include the Queues app on Teams mobile, a Teams Rooms “room builder” for IT, BYOD peripheral health reporting, and CSV-based breakout room assignments.

One commercial change for planners: Microsoft stopped selling standalone SharePoint Online Plan 1 & 2 and standalone OneDrive for Business Plan 1 & 2 to new customers after May 31, 2026.

Why it matters: the interface is getting quieter while Copilot gets louder. Admins who do nothing will still see Copilot show up in SharePoint — the default is now on.

3. Governance: How do I keep AI and agents under control as they spread?

This was the busiest theme of the week, and it runs through Microsoft Purview. The message is consistency: as Copilot reads more content and meetings generate more AI artifacts, the same labelling, retention, and discovery controls are being extended to those new surfaces.

Concretely, Teams Whiteboards now inherit SharePoint-based Purview controls — DLP, sensitivity labels, retention, eDiscovery, and audit logging apply to whiteboard content the way they do to documents. And a new Data Security Posture Management (DSPM) experience adds AI observability: a single view of every AI app and agent active in the last 30 days, including those running on Microsoft Agent 365.

Rounding it out: new safeguards for sensitive data in Copilot prompts and web searches, bulk remediation of overshared content, and expanded Copilot Dashboard analytics for clearer visibility into usage, risk, and business impact.

Why it matters: the governance perimeter is being redrawn around AI outputs, not just files. Whiteboards, prompts, and agent activity are becoming first-class objects that compliance teams can label, retain, and discover.

4. Copilot: Is it ready for high-stakes, verifiable work?

The week’s flagship post made the clearest case yet. Copilot in Excel, “built for the era of Frontier Finance,” targets the one audience that will not accept an answer it cannot trace: finance. The pitch rests on three pillars.

Skills. Teams can define how Copilot completes recurring processes — building a DCF, closing the books, refreshing a reporting model — using an open-standard, markdown-based SKILL.md file saved to OneDrive. A sample library ships now; custom skills are in Insiders, with partner-built skills coming in Q3.
Trusted data. New financial connectors bring institutional sources into the workbook — CB Insights, Daloopa, FactSet, Morningstar, PitchBook, and S&P Global (via Kensho) — alongside the LSEG and Moody’s connectors from May.
Traceability. Users can “Plan with Copilot” before any change, previewing which ranges, formulas, and assumptions it intends to touch; once applied, every edit is attributed to Copilot in the Show Changes pane.

That post sits inside a busy month: Copilot Cowork reached general availability on June 16 (Microsoft says more than half the Fortune 500 used it in preview), the Work IQ APIs went GA, and Copilot Chat now lets users pick Anthropic’s Claude as a model — with Microsoft citing roughly 50% faster responses.

Why it matters: Microsoft is betting the next phase of adoption is won on trust, not novelty — verifiable steps, cited data, and a clear audit trail. If it works in finance, it works almost anywhere.

The bottom line

Three currents ran through the week: agents are now everywhere, governance is racing to wrap around them, and Copilot is being re-engineered to show its work. For IT and business leaders, the practical takeaway is to check the defaults — several of these changes, from Copilot in SharePoint to AI observability in Purview, are arriving switched on.

What’s landing best in your environment — and what are you switching off? I’d love to hear how you’re handling the opt-out defaults.

#Microsoft365 #Copilot #PowerPlatform #SharePoint #MicrosoftTeams #Governance #Purview #AI