Microsoft Release Notes

Work IQ now grounds Microsoft Copilot and agents in your core business data from Microsoft Dynamics 365 and Microsoft Power Platform. Work IQ reasons across the productivity and business data that matters to your business. It’s available in preview starting September 30, 2026, with rollout continuing throughout October 2026.

A diagram showing Work IQ as the intelligence layer for Copilot and agents, connecting Microsoft 365 apps, Dynamics 365 apps, and Copilot.

By connecting and modeling your business once, you create a shared foundation for Copilot and agents: what your data means, how records relate, and which business rules guide the next step. You can then reuse that understanding and governed actions across Copilot and agent experiences without rebuilding context for every agent.

Business applications data and workflows in Work IQ shift the starting point from navigating apps to expressing what you need to accomplish. Your business applications remain the systems of record, but their data and processes are modelled into valuable, reusable business understanding and context made available through Copilot and agents. …

Release Summary

Category	Description
Announcements	Announcements about unload event changes and WIP and MDAG retirement in Microsoft Edge.
Feature Updates	Updates to profile setup, third-party sign-in, and password details in Microsoft Edge.
Policy Updates	New and updated policies in Microsoft Edge.
Security	Stable channel security updates are listed here.

Announcements

• Deprecating the unload event. Microsoft Edge is changing the default behavior of the web platform unload event. As the rollout progresses, pages will no longer run unload event handlers unless the site explicitly permits them.

  • In Edge 152 and 153, unload handlers will stop firing by default for 60% of page loads unless the site explicitly enables them through Permissions Policy.
  • In Edge 154, the rollout will increase to 80% of page loads.
  • In Edge 155, the rollout will reach 100% of page loads.

  The unload event is not a dependable way to save data, perform cleanup, or report the end of a session. Browsers and operating systems can suspend or terminate pages without firing it, and this can prevent pages from using the back/forward cache, which may make back and forward navigation slower.

  Web developers should migrate to lifecycle events and APIs designed for these scenarios. The long-term direction of the web platform is to remove support for unload. …

Microsoft 365 Copilot

• Seamless Search and Chat Integration [Windows, Web]

  Microsoft 365 Chat brings the power of conversational AI directly into Microsoft 365 Copilot Search, enabling users to move effortlessly from finding information to acting on it. Search results become the foundation for contextual chat, allowing you to ask follow-up questions, synthesize insights, and generate content—all in one unified experience. This integration reduces workflow fragmentation, accelerates decision-making, and delivers a more intuitive way to interact with your organization’s knowledge.

  Roadmap ID:512429

  Details:

  What changed: Microsoft 365 Copilot Search now embeds conversational AI chat directly within search results. Previously, users had to switch between search and chat tools separately. This update allows follow-up questions, insight synthesis, and content generation based on search context in a unified interface, reducing workflow fragmentation.

  Why: Integrating chat with search streamlines user interaction with organizational knowledge, accelerating decision-making and reducing the need to switch tools.

  Try this:

  1. Open Microsoft 365 Copilot Search.
  2. Enter a query and review the search results.
  3. Use the chat pane to ask follow-up questions or generate content based on the results. …

[1.19.0] - 2026-09-18

Added

• agent-framework, agent-framework-core: Add generic vector-store provider protocols, instrumentation message-event controls, and per-tool AgentModeProvider exposure controls (#8421, #8451, #8450)
• agent-framework-mongodb: Add the alpha MongoDB vector-store connector (#8184)
• agent-framework-azure-documentdb: Add the alpha Azure DocumentDB vector-store connector (#8185)
• agent-framework-azure-cosmos, agent-framework-core: Add an Azure Cosmos DB NoSQL implementation of the shared vector-store APIs (#8186)
• agent-framework-orchestrations: Add stable names for built-in orchestration workflows and register their checkpoint types for restoration (#8384, #8258)
• agent-framework-devui: Display Aspire traces in the developer UI (#7874)
• agent-framework-core: Add an option to invoke function calls sequentially (#8453) …

What's Changed

• .NET: fix: race concdition in workflow formula state by @baywet in https://github.com/microsoft/agent-framework/pull/8252
• .NET: update remaining dependencies by @baywet in https://github.com/microsoft/agent-framework/pull/8307
• .NET: fix: inspect for delemiter value before adding headers by @baywet in https://github.com/microsoft/agent-framework/pull/8301
• docs: fix 'availble' typo in ADR 0001 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8325
• .NET: docs: use 'a FunctionApprovalRequestContent' in ADR 0006 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8322
• .NET: docs: fix 'valueable' typo in ADR 0001 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8318
• .NET: docs: remove duplicate 'turns' in ADR 0006 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8317
• .NET: docs: fix 'extention' typo in ADR 0001 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8316
• docs: fix 'allow to' grammar in ADR 0011 by @mrchatam in https://github.com/microsoft/agent-framework/pull/8335
• Improve issue triage by @moonbox3 in https://github.com/microsoft/agent-framework/pull/8362
• .NET: expose OpenTelemetryAgent.DefaultSourceName by @YashvantHange in https://github.com/microsoft/agent-framework/pull/7815
• .NET: Temporarily skip flaky steering harness session reuse test by @rogerbarreto with @Copilot in https://github.com/microsoft/agent-framework/pull/8377 …

The semantic model settings pane is becoming the default way to configure semantic models in the Power BI service. The pane opens alongside your workspace, so you can review and change settings without leaving the current page. It provides the same settings as the full semantic model settings page while keeping the surrounding context visible. The classic settings page remains available during this transition, but it no longer opens first. This change builds on the settings pane preview and provides a more focused experience for managing semantic models.

Why it matters

The pane helps you stay in context while you manage a semantic model. It opens on the right side of the browser window and keeps your workspace visible. Settings are organized into expandable sections and tabs, including refresh, data access, performance, and OneDrive and SharePoint. You can use the search box at the top of the pane to find a setting across all sections and tabs. For example, enter "re" and select View refresh history to go directly to refresh history instead of opening sections one at a time. This organization is especially useful for semantic models with several connection, refresh, or performance settings. You can review a setting, make a change, and return to your work without navigating to a separate page.

What's changing …

Commerce personalization experiences continue to expand beyond traditional storefronts as customers interact with businesses across stores, websites, mobile apps, marketplaces, social channels, and conversational experiences. AI and agents are creating even more possibilities for how customers, employees, and business buyers interact with commerce. For developers and architects, this raises an important question: how do you introduce new custom experiences without rebuilding the commerce capabilities behind each one?

Microsoft Dynamics 365 Commerce provides a composable, API-first architecture that separates the experience layer from the commerce engine. New licensing offers customers more flexibility to use Dynamics 365 Commerce to build custom applications, connect third-party experiences, and support new commerce scenarios. Organizations can create experiences for their specific business requirements while using Dynamics 365 Commerce capabilities for pricing, promotions, inventory, loyalty, orders, fulfillment, and other commerce processes.

How AI and new channels are reshaping commerce experiences …

What's Changed

• .NET: Replace deprecated AWSSDK.Extensions.Bedrock.MEAI with AWS.Bedrock.MEAI by @BenGearset in https://github.com/microsoft/agent-framework/pull/7983
• .NET: Remove Azure.AI.OpenAI dependency by @rogerbarreto in https://github.com/microsoft/agent-framework/pull/7986
• .NET: Track and update A2A task state by @SergeyMenshykh in https://github.com/microsoft/agent-framework/pull/7998
• .NET: Update Azure AI Projects to 3.0.0 beta 1 by @rogerbarreto in https://github.com/microsoft/agent-framework/pull/7995
• .NET: Bump Aspire.Hosting from 13.5.2 to 13.5.3 by @dependabot[bot] in https://github.com/microsoft/agent-framework/pull/8029
• .NET: [BREAKING] Add file_access_read_lines and move the line-numbering contract onto AgentFileStore by @antsok in https://github.com/microsoft/agent-framework/pull/7671
• Bump Anthropic from 12.42.0 to 12.43.0 by @dependabot[bot] in https://github.com/microsoft/agent-framework/pull/8028
• .NET: Bump AgentMemory.AgentFramework from 1.4.1 to 1.5.0 by @dependabot[bot] in https://github.com/microsoft/agent-framework/pull/8027
• .NET: [BREAKING] Clarify A2A agent run modes by @SergeyMenshykh in https://github.com/microsoft/agent-framework/pull/8032
• .NET: Clarify declarative workflow input serialization by @UniversePeak in https://github.com/microsoft/agent-framework/pull/8046
• .NET: Preserve streamed annotations in Foundry hosted responses by @rogerbarreto in https://github.com/microsoft/agent-framework/pull/7984 …

[1.18.0] - 2026-09-10

Added

• samples: Add Magentic custom-manager prompts and MLflow observability examples (#7876, #8085)
• agent-framework-core: Add shared vector-store abstractions, portable filters, and an in-memory vector store (#8014, #8115)
• agent-framework-core: Add a maximum-duration bound and stop-reason signal to the tool invocation loop (#7772)
• agent-framework-core: Support mixed workflow invocation keyword arguments (#7963)
• agent-framework-ag-ui: Add emit_messages_snapshot configuration for suppressing the terminal message snapshot (#7808)
• agent-framework-ag-ui, agent-framework-core: Add supported MCP Host-history conversion for persisted AG-UI conversations (#8130)
• agent-framework-azure-ai-search, agent-framework-core: Add an Azure AI Search implementation of the shared vector-store APIs (#8153) …

In December, we announced the retirement of Power BI Q&A, our legacy natural-language querying experience, with retirement planned for December 2026. To give current Q&A user's additional time to assess their dependencies and transition to newer Copilot-powered solutions, we’re extending the retirement date to February 2027. This post recaps the affected experiences and provides updates on Copilot capacity availability, embedded scenarios, and sovereign clouds.

Recap of the January announcement

What is being deprecated?

The retirement applies to both the end-user Q&A experiences, and the associated Q&A configuration tools.

Retiring experience

Recommended alternative

Q&A in reports

Copilot with Power BI reports

Q&A on a dashboard

Copilot standalone experience

Q&A virtual analyst in mobile app

Copilot in Power BI Mobile …