Roadmap, security CVEs, Defender XDR, Entra ID & Graph API changes from official public sources — snapshotted every 2 hours, so you also see the edits, date slips and removals Microsoft makes later.
⏰ Remediate by Nov 24, 2026 · in 12d
Spoofing · Moderate · CVSS 6.5 · Exploited in the wild. Affects: Microsoft Office LTSC, Microsoft 365 Apps.
⏰ Remediate by Oct 16, 2026 · passed 27d ago
Security Feature Bypass · Important · CVSS 8.8 · Exploited in the wild. Affects: Windows Server, Windows 10 Version, Windows 10 Version 21H2 for 32-bit Systems, Windows 10 Version 21H2 for ARM64-based Systems, Windows 10 Version 21H2 for x64-based Systems, Windows 10 Version 22H2 for 32-bit Systems.
<h2>Business Value</h2> <p>Shopify regularly retires API versions. Staying current helps prevent avoidable connection interruptions and keeps synchronization compatible with Shopify platform changes. Better operational cues and clearer timestamps help administrators find failures faster and understand whether a value came from Shopify or Business Central.</p> <h2>Details</h2> <p>Shopify releases a new API version every three months at the beginning of the quarter, and supports each version for 12 months. The updated versions might contain important changes, so it's important to uptake Shopify API versions in major releases of Business Central. Typically, new versions of APIs increase stability and security, and enable additional capabilities. Starting with this release, Shopify Connector uses the Shopify API that was released in July 2026. This update keeps the integration on a supported API version and includes security changes such as support for expiring offline access tokens for public apps, as well as functional changes, like market-driven shipping methods.</p> <blockquote> <p>[!IMPORTANT]</p> <p>The Shopify Connector released in 2026 release wave 1 (April 2026) relies on API 2026-01, which is supported until December 31, 2026. To continue to use your integration, upgrade to the latest version of Business Central before this date.</p> </blockquote> <h3>The connector now supports Shopify's expiring offline access tokens</h3> <ul> <li>Access tokens refresh automatically before their one-hour lifetime expires.</li> <li>Refresh tokens rotate and remain valid for up to 90 days.</li> <li>Existing non-expiring tokens migrate when the connector needs next authentication.</li> <li>If the refresh-token window expires, an administrator must reconnect the shop from the Shopify Shop Card.</li> </ul> <h3>Operational improvements make synchronization easier to supervise</h3> <ul> <li>A <strong>With errors</strong> view filters the Shopify Log to entries that contain errors.</li> <li>The Shopify Activities page shows <strong>Skipped Records</strong> and <strong>API Errors</strong> cues and highlights them when action is needed.</li> <li>Product and price synchronization skips invalid item unit-of-measure combinations and records the reason instead of stopping the complete synchronization. Enable logging to retain skipped-record details.</li> <li>Suffixes help you to distinguish <strong>Created At (Shopify)</strong> and <strong>Updated At (Shopify)</strong> imported from Shopify from standard audit fields present in Business Central.</li> </ul>
<p>This is being removed as a duplicate of 486820</p>
<p>You can now edit and collaborate on the presentation outline generated by Copilot in a Page before the PowerPoint deck is created. This item is no longer accurate and is being removed from the roadmap. We apologize for any inconvenience</p>
<p>Drive Copilot chat engagement for 3P content via deep citations, inline citations, side by side preview experiences.<br> Note: This roadmap item is no longer accurate and will be removed from the roadmap. We apologize for any inconvenience.</p>
<p>Access to Archive mailboxes (Main + Auxiliary) through Microsoft Graph. The goal is to give users a single, seamless Archive view, even though Archive data may physically reside across multiple auxiliary mailboxes with EWS Graph APIs getting deprecated by OCT 2026.</p>
<ol> <li>Makers can now scope their data in their agent created on custom connector data at a particular container.</li> <li>These containers will be defined during creation/updating of the custom connector.</li> </ol> <p>Note: This roadmap item is no longer accurate and will be removed from the roadmap. We apologize for any inconvenience.</p>
<ol> <li>Maker can create agents by providing 3p URL.</li> <li>Maker can provide either an item URL or a container level, for e.g. ADO ticket/ ADO area path.</li> </ol> <p>Note: This roadmap item is no longer accurate and will be removed from the roadmap. We apologize for any inconvenience.</p>
<p>The standard Dynamics 365 Business Central solution already meets many global needs. We expand that solution to meet local needs by adding capabilities that include:</p> <ul> <li>Logistics flows that manage subcontractor transfers for raw materials and components, along with warehouse handling and item tracking.</li> <li>Flexible pricing that considers the work center, item, dates, and quantity.</li> <li>Finished goods receipts with item tracking and warehouse handling from purchase orders.</li> <li>Logistics flows that manage subcontractor transfers of finished goods.</li> <li>Enhanced usability and more transparency in production processes.</li> </ul> <p><strong>Special note for Italian localizations</strong></p> <p>The Italian localization currently supports logistics for both finished goods and raw materials/components. We deprecate the existing local functionality and provide upgrade logic to facilitate migration to a new W1 solution. You decide when to start the transition by activating a feature key on the <strong>Feature Management</strong> page.</p> <p>Business Value:</p> <p>A complex industrial structure can include external vendors that handle specific tasks within the broader production process. Some companies outsource up to 75 percent of their production. Outsourcing can lead to significant cost savings or access to specialized skills and technologies that might not be available otherwise. A typical example is a company that handles research, design, quality control, and sales in-house but outsources all or large parts of the actual production.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
<p>Consolidated AI settings make it easier for makers and admins to find and manage AI capabilities for model-driven apps across two complementary surfaces.</p> <p>In Maker Studio, the <strong>Settings</strong> dialog in the model app form designer adds a new top-level <strong>Copilot and AI</strong> tab. Makers can see and adjust all available AI options for the app in one place instead of finding them scattered among all the other settings.</p> <p>In the Power Platform admin center, model-driven app AI settings are consolidated from <strong>Environment > Settings</strong> into <strong>Copilot Hub > Power Apps</strong>. This provides a central location for settings such as Generative pages, Copilot in apps, and the in-app AI skills. The in-app skill settings are organized into these groups:</p> <ul> <li><strong>Data entry:</strong> Form fill assistance.</li> <li><strong>Summary:</strong> Row summaries.</li> <li><strong>Data analysis:</strong> AI-generated charts and natural-language search and filtering.</li> </ul> <p>Labels and descriptions are aligned across Maker Studio and Copilot Hub so makers and admins can understand how the controls relate.</p> <p>As part of this consolidation, the old model-driven app AI switches under <strong>Environment > Settings</strong> will also be retired and removed.</p> <h3>Availability</h3> <table> <thead> <tr> <th>Field</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Applies to</td> <td>Model-driven apps</td> </tr> <tr> <td>Release Channel</td> <td>Weekly</td> </tr> <tr> <td>Version</td> <td>2610.3</td> </tr> <tr> <td>Feature Scope</td> <td>Admins or makers</td> </tr> </tbody> </table>
This is item is no longer accurate and we are removing it from the roadmap, we apologize for any inconvenience.
Viva Connections multi-home site management is moving from the Microsoft 365 admin center (MAC) to the SharePoint Admin Center (SPAC). Administrators will be able to create and manage multiple Home sites, configure audience targeting, manage home site priority order, and remove Home sites directly from SPAC. Existing entry points in the Microsoft 365 admin center will direct administrators to the new SPAC experience. As part of this update, legacy Viva Connections (VC) instances and draft/enabled management concepts are being deprecated as Viva Connections administration is consolidated into SharePoint Home site management. Existing VC experiences will be upgraded to full Home sites.
The Communication Compliance homepage will provide two columns that offer a quick overview of policy performance: the first column shows the number of scanned parent items in real time, giving visibility into scanning progress; the second column keeps you informed about parent items that meet policy conditions, ensuring you stay updated on potential issues requiring attention and maintaining control over communication compliance. This item is no longer accurate and is being removed from the roadmap. We apologize for the inconvenience.
We're introducing dynamic tool discovery for declarative agents in Microsoft 365 Copilot. Developers can now add, update, or retire tools on their MCP servers without republishing the agent - so end users get the latest agent capabilities immediately, with no deployment cycle in between. Support for federated Copilot connectors will be a fast follow to declarative agents at a later stage. Dynamic tool discovery is backed by Microsoft's enterprise RAI and security protections, and customers retain full control over agent deployment and availability to users and groups.
Spoken language detection is now fully automatic. Teams will automatically detect each speaker’s spoken language and update it in real time as the conversation evolves. Manual spoken language selection will no longer be available. This applies to both live captions and transcripts when Interpreter is enabled or when multilingual speech recognition is turned on in meeting options, helping deliver more accurate language recognition and a more consistent multilingual meeting experience.
Teams will automatically remove hidden metadata (EXIF) from images shared in conversations. This privacy protection helps prevent sensitive information such as photo location and device details from being shared without your knowledge.
Beginning with this feature release, Focus Areas will be associated with survey cycles and goal periods will be retired. Users will be able to select the same Focus Area across multiple cycles. The Focus Area Overview report will be filterable to groups of interest (e.g. managers only). Draft/deleted Focus Areas will no longer be included in Focus Area calculations.
These enrollment policies for iOS/iPadOS contains enrollment time grouping, improved UI, and removes automatic deployment of the Company Portal app and deprecated settings.
⏰ Act before October CY2026 · overdue
<p>Federated Copilot connectors (MCP type) currently let Microsoft 365 Copilot read data from third-party services in real time. With this update, the connector tools that create, update, and delete content in those services are unblocked in Copilot Chat, so users can complete work without leaving Copilot. Copilot acts with the user's own account and permissions at the third-party service, and every create, update, or delete action requires the user's explicit confirmation before it runs. Admins can view each connector's read and write/delete tools in the Microsoft 365 admin center and disable connectors that don't meet their organization's policies.</p>
⏰ Act before September CY2026 · overdue
<p>The multioutlet B2B web storefront introduces a unified sign-in system that allows buyers to access all their associated organizations and outlets using a single account. The storefront UI is updated to display an organization selector during sign-in and provides outlet-specific navigation and catalog views. Buyers can place, track, and manage orders for multiple outlets within a single session, with real-time visibility into order status, inventory, and account information.</p> <p>This feature supports role-based access, ensuring that users only see the organizations and outlets they are authorized to transact with. This experience is behind a feature flag that's available for administrators to update from Commerce headquarters. Administrators must configure organization and outlet relationships, assign users to their respective organizations, and activate the unified sign-in option in the storefront settings.</p> <p>The following features are available after enabling this feature:</p> <ul> <li><strong>Unified sign-in with organization selector</strong>: Enables buyers to select their organization during sign-in for multioutlet ordering and tracking.</li> <li><strong>On-account payments and credit limits</strong>: Provides real-time credit validation for organization accounts during checkout to ensure compliance and reduce payment friction.</li> <li><strong>Seller inventory visibility and Commerce Scale Unit (CSU) tools.</strong></li> <li><strong>Account header updates</strong>: Displays the organization name and linked accounts for clarity.</li> <li><strong>User management</strong>: Allows B2B organization administrators to use contacts to directly manage users from Commerce headquarters.</li> <li><strong>Multicart shopping</strong>: Enables individual contacts to manage separate carts for different outlets under one organization account.</li> <li><strong>CSU tools</strong>: Assist contact-based B2B sellers in the business partner employee role to implement real-time inventory data and efficiently accept or reject multioutlet orders.</li> </ul> <p>Business Value:</p> <p>This feature empowers business-to-business (B2B) buyers with a seamless, unified experience across multiple outlets. This feature simplifies account management by enabling a single sign-in for all organizations, reducing friction and improving efficiency. Buyers can place and track orders for multiple outlets from one storefront, thereby reducing errors. Buyers can use a single sign-in to access all their organizations, view outlet-specific catalogs, and manage orders for all their organizations in one place.</p> <p>By consolidating workflows and account management, businesses can increase productivity, reduce errors, and deliver a seamless experience that drives customer satisfaction and loyalty. The unified approach also supports faster onboarding for new outlets. For your business, this means stronger customer loyalty, higher order volumes, and streamlined operations, while delivering a modern, intuitive experience that differentiates your brand in a competitive market.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before July CY2026 · overdue
<p>You can now configure and run multiple Sales Order Agent instances in a single company. Each instance operates independently with its own mailbox, folder settings, email signature, and processing rules.</p> <p>Each agent instance tracks its own KPI metrics, such as emails received, quotes created, orders created, and time saved. The setup page is restructured to support per-instance configuration, and an upgrade path migrates existing single-instance setups to the new architecture. This change allows organizations to set up separate agents for different sales teams, product lines, or customer segments, each monitoring their own personal or shared mailbox.</p> <h3>Improved items search:</h3> <p>When a customer requests items, the agent now uses a multi-layer matching strategy:</p> <ul> <li>Exact identifier match: direct lookup by item number, vendor item number, GTIN, or cross-reference.</li> <li>Semantic attribute matching: extracts attributes from the customer's message (color, material, size) and ranks candidates by relevance using AI.</li> <li>Broader fuzzy search: falls back to a global item search when direct and attribute-based searches produce no results.</li> </ul> <h3>Message and attachment relevance:</h3> <p>The agent now validates incoming messages and attachments against a detailed relevance model before processing. Messages that fall outside the agent's responsibilities (such as offers to sell, requests for discounts, or attempts to extract internal information) are identified and filtered.</p> <p>A separate relevance check runs on attachments, ensuring that non-sales-related documents don't trigger unnecessary processing. The validation considers the full conversation history and the agent's defined scope to make accurate relevance decisions.</p> <h3>Larger attachment files with diagnostics.</h3> <p>The maximum number of pages per PDF attachment has been raised from 10 to 50, addressing customer feedback about the agent not reading larger purchase orders. A new cumulative content length limit of 150,000 characters is also enforced across all attachments in a single email (approximately 50K tokens).</p> <p>When an attachment is skipped, Business Central now stores the specific reason directly on the attachment record (page count exceeded, cumulative content length exceeded, attachment count exceeded, unsupported format, or analyze-attachments not enabled). This information is visible on the <strong>Attachments</strong> page and logged in telemetry, making it straightforward to diagnose why a particular document wasn't processed.</p> <h3>Try it out.</h3> <p>You can now create tasks for the Sales Order Agent without sending an email. From the agent's setup page, a new <strong>Try it out</strong> section lets you compose a message by selecting a sender (from your contact or customer list), entering message text, and attaching files. The agent acts like it received a real email.</p> <p>To help you get started quickly, two sample messages are included. One is a text-only message that references items from your catalog, and the other is a message with a sample purchase order attachment. The sample order is generated based on your actual item data, so the agent has realistic content to work with.</p> <p>These samples are particularly useful for first-time setup, demos, and testing agent behavior with specific scenarios without needing to send an actual email.</p> <h3>Handling of unknown senders</h3> <p>When the agent receives an email from an unregistered email address, you now have three options instead of just one:</p> <ul> <li>Create a new contact: register the sender as a new contact (existing behavior)</li> <li>Use another contact once: pick an existing contact from the contact list and link them to this specific task only, without modifying any master data. The override is stored per task message and does not affect future emails.</li> <li>Update an existing contact's email: select an existing contact and update their email address to the sender's address</li> </ul> <h3>More control over email</h3> <p>New configuration options give administrators more control over how the agent interacts with the monitored mailbox:</p> <ul> <li>Mark email as read: a new toggle to mark processed emails as read in the mailbox. This works in addition to the custom <em>Processed by Sales Order Agent</em> category, giving users a visual signal in their inbox.</li> <li>Mandatory folder selection: the agent now requires you to select a specific mailbox folder before activation. Previously this was optional and could lead to the agent monitoring an unexpected folder. If in doubt, choose <em>Inbox</em>.</li> <li>Stricter activation validation: trying to activate the agent without a mailbox folder now shows a clear error message instead of allowing activation in an ambiguous state.</li> </ul> <h3>Prompts as embedded resources.</h3> <p>The agent's AI prompts (instructions, item search logic, mail template checks, irrelevance validation) are now shipped as embedded resource files within the app extension package. This change reduces latency on first task processing and makes the prompt structure more transparent for engineering iteration.</p> <p>Business Value:</p> <p>The Sales Order Agent now handles more complex organizational structures and higher volumes with less manual intervention. You can run multiple agent instances in one company, each dedicated to a different team or shared mailbox with independent settings and performance tracking. The agent finds the right items more reliably by understanding product attributes, informal descriptions, and identifiers across multiple matching layers.<br> The agent now processes PDFs up to 50 pages (previously, the limit was 10) and clearly shows why any attachment was skipped. It also filters irrelevant messages before processing, so credits aren't consumed by marketing emails or out-of-scope inquiries. If a customer writes from an unregistered email address, you can link an existing contact to that single task without creating duplicates. You can test the agent directly from the setup page without sending a real email, reducing the time to validate your configuration.</p> <p>Enabled for:</p> <p>Enabled for end users automatically</p>
⏰ Act before July CY2026 · overdue
<p>Administrators configure team-based access for representatives through Microsoft Entra ID security groups. They link an Entra security group to a Dataverse team of type <strong>Microsoft Entra ID Security Group</strong> and assign at the team level the required security roles such as:</p> <ul> <li>Basic user</li> <li>Customer Service Representative</li> <li>Omnichannel agent</li> </ul> <p>Every member of the linked group inherits the roles automatically with no per user role assignment, including:</p> <ul> <li>Queue participation</li> <li>Presence</li> <li>Conversation handling</li> </ul> <p>When a representative belongs to more than one team, they receive the combined privileges of their teams. Existing persona-based assignments continue to work, so current configurations continue to function without changes.</p> <p>Business Value:</p> <p>Large contact centers face major challenges when they onboard and offboard service representatives at scale. Administrators must assign multiple security roles to each user individually. This approach increases effort, delays readiness, and raises the risk of access errors.</p> <p>This feature simplifies access management through Microsoft Entra security groups. Administrators assign roles to a group once. They grant or revoke access instantly by adding or removing users from the groups.</p> <p>Organizations reduce administrative burden, strengthen access control, and speed up onboarding. New service representatives receive the access they need on day one. Administrators replace thousands of repetitive tasks with a centralized, scalable model that supports growth and improves operational efficiency.</p> <p>Enabled for:</p> <p>Enabled for admins/makers/marketers automatically</p>
Added the agentMetadata resource for agent policy scoping and evaluation. Added the policyLocationAgent resource for agent data loss prevention policy locations. Added the abstract interactionParticipant resource for parties in agent interactions. Added the agentParticipant resource. Added the toolParticipant resource. Added the userParticipant resource. Added the participants property to the activityMetadata resource. Added the tenant-scoped processContent method for agent interactions. Updated tenantProtectionScopeContainer: compute to support agent evaluation scopes and agent policy locations. Updated the evaluationScope property of processContentRequest to support agent evaluation. Removed the policyLocationTool resource from the policy location model. Removed the sourceLocation property from the protectedApplicationMetadata resource.
⏰ Act before August CY2026 · overdue
<p>This feature provides the following capabilities:</p> <ul> <li>The adherence tracker includes a planning group filter that supervisors can use to scope the view to a specific planning group.</li> <li>The planning group filter works with the existing shift plan and service representative filters, so supervisors can combine filters to refine a single view.</li> <li>The tracker displays representatives based on the planning groups associated with their scheduled shifts. This behavior keeps the tracker aligned with the shift plan used to calculate adherence.</li> <li>The tracker saves each supervisor’s filter selections across sessions and opens with their previous scope.</li> <li>The tracker recalculates adherence percentages and out-of-adherence counts for the filtered scope, providing a planning group-level view of intraday adherence.</li> <li>In Copilot Service workspace, go to <strong>Workforce management</strong> > <strong>Adherence tracker</strong>.</li> </ul> <p><strong>Access and prerequisites</strong></p> <p>To use Workforce Management capabilities, an administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.</p> <p>Business Value:</p> <p>Supervising large contact centers is tough when you have to scan endless lists to find your team. Now, with planning group support, you can filter the adherence tracker to just the groups you manage. That means you spot issues faster and act right away, keeping service levels on track in real time instead of fixing problems after the fact. This feature scales for enterprise operations with hundreds of representatives and aligns with the same planning group structure you already use for forecasting, staffing, and scheduling. It saves time, reduces complexity, and helps you stay focused on what matters most: delivering consistent service.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before August CY2026 · overdue
<p>This feature provides the following capabilities:</p> <ul> <li>The adherence historical analytics report includes a planning group filter that workforce managers can use to scope results to one or more planning groups.</li> <li>The planning group filter works with the report’s existing filters, allowing managers to combine planning groups, date ranges, and other report parameters in a single view.</li> <li>The report recalculates adherence metrics for the filtered scope, providing a group-level view of adherence performance instead of a contact center-wide aggregate.</li> <li>The report associates representatives with planning groups through their scheduled shifts. This behavior keeps historical reporting aligned with the shift plans used to calculate adherence.</li> <li>Planning groups must be configured and have assigned representatives before the filter returns results.</li> <li>In Copilot Service workspace, go to <strong>Workforce management</strong>.</li> </ul> <p><strong>Access and prerequisites</strong></p> <ul> <li>To use Workforce Management capabilities, an administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.</li> </ul> <p>Business Value:</p> <p>Adherence only matters when it reflects how your work is organized. Until now, historical adherence reports didn’t account for planning groups, making it hard to see if performance dips came from a single under-supported queue or were spread across the operation.</p> <p>With planning group support, you can focus your analysis on the groups that matter and compare adherence across them for the same time period. This gives you clearer insights and helps you make smarter staffing decisions.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before August CY2026 · overdue
<p>This feature provides the following capabilities:</p> <ul> <li>When creating or editing a forecast scenario, forecasters can optionally select a planning group.</li> <li>When a planning group is selected, the <strong>Timezone</strong>, <strong>Channel</strong>, and <strong>Queue</strong> values are populated from the planning group definition and become read-only. This behavior keeps the scenario aligned with its planning group.</li> <li>When no planning group is selected, forecasters can manually edit the <strong>Timezone</strong>, <strong>Channel</strong>, and <strong>Queue</strong> values. Existing scenario creation workflows remain unchanged.</li> <li>The forecast scenario list includes a <strong>Planning group</strong> column that forecasters can use to sort and filter scenarios.</li> <li>Capacity plans created from a forecast scenario inherit the scenario’s planning group. For a capacity plan created from an uploaded file, forecasters can select the planning group manually.</li> </ul> <p><strong>Access and prerequisites</strong></p> <p>To use Workforce Management capabilities, an administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.</p> <p>Business Value:</p> <p>Contact center demand rarely aligns perfectly with a single queue. Most lines of business, sites, or skill pools rely on multiple queues and channels that share the same agents and service goals.</p> <p>Planning group support brings these queues and channels together so you can forecast them as one unit. Instead of juggling separate scenarios, you work with a single view where volume and average handle time reflect the actual demand pool your team staffs. This means you can pass accurate numbers straight to capacity planning and scheduling without extra steps. You save time, reduce errors, and measure performance at the level your business truly operates.</p> <p>If you manage dozens of queues across multiple lines of business, this feature shifts forecasting from a queue-by-queue task to planning at the scale of your entire operation.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before June CY2026 · overdue
<p>The quality evaluation skill of the Quality Assurance Agent now includes real-time coaching, enabling organizations to shift from post-interaction monitoring to in-the-moment guidance during live conversations. Service representatives receive contextual coaching nudges during live conversations based on configured quality criteria and guardrails, allowing immediate course correction and improved interaction quality.</p> <p>Organizations can:</p> <ul> <li><strong>Define policy-driven coaching triggers</strong>: Configure which quality criteria (such as compliance, empathy, script adherence, or resolution steps) initiate real-time coaching.</li> <li><strong>Provide contextual, conversation-aware nudges</strong>: Deliver coaching suggestions based on the live conversation to ensure relevance.</li> <li><strong>Control coaching triggers</strong>: Specify when coaching is triggered, such as for missed behaviors, risk signals, or guideline violations.</li> <li><strong>Manage coaching frequency</strong>: Set frequency limits and suppression rules to prevent over-intervention.</li> <li><strong>Enforce boundaries for sensitive scenarios</strong>: Apply stricter or mandatory guidance for cases such as compliance requirements or escalations.</li> </ul> <p>Business Value:</p> <p>Shift your quality assurance approach from passive evaluation to real-time coaching that makes an immediate difference in customer interactions. With enhanced real-time guidance, you can move beyond monitoring and give your team the support they need to adjust on the spot, improve conversations, and maintain quality and compliance every time.</p> <p>Enabled for:</p> <p>Enabled for admins/makers/marketers automatically</p>
⏰ Act before July CY2026 · overdue
<p>Shopify expanded its B2B capabilities to all plans, and the Shopify Connector for Business Central is updated accordingly. Core B2B features that previously required a Shopify Plus subscription now work on Basic, Grow, and Advanced plans.</p> <p>The following capabilities are available on all Shopify plans:</p> <ul> <li><strong>Company sync</strong>: Import Shopify B2B companies and company locations and map them to customers in Business Central.</li> <li><strong>B2B order processing</strong>: When a B2B order arrives, the connector identifies the company and resolves the correct bill-to and ship-to customer based on the company location.</li> <li><strong>Market catalogs</strong>: Assign catalogs to B2B markets for price synchronization. Basic, Grow, and Advanced plans support up to three active market catalog assignments (unlimited on Plus).</li> </ul> <p>The following features require Advanced or Plus plans:</p> <ul> <li><strong>Direct company catalogs</strong>: Assign catalogs to specific companies or company locations for customer-level pricing. The <strong>B2B Catalogs</strong> page and the <strong>Auto Create B2B Catalog</strong> toggle are only available in the Advanced and Plus plans.</li> <li><strong>Staff member mapping</strong>: Import Shopify staff members and map them to Business Central salespeople.</li> </ul> <p>If you're already using Shopify, to get the updated B2B availability, you must update the plan information for the connector. An easy way to do that is to turn off the Shopify connector and then turn it on again. To do that, open the <strong>Shopify Shop Card</strong> page, turn off the <strong>Enabled</strong> toggle, and then turn it back on.</p> <p>Learn more at <a href="https://learn.microsoft.com/en-us/dynamics365/business-central/shopify/synchronize-customers">Synchronize customers and companies</a>.</p> <p>Business Value:</p> <p>This change removes a key barrier for merchants who sell wholesale through Shopify but don't use the Plus plan. Market catalogs, payment terms, and B2B order processing are available on all plans, so more businesses can manage their wholesale and direct-to-consumer operations from a single connected platform.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before August CY2026 · overdue
<p>Business Central adds support for e-invoicing and e‑reporting in France, following the DGFiP five‑corner model. Microsoft doesn't operate as a certified Partner Dematerialization Platform (PDP); instead, companies can use existing E‑Document connectors to exchange invoices and lifecycle messages through certified PDP providers. The localization app enables two compliant formats: <strong>Peppol BIS3</strong> (XML) and <strong>Factur‑X</strong> (PDF/A‑3 with embedded XML).</p> <p>The feature supports sending and receiving structured e‑invoices for sales and purchase processes, including all mandatory lifecycle statuses. Companies will use the standard <strong>E-Document</strong> module with the localization app for setup, where they can select one of the supported formats: Peppol BIS3 and Factur-X. Formats and integration services can be configured by running the <strong>E-Document Service</strong> page. Business Central also generates <strong>Transaction E‑Reporting</strong> for operations where structured invoices are not required but are required to be reported to French authorities in specific periods (monthly or quarterly).</p> <p>This functionality ensures that Business Central meets French e‑invoicing and CTC obligations effective September 2026, supporting invoice lifecycle traceability, and simplifying reporting obligations.</p> <p>Business Value:</p> <p>French e-invoicing and e-reporting mandates will become mandatory for all VAT-registered businesses from September 2026. This feature helps your company maintain compliance with DGFiP regulations, avoid penalties, and streamline invoice exchange through certified PDPs. By supporting Peppol BIS3 and Factur-X formats, you can automate invoice processing, enhance interoperability, and reduce manual effort, all while fulfilling legal requirements for B2B transactions and real-time reporting.</p> <p>Enabled for:</p> <p>Enabled for end users automatically</p>
⏰ Act before June CY2026 · overdue
<p>This feature enhancement extends the standard credit management framework to all Commerce orders across channels, ensuring the consistent application of credit policies between Commerce and Supply Chain Management. During order fulfillment, Commerce channels including call center and POS adhere to defined credit management blocking rules to determine whether an order should be placed on credit hold for review. For order capture scenarios, POS and Commerce e-commerce continue to rely on the existing <strong>Check credit limit on sales order</strong> configuration in credit and collections parameters to evaluate whether a credit limit check should be performed at order placement.</p> <p>To use these capabilities, store administrators must enable a new <strong>Enable credit management for Commerce orders</strong> feature flag in the Commerce headquarters <strong>Feature management</strong> workspace.</p> <p>Two exceptions to standard credit limit validation remain in place:</p> <ul> <li>Cash-and-carry transactions paid on credit continue to be blocked when the customer’s available credit is insufficient, ensuring that on‑account purchases can't bypass credit policies.</li> <li>Customer orders using a carry-out mode of delivery continue to be marked as <strong>Exclude from credit management</strong>, because these orders are partially invoiced immediately when the customer pays for items they carry out at the point of sale.</li> </ul> <p>This feature enhancement ensures unified and predictable credit governance across all Commerce channels, while respecting scenarios that require operational exceptions.</p> <p>Business Value:</p> <p>Credit limit management is essential for business-to-business (B2B) organizations because most transactions occur on accounts, often involving large orders, long fulfillment cycles, and repeat purchasing. By enforcing well‑defined credit limits and blocking rules, your organization can control financial risk, prevent bad debt, and maintain healthy cash flow, ensuring that open orders, uninvoiced orders, and outstanding balances are all factored into a buyer’s available credit.</p> <p>Before this feature enhancement, unlike Supply Chain Management orders, Commerce orders didn't follow the standard credit management capabilities. This resulted in different order processing flows that required customization to make order processing consistent.</p> <p>This feature ensures consistent credit policies for customers using both Supply Chain Management and Commerce orders, reducing operational complexity and eliminating costly customizations.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before June CY2026 · overdue
<p>In the current release wave, we are introducing the following regulatory reporting enhancements:</p> <p><strong>Performance improvements for Audit File Financial (XAF) – Netherlands</strong></p> <p>Dutch customers can generate the mandatory XAF export significantly faster, even for large data volumes.</p> <p>This enhancement uses optimized data storage and the latest XAF 4.0 format to reduce processing time and system load when producing audit files. It ensures compliance with the Dutch Tax Administration’s newest digital audit requirements by supporting XAF 4.0, which replaces the legacy XAF 3.2 standard.</p> <p>This performance enhancement is achieved through two key improvements:</p> <ul> <li><p><strong>Leveraging the new <a href="https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/financial-dimension-set-new">General ledger dimension set balance calculation</a></strong>: The Audit File Financial report now takes advantage of the <strong>Performance enhancement for general ledger dimension set balance calculation</strong> feature in Dynamics 365 Finance. When this feature is enabled, the system precalculates and continuously updates ledger balances for defined financial dimension sets in the background (through a process automation job that runs every few minutes).</p> <p>Reports that use financial dimension sets (like the XAF report) can then pull data from these preaggregated balances instead of computing everything from scratch. This means the Audit File generation runs much more efficiently, data is stored in optimized tables using less space, and the trial balance figures are readily available for reporting. As a result, the XAF output can be produced quickly, even if the transactional data volume is very large, since calculations have been done ahead of time.</p> </li> <li><p><strong>Adopting the latest Audit File implementation best practices</strong>: The feature updates the XAF generation to use the latest standard methods and format. It introduces a new Electronic Reporting (ER) model mapping configuration for XAF 4.0 optimized for that format. By using the ER framework, the solution follows Microsoft’s best practices for regulatory reporting, which improves maintainability and performance.</p> </li> </ul> <p>Together, these improvements mean that a Dutch legal entity can generate its XML Audit File Financial quickly and reliably. After setting up the feature (ensuring that financial dimension sets are defined and balance tracking is enabled for them) and importing the latest XAF 4.0 ER configurations, you run the Audit File Financial process as before. The report completes faster and the resulting XML complies with XAF 4.0 requirements (with fields like the RGS codes for each account as per the latest specification).</p> <p>By following the standard setup (such as associating main accounts with RGS codes in a consolidation account group per the documentation) and enabling this feature, organizations ensure that Audit File generation is not only compliant but also optimized for performance. This is especially beneficial at month-end or year-end, when time is critical–the audit file can be produced with minimal delay, allowing finance departments to confidently meet Dutch statutory obligations with improved efficiency and accuracy.</p> <p>Business Value:</p> <p>Dutch organizations can produce the Audit File Financial (XAF) export faster and more reliably with XAF 4.0 support. By preaggregating ledger balances in the background, the system reduces the time and load required at reporting time, helping your finance team stay compliant with Dutch Tax Administration requirements without delays.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before August CY2026 · overdue
<p>This feature introduces email review policy and a <strong>Known Senders</strong> list page to give accounts payable teams more control over which incoming emails require human approval before the Payables Agent processes them.</p> <p>A new <strong>Email review</strong> field in the Payables Agent setup lets administrators choose when incoming emails require human approval. The following options are available:</p> <ul> <li>Always: Every email requires approval, regardless of the sender.</li> <li>Never: No emails require approval.</li> <li>Only if untrusted (recommended): Only emails from senders who aren't on the list of known senders require review. This is the recommended setting for most organizations.</li> </ul> <p>Administrators must explicitly select an option before they start to monitor the email inbox. To ensure that they make an active decision, a default isn't preselected for the field. Every known sender is subject to a setting that sets the review policy for the specific sender.</p> <p>When you set the email review policy to <strong>Manage per sender</strong>, the agent evaluates incoming emails in the following order:</p> <ul> <li>Invoice is uploaded and not received via email: No review required.</li> <li>Email subfolder is configured: All emails in the monitored subfolder are treated as trusted. No review required.</li> <li>Sender is on the Known Senders list: Action depends on the configured value (Ask, Approve, or Reject).</li> <li>Internal sender (same organization, not on the list): No review required. Internal detection uses email authentication headers (planned to be available in 2026 wave 2, version 29.0.).</li> </ul> <p>Administrators can maintain a list of known senders, each with a configured policy:</p> <ul> <li>Ask: The email requires human approval.</li> <li>Approve: The agent processes the invoice without review.</li> <li>Reject: The sender is blocked and the attachment isn't processed.</li> </ul> <p>To build the list organically, after you review an email and want to continue, the sender is added automatically to the list of known senders, provided that the <strong>Manage per sender</strong> policy is active. Security telemetry is logged for each auto-addition.</p> <p>This feature is available from the August minor release of 2026 release wave 1.</p> <p>Business Value:</p> <p>Payables Agent processes vendor invoices received by email, but today every incoming email requires supervisor approval before the agent can act on it, unless email review is disabled entirely. This creates friction for accounts payable teams who repeatedly receive invoices from the same vendors. They must manually approve each email, even from senders they already trust. The Known Senders feature lets businesses define which senders the agent can process automatically, reducing manual intervention while maintaining control over unknown or unverified sources. With this capability, organizations can safely default email review to off, moving closer to fully autonomous invoice processing.</p> <p>Enabled for:</p> <p>Enabled for end users automatically</p>
⏰ Act before October CY2026 · overdue
<p>Supervisors can create volume spike alerts that compare real-time conversation volume with the forecast linked to a shift plan. When volume remains above forecast for the configured number of intervals, selected recipients receive an in-app notification.</p> <p>The capability includes the following features:</p> <ul> <li>Administrators can enable workforce alerts in Copilot Service admin center by going to <strong>Workforce management</strong> > <strong>Intraday management</strong> > <strong>Workforce alerts</strong>.</li> <li>Supervisors can create and manage alerts from Workforce alerts in the Copilot Service workspace site map.</li> <li>Each alert references a shift plan and monitors the queues associated with its linked capacity plan.</li> <li>Supervisors can specify the percentage by which actual volume must exceed forecast volume.</li> <li>Supervisors can specify the number of consecutive intervals during which the deviation must continue before an alert is raised. The forecast determines whether an interval is 15, 30, or 60 minutes.</li> <li>Supervisors can set an expiration date to limit an alert to a campaign, season, or known event.</li> <li>Supervisors can select one or more notification recipients for each alert.</li> <li>Active alerts are evaluated on a recurring schedule. Notifications are sent when the configured threshold and duration are met.</li> <li>Recipients can select a notification to open the alert details. The details include the queue and alert name, detection time, current and forecast volumes, spike percentage, and an interval-by-interval breakdown.</li> </ul> <h3>Access and prerequisites</h3> <ul> <li>An administrator must install the Workforce Management for Customer Service package from Power Platform admin center.</li> <li>Forecasting and scheduling must be configured.</li> <li>The selected shift plan must have a linked capacity plan and forecast.</li> <li>Real-time conversation data must be available for the monitored queues.</li> </ul> <p>Business Value:</p> <p>Contact centers plan staffing based on forecasted demand, but actual demand can change quickly. When conversation volume rises significantly above forecast, queues can grow and service levels can decline before supervisors have time to respond.</p> <p>Workforce alerts help supervisors identify unusual intraday volume changes without continuously monitoring a dashboard. Supervisors define the deviation and duration that represent a volume spike and select who should be notified when those conditions are met.</p> <p>The notification provides information about the spike, including how far actual volume is above forecast and whether the deviation is continuing. Supervisors can use this information to decide whether to shift capacity, offer overtime, or defer offline work while these actions can still help protect the customer experience.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before October CY2026 · overdue
<p>The Customer Data Platform panel in Store Commerce has been rebuilt using React, replacing the legacy implementation with a modern, responsive layout optimized for both desktop and mobile form factors.</p> <p><strong>What's new in the modernized CDP panel</strong></p> <ul> <li><strong>Mobile-optimized layout</strong>: The panel uses a vertical scroll pattern that works naturally on tablets and handheld devices used by store associates on the floor.</li> <li><strong>Customer summary at a glance</strong>: Loyalty points, purchase frequency, average spend, and contact details are prominently displayed at the top of the panel.</li> <li><strong>Transaction history inline</strong>: Associates can view recent purchases, including items bought, channel, and location, without leaving the current context.</li> <li><strong>Buy-again workflow</strong>: Frequently purchased items are surfaced with a direct add-to-sale action, enabling associates to quickly rebuild a customer's basket.</li> <li><strong>Customer timeline</strong>: Chronological view of customer interactions, notes, and activities gives associates context for the current conversation.</li> <li><strong>Product recommendations</strong>: Curated or engine-driven recommendations are shown inline to support upsell and cross-sell during the interaction.</li> </ul> <p><strong>Streamlined customer creation and editing</strong></p> <ul> <li><strong>Single-save workflow</strong>: Associates can create a new customer record with both customer information and primary address captured in one form, saved in a single action. This reduces the number of clicks and screen transitions required compared to the legacy multistep flow.</li> <li><strong>Inline address validation</strong>: Mandatory address fields are validated at the point of entry before the record is saved to help ensure compliance with fiscal requirements for markets where a complete primary address is legally required on customer records. This validation is opt-in and configured at the channel level.</li> <li><strong>Unified edit experience</strong>: Editing an existing customer's details and address follows the same consolidated pattern to keep associates in a single context rather than navigating between separate management screens.</li> </ul> <p><strong>Custom attributes tab</strong></p> <p>Retailers who capture custom attribute data on customer records can now find that information directly within the CDP panel via a dedicated <strong>Custom information</strong> tab. The tab is displayed conditionally and appears only when custom attributes have been configured for the customer record to keep the panel clean and uncluttered for retailers who do not use custom attributes. This allows retailers to extend the clienteling experience with their own data, such as membership tiers, fit preferences, loyalty program details, or any other retailer-defined fields, without requiring associates to leave the panel or open a separate management screen.</p> <p><strong>How associates access the feature</strong></p> <p>The CDP panel is accessible from two entry points in Store Commerce:</p> <ol> <li><strong>Customer search</strong>: When an associate searches for and selects a customer, the modernized CDP panel opens directly.</li> <li><strong>Active transaction</strong>: Associates can open the CDP panel from within an in-progress transaction to view customer context without interrupting the sale.</li> </ol> <p><strong>Enabling the feature</strong></p> <p>This feature is enabled via <strong>Feature management</strong> in Dynamics 365 Commerce headquarters. Once the feature flag is turned on, the modernized CDP panel is automatically available in Store Commerce for all users without additional configuration at the register or device level.</p> <p><strong>Applies to</strong>: Point of sale (Store Commerce)</p> <p>Business Value:</p> <p>Store associates spend valuable selling time navigating a cluttered, legacy customer detail page that wasn't designed for mobile or fast-paced retail floors. Critical information, such as purchase history, loyalty points, preferences, and product recommendations, is buried across multiple tabs and screens, slowing assisted selling and reducing the quality of in-store customer interactions.</p> <p>The modernized Customer Data Platform (CDP) panel in Store Commerce delivers a lightweight, mobile-optimized clienteling experience designed for the way associates actually work. Key customer signals, such as spending summaries, recent transactions, buy-again suggestions, and a full customer timeline, are now surfaced inline without requiring associates to navigate away from the transaction. This means faster, more personalized customer conversations, higher basket value through timely product recommendations, and reduced training burden for new associates who can now act on customer context at a glance.</p> <p>Creating and editing customer records has also historically required associates to navigate multiple screens and save operations, increasing the risk of incomplete records and slowing down queue-sensitive moments on the shop floor. For retailers operating in regions with fiscal requirements, where a validated primary address is mandatory for customer records, the legacy workflow offered no inline guardrails, leading to compliance gaps and post-transaction corrections.</p> <p>The modernized CDP panel addresses this by consolidating customer creation and editing into a streamlined, single-save workflow. Associates can capture customer information and primary address in one form and save the complete record in a single action that reduces clicks and eliminates the back-and-forth between separate screens. Mandatory address field validation is enforced inline at the point of entry, ensuring compliance with fiscal requirements before the record is committed and removing the need for manual follow-up or administrative correction.</p> <p>For retailers investing in omnichannel clienteling, this feature provides a modern, compliant foundation to deliver consistent, data-informed customer engagement at the point of sale.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
⏰ Act before October CY2026 · overdue
<p>The intraday performance report provides supervisors with an interval-level view of performance against the forecast. In Copilot Service workspace, go to <strong>Workforce management</strong> to access the report.</p> <ul> <li>Compare forecast and actual contact volume and average handle time. Variances appear as values and percentages, making outliers easier to identify.</li> <li>Compare forecast, required, and scheduled staffing levels to identify understaffed and overstaffed intervals.</li> <li>Review service level, occupancy, and schedule adherence alongside volume and staffing data in a single report.</li> <li>View data in 15-, 30-, or 60-minute intervals to match how your organization manages intraday performance.</li> <li>Filter the report by planning group and shift plan to focus on the areas you manage.</li> </ul> <p><strong>Access and prerequisites</strong></p> <p>To use Workforce Management capabilities, an administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.</p> <p>Business Value:</p> <p>Contact center forecasts and schedules are built days or weeks in advance, but demand rarely arrives exactly as planned. When volume spikes, handle times run long, or agents are absent, supervisors often don't see the gap until service levels have already slipped and the interval is gone.</p> <p>The intraday performance report closes that gap by showing plan versus actual as the day unfolds. Supervisors can see which intervals are under- or over-staffed and act while there's still time by moving agents between queues, adjusting break and training schedules, or opening overtime only where it's genuinely needed. That protects service level and abandonment targets on the days that matter most, and it curbs the two costs that quietly compound in every contact center: paying for idle capacity in over-forecasted intervals and paying premium rates to recover from under-forecasted ones.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>
Removed the fileTooLarge member from the evaluationErrorType enumeration. Removed the archiveSizeTooLarge member from the evaluationErrorType enumeration. Removed the textExceedsMceThreshold member from the evaluationErrorType enumeration. Removed the partiallyScannedArchive member from the evaluationErrorType enumeration. Removed the partialImageExtraction member from the evaluationErrorType enumeration. Removed the imageOcrPartialResult member from the evaluationErrorType enumeration. Removed the ocrProcessingFailure member from the evaluationErrorType enumeration. Removed the ocrQuotaExhausted member from the evaluationErrorType enumeration. Removed the classificationServiceError member from the evaluationErrorType enumeration. Removed the sitExtractionFailure member from the evaluationErrorType enumeration. Removed the textExtractionFailure member from the evaluationErrorType enumeration. Removed the archiveTextExtractionError member from the evaluationErrorType enumeration. Added the contentTooLarge member to the evaluationErrorType enumeration. Added the partiallyScanned member to the evaluationErrorType enumeration. Added the unscannable member to the evaluationErrorType enumeration. Added the billingNotSetup member to the evaluationErrorType enumeration. Added the authenticationOrAuthorizationFailed member to the evaluationErrorType enumeration. Removed the errorMessage property from the evaluationErrorDetail resource.
Added the backupPolicyDeleted member to the activityLogOperationType enumeration. Added the restoreJobType property to the restoreTaskActivityLog resource. Removed the tags property from the restoreTaskActivityLog resource.
Added the accessDriftReportResourceType enumeration type. Removed the connectedApp member from the accessDriftReportResourceType enumeration. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the accessDriftResourceType enumeration type. Added the accessDriftSource enumeration type. Added the accessDriftType enumeration type. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the applicationDriftResourceInfo resource. Added the driftAccessPackageInfo resource. Added the driftCounts resource. Added the driftResourceInfo resource. Added the groupDriftResourceInfo resource. Added the accessDriftDetail resource. Removed the accessPackageIdentifier property from the accessDriftDetail resource. Removed the accessPackageName property from the accessDriftDetail resource. Removed the assignedRole property from the accessDriftDetail resource. Removed the catalogIdentifier property from the accessDriftDetail resource. Added the driftSource property to the accessDriftDetail resource. Removed the expectedRole property from the accessDriftDetail resource. Removed the identityIdentifier property from the accessDriftDetail resource. Removed the identityPrincipalName property from the accessDriftDetail resource. Added the resource property to the accessDriftDetail resource. Removed the resourceId property from the accessDriftDetail resource. Removed the resourceName property from the accessDriftDetail resource. Removed the resourceType property from the accessDriftDetail resource. Removed the userDisplayName property from the accessDriftDetail resource. Added the identities relationship to the accessDriftDetail resource. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the accessDriftReport resource. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the accessDriftSummary resource. Added the id resource. Removed the resourceId resource. Removed the assignmentsWithDrift property from the accessDriftSummary resource. Removed the catalogIdentifier property from the accessDriftSummary resource. Added the driftCounts property to the accessDriftSummary resource. Added the driftSource property to the accessDriftSummary resource. Added the id property to the accessDriftSummary resource. Removed the missingAccessCount property from the accessDriftSummary resource. Added the resource property to the accessDriftSummary resource. Removed the resourceId property from the accessDriftSummary resource. Removed the resourceName property from the accessDriftSummary resource. Removed the resourceType property from the accessDriftSummary resource. Removed the unauthorizedAccessCount property from the accessDriftSummary resource. Added the details relationship to the accessDriftSummary resource. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the driftIdentityInfo resource. Added the entraAccessDriftDetail resource. Added the entraDriftIdentityInfo resource. Added the accessDriftReport relationship to the insights resource. Added the accessDriftReport resource. Removed the accessDriftReport resource. Added the accessDriftSummary relationship to the insights resource. Added the accessDriftSummary resource. Removed the accessDriftSummary resource. Added the localDriftIdentityInfo resource. Added the downloadFile method to the accessDriftReport resource. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource. Added the generateDownloadUri method to the accessDriftReport resource. Added the Org.OData.Core.V1.Revisions resource. Removed the Org.OData.Core.V1.Revisions resource.
⏰ Act before October CY2026 · overdue
<p>B2B users, including internal guest users and external users, will be able to register and sign in with passkeys issued by a resource tenant to meet that tenant's multifactor authentication (MFA) requirements. Today, passkeys are supported for member users in their home tenant. With this update, B2B users can register a resource tenant passkey from the resource tenant's My Security Info page, or in-line during a proof-up prompt or passkey registration campaign, and then use it to satisfy the resource tenant's MFA requirements. This change is on by default. B2B users already in scope for passkeys in your Authentication methods policy will be enabled automatically. No action is required to turn it on. If you want to review or adjust who's affected, update your Authentication methods policy, passkey registration campaign, Conditional Access policies, and user scoping before rollout.</p>
<p>Align event registrations with the way your organization manages customer data. By supporting lead-based registration journeys and existing matching rules, you can avoid unnecessary Contact creation, improve data quality, and ensure event attendees follow the same lead management process used across your business.</p> <ul> <li>Configure event registration forms to create or update Contacts, Leads, or both Leads and Contacts </li> <li>Apply existing matching, deduplication, and update rules to event registrations for more consistent and accurate customer data.</li> <li>Register attendees without requiring a Contact record, enabling lead-only registration scenarios and sales-driven qualification processes.</li> </ul>
<p>Desktop flows will support direct triggers, enabling automations to start in response to supported events without requiring an intermediary cloud flow. This simplifies automation design and reduces the effort required to connect desktop flows to business processes.</p>
<p>Power Automate will support Delinea Secret Server as an external credential provider for desktop flows. Organizations can securely use credentials managed in Delinea for machine sign-in and credential retrieval during attended and unattended automation.</p>
<ul> <li>Deduplicates recipients by contact point, so each phone number or custom channel address gets the message once per send.</li> <li>Eliminates manual post-send clean-up, wasted messaging spend and the customer annoyance of duplicate texts.</li> <li>Brings SMS and custom channels to parity with email's built-in deduplication.</li> </ul>
<p>Copilot Chat in Outlook on iOS and Android is getting updated! You'll notice smoother animations, improved strings, and some small changes to the header, such as the new/temporary chat button being moved behind the ... button.</p>
<p>Adding easy access to top sites in Edge search bar on desktop. Users can add, edit, remove, or hide top sites. Admins can control available to this feature using the NewTabPageManagedQuickLinks and NewTabPageQuickLinksEnabled policies.</p>
<p>In learning activities, students can rehearse presentations, receive feedback on their delivery, and practice again with targeted suggestions to improve clarity and confidence.</p> <p>#education</p>
<p>The write to business rules engine configuration experience introduces an option to submit only records that have successfully passed Account structure validation. When enabled, Business Performance Planning filters the writeback dataset and submits only records marked as valid by account structure validation to the business rules engine writeback process. Records that have not passed validation are excluded from the submission so users can review and correct them before attempting to write them to Dynamics 365 Finance.</p>
<p>Segment templates help you build audiences without recreating queries for each campaign. Choose a built-in template for common scenarios such as event attendance or email engagement, or save your own segment query as a reusable custom template. Add placeholders with hint text to guide marketers through entering campaign-specific values, reducing repetitive setup while keeping audience criteria consistent.</p>
<p>Bring Minecraft Education to every classroom with AI-powered tools that match curriculum goals to Build Challenges, blend lessons with project-based learning, launch directly from Learning Zone, and give you full visibility into participation, completion, and student understanding.</p> <p>#education</p>
<p>Cross-Tenant Orchestrated Migration for User Data Migration (UDM) and Shared Data Migration (SDM) allows customers to move their Microsoft 365 data from one Microsoft tenant to another. UDM includes the ability to move user mailboxes, OneDrive accounts, Teams chats, and Teams meetings. SDM includes the ability to move M365 Groups, SharePoint Sites, Group Mailboxes, and teams and channels.</p>
<p>Organizations managing high volumes of project transactions need to retain historical cost data without allowing years of completed transactions to continually increase the volume of active operational data. This capability enables organizations to archive processed project staging table cost actuals for long-term retention while preserving access to historical records when needed.<br> <br> Administrators can archive eligible project cost actuals for selected legal entities and date ranges using the Archive with Dataverse long-term retention workspace. The archive process moves eligible cost actuals and related transaction records to long-term storage, while providing visibility into job status and progress and continued access to archived records after the process completes.<br> <br> This capability helps organizations manage growing project transaction volumes while retaining the historical cost information required for financial history, audit, and business needs. It is available for Dynamics 365 Project Operations deployments that work with other Dynamics 365 ERP applications and requires Archive with Dataverse long-term retention.</p>
<p>Update Repair helps admins identify Windows devices with Microsoft 365 Apps that are out of date or experiencing update issues. In the Microsoft 365 Apps admin center, admins can review device status and recommended actions, remotely start Online Repair for eligible devices, and follow manual remediation guidance for devices that need attention. Repair reinstalls Microsoft 365 Apps using the latest available build for the device’s configured update channel.</p>
<p>Improve accessibility by adding alternate text to images shared in Teams from OneDrive and SharePoint, helping users better understand visual content</p>
<p>Users can now use the Teams Meet app to discover events across their organization, track what important events are upcoming, and plan and organize their own professional events. With this release, Meet app will be renamed to Events app.</p>
<p>Meeting organizers will only see automatic recording and transcription choices in Meeting Options that are allowed by their organization's existing meeting policies. A new Record only choice lets organizers automatically start recording without starting transcription. Depending on the organizer's policies, available choices can include Record and transcribe, Transcribe only, Record only, and Off. When both recording and transcription are disabled by policy, the automatic setting is not shown.</p>
<p>Users in Gov clouds can now report suspicious messages and external users within Teams. Reports are surfaced in the Teams admin center, giving admins greater visibility into potentially malicious activity and enabling them to investigate and take appropriate action. By incorporating end-user reports as an additional security signal, this capability helps organizations identify and respond more quickly to phishing, impersonation, spam, and other messaging threats.</p>
<p>This release follows the availability of organization prompts, providing admins the ability to upload custom prompts for their organization in the Copilot app home screen. Now, admins can delegate organization prompt publishing to users, AAD security groups, and distribution groups. These delegated users and groups will be able to create, edit and delete organization prompts at the tenant level through the Prompt Lab, without having to access the Microsoft 365 Admin Center. Admins can continue to monitor and provide oversight through the current experience in the Microsoft 365 Admin Center.</p>
<p>Improving permission checks when users access the Microsoft Purview portal. Enhanced audit logs will provide clearer visibility into role and scoped-role access decisions, helping administrators troubleshoot access issues and monitor authorization outcomes.</p>
<p>Microsoft Teams browser app users will be able to pop out calls into a simplified call window that stays available while they navigate away from, hide, or minimize the tab or progressive web app (PWA) hosting the call. This helps users multitask and collaborate more easily during calls.</p>
<p>The sharing panel in today’s meetings is the default place for content discoverability and sharing. New sharing panel UI is crafted with intent of modernising and simplifying default tasks such as window sharing, but also for easier discovery of sharing options and more discoverable file sharing.</p>
<p>This is being removed as a duplicate of 486820</p>
Remote Code Execution · Important · CVSS 8.8. Affects: Microsoft Office LTSC, Microsoft 365 Apps, Microsoft Office LTSC for Mac, Microsoft Office 365 for Mac.
<p>Available for core and integrated.<br> Currently, project invoices include transactions based on the invoice date, which can make it difficult to prepare invoices in advance when additional transactions are expected before the end of the billing period.</p> <p>With this feature, you can use the Accounting date as the transaction cutoff date for an invoice. When the Accounting date is later than the invoice date, you can include eligible future-dated transactions through the Accounting date on the invoice.</p> <p>This capability helps billing teams prepare invoices ahead of time while ensuring that transactions through the intended billing cutoff date can be included. The Accounting date also determines the accounting period in which the resulting billed transactions are recorded.</p>
<p>Microsoft Edge for Business is expanding its existing Data Loss Prevention Enterprise Connector capabilities. Administrators will be able to configure more consistent enforcement across download, upload, paste, and print workflows. Additional controls include required bypass justification and administrator-defined guidance.</p>
<p>Teams administrators can use meeting policies to control who can start recording and transcription, helping organizations apply consistent meeting settings. Administrators can restrict these permissions to organizers and co-organizers or extend them to presenters. They can also determine whether meeting organizers can modify these settings or whether they are enforced by policy.</p>
<p>Calling representative and Supervisor leads can view real-time call queue metrics directly from the Queues app on Mobile, giving them greater visibility into current queue activity and performance while on the go. Users can quickly understand the state of their queues, monitor key operational metrics, and make more informed decisions about their availability and queue participation without needing to switch to desktop.</p>
<p>You'll be able to see how much storage your recoverable items are using in Outlook. This gives you a clearer picture of your storage usage before you reach a limit. You can use this information to make more informed decisions about managing your mailbox. #newoutlookforwindows</p>
<p>You'll be able to expand or collapse all accounts at once in Outlook's folder pane. You won't need to expand or collapse each account individually. This makes it easier to navigate multiple accounts or keep your folder pane compact. #newoutlookforwindows</p>
<p>Outlook will remember whether your online archive is expanded or collapsed when you return. Outlook on the web and the new Outlook for Windows will each keep their own saved state. This saves you from repeatedly expanding or collapsing your archive as you navigate your mailbox. #newoutlookforwindows</p>
Nothing matches your filters.