Breaking changes and API deprecations that may need admin or developer action.
LaunchedDynamics 365 Commerce
⏰ 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>
LaunchedMicrosoft Copilot (Microsoft 365)Dynamics 365 Business Central
⏰ 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>
LaunchedDynamics 365 Contact Center
⏰ 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>
LaunchedDynamics 365 Customer Service
⏰ 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>
LaunchedDynamics 365 Customer Service
⏰ 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>
LaunchedDynamics 365 Customer Service
⏰ 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>
LaunchedDynamics 365 Contact Center
⏰ 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>
LaunchedDynamics 365 Business Central
⏰ 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>
LaunchedDynamics 365 Business Central
⏰ 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>
LaunchedDynamics 365 Commerce
⏰ 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>
LaunchedDynamics 365 Finance
⏰ 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>
LaunchedDynamics 365 Business Central
⏰ 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>
In developmentDynamics 365 Customer Service
⏰ 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>
In developmentDynamics 365 Commerce
⏰ 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>
In developmentDynamics 365 Customer Service
⏰ 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>
In developmentMicrosoft Entra
⏰ 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>
LaunchedDynamics 365 Business Central
⏰ Act before October CY2026 · overdue
<p>"Add default method bodies to AL interfaces so existing implementors continue working, then use RequiredPending and analyzer rules to introduce required methods safely.</p>
<p>Business value: Extension publishers can add behavior to an interface without immediately requiring every implementing extension to change. Default methods provide a compatible implementation, while the new transition attribute and AppSourceCop rules support a managed path toward making a method mandatory in a future version. This reduces disruptive interface upgrades and gives dependent developers time to adopt new contracts."</p>
LaunchedDynamics 365 Business Central
⏰ Act before October CY2026 · overdue
<h2>Business Value</h2>
<p>Direct transfers move inventory between locations without using an in-transit location. You can use this simpler transfer method when the source location requires outbound warehouse handling, while preserving the picking and shipment controls configured for that location.</p>
<h2>Details</h2>
<p>Previously, one setting on the <strong>Inventory Setup</strong> page controlled how Business Central posted all direct transfers. You can now choose a posting method for each transfer route, so different routes can post separate transfer shipment and receipt documents together or create one posted direct transfer document.</p>
<p>Set <strong>Default Direct Transfer Posting</strong> on the <strong>Inventory Setup</strong> page to define the company-wide default. On the <strong>Transfer Routes</strong> page, set <strong>Direct Transfer Posting</strong> for routes that need a different method. The transfer order uses the route setting when one is specified and otherwise uses the Inventory Setup default. You can change <strong>Direct Transfer Posting</strong> on an open <strong>Transfer Order</strong> when needed.</p>
<p>The posting methods work as follows:</p>
<ul>
<li><strong>Shipment and Receipt</strong> posts a transfer shipment and transfer receipt together. <strong>Qty. to Ship</strong> must equal <strong>Qty. to Receive</strong>. When you post from a warehouse shipment, partial posting is supported.</li>
<li><strong>Direct Transfer</strong> posts one <strong>Posted Direct Transfer</strong> document. Business Central posts the full transfer-line quantity without creating separate transfer shipment and receipt documents.</li>
</ul>
<p>Direct transfers support the following outbound warehouse scenarios:</p>
<table>
<thead>
<tr>
<th>Transfer-from location setup</th>
<th>How you complete the transfer</th>
</tr>
</thead>
<tbody>
<tr>
<td>No warehouse requirements</td>
<td>Post from the <strong>Transfer Order</strong>.</td>
</tr>
<tr>
<td><strong>Require Pick</strong> without <strong>Require Shipment</strong></td>
<td>Create and post an <strong>Inventory Pick</strong>.</td>
</tr>
<tr>
<td><strong>Require Shipment</strong> without <strong>Require Pick</strong></td>
<td>Create and post a <strong>Warehouse Shipment</strong>.</td>
</tr>
<tr>
<td><strong>Require Pick</strong> and <strong>Require Shipment</strong></td>
<td>Register the <strong>Warehouse Pick</strong>, and then post the <strong>Warehouse Shipment</strong>.</td>
</tr>
<tr>
<td><strong>Bin Mandatory</strong></td>
<td>Enter valid source and destination bins, and post from the document required by the other warehouse settings.</td>
</tr>
<tr>
<td><strong>Directed Put-away and Pick</strong> at the source</td>
<td>Register the warehouse pick and post the warehouse shipment by using the advanced warehouse process.</td>
</tr>
</tbody>
</table>
<p>With <strong>Shipment and Receipt</strong>, the destination can't require warehouse receipt or put-away. A destination that uses bins requires a valid <strong>Transfer-To Bin Code</strong>.</p>
LaunchedDynamics 365 Business Central
<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>
LaunchedMicrosoft Copilot (Microsoft 365)
⏰ 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>
In developmentMicrosoft Edge
⏰ Act before December CY2026 · ~1 mo away
Microsoft Edge is updating its vertical tab implementation and architecture. Edge is reimplementing capabilities across pane, layout, controls, tab behavior, visual treatments, & embedder customizations. No admin action is required.
In developmentPossibleMicrosoft Entra
Windows Hello for Business (WHfB) and macOS Platform SSO (macOS PSSO) can now satisfy multifactor authentication as a standalone second factor. Previously, these methods only counted as MFA during primary sign-in, and users needed a separate passkey to complete step-up prompts, Authentication Strength policies, and sign-in frequency checks. With this change, WHfB and macOS PSSO work on their own for those scenarios, so more of your users can rely on strong, phishing-resistant sign-in without registering an extra method. What you need to know: Users who have only WHfB or macOS PSSO are now treated as MFA-capable and will no longer be automatically prompted to register another method. Because WHfB and macOS PSSO are tied to a specific device, we recommend having users register a portable method, such as a passkey or Microsoft Authenticator, during onboarding so they can complete MFA from any device.
In developmentOutlook
⏰ Act before September CY2026 · overdue
People using Outlook for iOS on iPhone and iPad will see refreshed interface elements aligned with the latest Liquid Glass iOS visual experience, including modernized app chrome, navigation, and use of screen space. It will be enabled by default with no administrator action required.
In developmentPossibleOneDrive
OneDrive is updating its integration with the iOS Files app to use Apple's Replicated File Provider API. This update provides end-user improvements such as better upload progress. As part of the change, read-only Shared and Libraries locations will no longer appear in the Files app integration. Users can use Add to OneDrive for shared content and libraries they need to access, including write access where permitted.
Rolling outMicrosoft Teams
⏰ Act before September CY2026 · overdue
We are providing a new configuration experience in Teams Admin Center where tenant admins can enable and customize an explicit consent message before joining any meeting hosted in their organization.
Rolling outMicrosoft Teams
⏰ Act before September CY2026 · overdue
What’s new
Teams now supports audio and video offloading for Town hall attendees in VDI environments that are using the new optimization. Media streams are offloaded directly to the user’s local device, improving performance and delivering a high definition viewing experience while reducing virtual desktop resource usage.
Who it applies to
• Windows endpoints only using the new VDI optimization
• Supported VDI platforms:
o Azure Virtual Desktop and Windows 365
o Citrix
o Omnissa
o Amazon WorkSpaces
What stays the same
All attendee interactivity features remain supported, including captions, DVR, reactions, streaming chat, and Q&A.
Additional details
First party and third party eCDNs are supported. When enabled, the attendee’s endpoint establishes a direct peer to peer connection using the local device network, avoiding virtual desktop double hop traffic.
Action required
No action is required if the new optimization for Microsoft Teams is already enabled.
LaunchedPossibleMicrosoft EdgeMicrosoft Copilot (Microsoft 365)
The Microsoft365CopilotChatIconEnabled policy is becoming the standard for configuring Copilot Chat. Extension and sidebar policies will no longer affect the appearance or functionality of Copilot Chat.
Rolling outPossibleMicrosoft Teams
We are updating private channels to align with compliance model for all channels. After this change, compliance policies applied to the team (M365 Group) will apply to all channels in the team - across standard, private, and shared. Private channels will no longer need user level targeting of policies different from other channels, and private channel compliance messages will no longer be copied to user mailboxes, relying on a dedicated, internal mailbox per channel like shared channels. In addition, limits for private channels will be increased so each team can have more than 30 private channels, up to the 1000 total channel limit per team. Private channel member limits will increase from 250 to 5000. You will also be able to schedule meetings in private channels.
Rolling outMicrosoft Purview
⏰ Act before December CY2025 · overdue
OCR Cost Estimator allows you to estimate the potential cost for using Optical Character Recognition. This means that you will no longer be required to set up an Azure Subscription for billing first and can accurately estimate the cost you would have incurred while using OCR. This will help you to identify the optimal configuration settings for OCR as per your requirements. Cost Estimator can be used for 30 days and will not scan images for sensitive content.
UpcomingMicrosoft Entra IDMicrosoft Authenticator App
⏰ Migrate before Aug 1, 2026 · passed 103d ago
What is changing? Starting August 2026, users will see an improved restore experience for device-bound Authenticator app passkeys for iOS users. No admin or user action is required.
betaMicrosoft GraphSecurity
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.
betaMicrosoft GraphSecurity
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.
betaMicrosoft GraphBackup and recovery
Added the backupPolicyDeleted member to the activityLogOperationType enumeration. Added the restoreJobType property to the restoreTaskActivityLog resource. Removed the tags property from the restoreTaskActivityLog resource.
betaMicrosoft GraphIdentity and access
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.
betaMicrosoft GraphDevice and app management
⏰ Update before removal Jan 31, 2024 · passed 1016d ago
Updated the date when the deprecated statusDetails property on the cloudPcDeviceImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the errorCode property. Updated the date when the deprecated id property on the cloudPcSourceDeviceImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the resourceId property. Updated the date when the deprecated offer property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the offerName property. Updated the date when the deprecated offerDisplayName property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the displayName property. Updated the date when the deprecated publisher property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the publisherName property. Updated the date when the deprecated recommendedSku property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. No replacement is planned. Updated the date when the deprecated sku property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the skuName property. Updated the date when the deprecated skuDisplayName property on the cloudPcGalleryImage resource will stop returning data from January 31, 2024 to December 7, 2026. Going forward, use the displayName property.
betaMicrosoft GraphDevice and app management
⏰ Update before removal Dec 31, 2026 · in 49d
Added the domainJoinCredential property to the cloudPcOnPremisesConnection resource. Added the cloudPcDomainJoinCredential resource. Added the cloudPcPlainTextDomainJoinCredential resource. Added the cloudPcKeyVaultDomainJoinCredential resource. Added the cloudPcDomainJoinKeyVaultIntentConfiguration resource. Added the cloudPcDomainJoinKeyVaultPasswordConfiguration resource. Added the cloudPcDomainJoinUserIdentity resource. Added the cloudPcDomainJoinPlainTextUserIdentity resource. Added the domainJoinCredential parameter to the updateAdDomainPassword method. Deprecated the adDomainPassword property of the cloudPcOnPremisesConnection resource. This property will be removed on December 31, 2026. Going forward use the domainJoinCredential property instead. Deprecated the adDomainUsername property of the cloudPcOnPremisesConnection resource. This property will be removed on December 31, 2026. Going forward use the domainJoinCredential/domainUserPrincipalName property instead. Deprecated the adDomainPassword parameter of the updateAdDomainPassword method. This parameter will be removed on December 31, 2026. Going forward use the domainJoinCredential parameter instead. Added the keyVaultSecretCheckAccessDenied member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckVaultNotReachable member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckNotFound member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckDisabled member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckExpired member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckEmptyValue member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckTransientServiceError member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration. Added the keyVaultSecretCheckUnknownError member to the cloudPcOnPremisesConnectionHealthCheckErrorType enumeration.
betaMicrosoft GraphFiles
⏰ Update before removal Sep 28, 2026 · passed 45d ago
Deprecated the viewer parameter on the preview method. The parameter will be removed on September 28, 2026. Call preview without this parameter. Deprecated the chromeless parameter on the preview method. The parameter will be removed on September 28, 2026. Call preview without this parameter. Deprecated the allowEdit parameter on the preview method. The parameter will be removed on September 28, 2026. Call preview without this parameter.
betaMicrosoft GraphMail
Removed the Get member method from the distributionList resource. Use the $expand=members query parameter with the Get distribution list method instead. Removed the List members method from the distributionList resource. Use the $expand=members query parameter with the Get distribution list method instead.
betaMicrosoft GraphMail
Removed the contactId property from the member resource. Added the memberId property to the member resource. Removed the recipientType property from the member resource. Removed the routingType property from the member resource. Added the type property to the member resource. Removed the members property from the distributionList resource. Added the members relationship to the distributionList resource.
betaMicrosoft GraphIdentity and access
Added the user member to the agentIdentityType enumeration. Added the displayName property to the agentRiskDetection resource. Added the identityId property to the agentRiskDetection resource. Deprecated the agentId property in the agentRiskDetection resource. Use identityId instead. This property will be removed after 2027-04-28. Deprecated the agentDisplayName property in the agentRiskDetection resource. Use displayName instead. This property will be removed after 2027-04-28.
betaMicrosoft GraphDevice and app management
⏰ Update before removal Jul 14, 2026 · passed 121d ago
Deprecated the cloudPcNotificationSetting resource. This resource will stop returning data on July 14, 2026. Deprecated the notificationSetting property on cloudPcUserSetting resource. This property will stop returning data on July 14, 2026.
betaMicrosoft GraphDevice and app management
⏰ Update before removal Jul 1, 2024 · passed 864d ago
Added the enrollmentState enumeration type. Added the updateCategoryEnrollmentInformation resource type. Removed the updateCategory property from the updateManagementEnrollment resource. Added the feature property to the updateManagementEnrollment resource. Added the quality property to the updateManagementEnrollment resource. Added the driver property to the updateManagementEnrollment resource. Deprecated the updatableAssetEnrollment resource. The updatableAssetEnrollment resource is deprecated and stopped returning data on July 1, 2024. Removed the enrollments property from the azureADDevice resource. Added the enrollment property to the azureADDevice resource.
betaMicrosoft GraphIdentity and access
Added the accessReviewContextData resource. Added the calloutRequest resource. Added the data resource. Added the applyDecisionContextData resource. Added the accessReviewContextDataBase resource. Removed the source property from the customDataProvidedResourceUploadSessionRequest resource. Removed the type property from the customDataProvidedResourceUploadSessionRequest resource. Added the customDataProvidedResourceAccessReviewUploadSession resource. Removed the source property from the customDataProvidedResourceUploadSession resource. Removed the type property from the customDataProvidedResourceUploadSession resource.
betaMicrosoft GraphIdentity and access
Removed the accessReviewDataUploadTriggerCallbackData resource. Removed the accessReviewResourceDataUploadSessionContextData resource. Removed the source property from the customDataProvidedResourceUploadSessionRequest resource. Removed the type property from the customDataProvidedResourceUploadSessionRequest resource. Removed the customExtensionData resource. Added the accessPackageAssignmentResourceRole resource. Added the customDataProvidedResourceAccessReviewUploadSession resource. Removed the source property from the customDataProvidedResourceUploadSession resource. Removed the type property from the customDataProvidedResourceUploadSession resource. Added the accessReviewContextData resource. Added the accessReviewContextDataBase resource. Added the applyDecisionContextData resource. Added the calloutRequest resource. Added the data resource.
betaMicrosoft GraphBackup and recovery
Added the granularRestoreItems enumeration type. Deprecated the queryExpression property of the artifactQuery resource. Use the structuredQueryExpression property instead. Added the structuredQueryExpression property to the artifactQuery resource. Added the restoreSearchArtifactQueryExpression resource.
betaMicrosoft GraphTenants
Added the migrate method to the crossTenantMigrationJob resource. Changed the behavior of the validate method on the crossTenantMigrationJob resource to validate an existing job as an entity-bound action. Going forward, use the POST /solutions/migrations/crossTenantMigrationJobs/{crossTenantMigrationJobId}/validate endpoint to trigger the validation of an existing cross-tenant migration job. Removed the displayName parameter from the validate method. Removed the completeAfterDateTime parameter from the validate method. Removed the sourceTenantId parameter from the validate method. Removed the exchangeSettings parameter from the validate method. Removed the workloads parameter from the validate method. Removed the resourceType parameter from the validate method. Removed the resources parameter from the validate method.
betaMicrosoft GraphSecurity
Added the policyTip member to the dlpAction enumeration. Removed the overrideOption property from the notifyUserAction resource. Removed the policyTip property from the notifyUserAction resource. Added the policyTipAction resource.
betaMicrosoft GraphSecurity
Added the detectionRuleStatus enumeration type. Added the accountObjectIdAction resource. Added the accountSidAction resource. Added the alertCustomDetails resource. Removed the alertTemplate resource. Deprecated the allowFileResponseAction resource. Added the automatedAction resource. Added the automatedActionSet resource. Deprecated the blockFileResponseAction resource. Deprecated the collectInvestigationPackageResponseAction resource. Removed the detectionAction resource. Added the deviceAction resource. Deprecated the disableUserResponseAction resource. Added the emailAction resource. Added the fileAction resource. Deprecated the forceUserPasswordResetResponseAction resource. Deprecated the hardDeleteResponseAction resource. Deprecated the impactedAsset resource. Deprecated the impactedDeviceAsset resource. Deprecated the impactedMailboxAsset resource. Deprecated the impactedUserAsset resource. Deprecated the initiateInvestigationResponseAction resource. Added the isolateDeviceAction resource. Deprecated the isolateDeviceResponseAction resource. Deprecated the markUserAsCompromisedResponseAction resource. Added the mitreTactic resource. Added the mitreTechnique resource. Deprecated the moveToDeletedItemsResponseAction resource. Deprecated the moveToInboxResponseAction resource. Deprecated the moveToJunkResponseAction resource. Added the deviceGroups property to the organizationalScope resource. Deprecated the organizationalScope resource. Deprecated the organizationalScope resource. Deprecated the queryCondition resource. Deprecated the responseAction resource. Deprecated the restrictAppExecutionResponseAction resource. Added the frequency property to the ruleSchedule resource. Deprecated the ruleSchedule resource. Deprecated the ruleSchedule resource. Deprecated the runAntivirusScanResponseAction resource. Deprecated the runDetails resource. Deprecated the softDeleteResponseAction resource. Added the stopAndQuarantineFileAction resource. Deprecated the stopAndQuarantineFileResponseAction resource. Added the accountEntityMapping resource. Added the alertTemplate resource. Added the amazonResourceEntityMapping resource. Added the azureResourceEntityMapping resource. Added the cloudApplicationEntityMapping resource. Added the detectionAction resource. Added the createdBy property to the detectionRule resource. Added the createdDateTime property to the detectionRule resource. Added the description property to the detectionRule resource. Removed the detectionAction property from the detectionRule resource. Deprecated the detectionRule resource. Added the displayName property to the detectionRule resource. Added the id property to the detectionRule resource. Added the isEnabled property to the detectionRule resource. Added the lastModifiedBy property to the detectionRule resource. Added the lastModifiedDateTime property to the detectionRule resource. Deprecated the detectionRule resource. Added the status property to the detectionRule resource. Added the detectionAction relationship to the detectionRule resource. Added the dnsEntityMapping resource. Added the entityMapping resource. Added the entityMappingConfiguration resource. Added the fileEntityMapping resource. Added the googleCloudResourceEntityMapping resource. Added the hostEntityMapping resource. Added the ipEntityMapping resource. Added the mailboxEntityMapping resource. Added the mailClusterEntityMapping resource. Added the mailMessageEntityMapping resource. Added the oAuthApplicationEntityMapping resource. Added the processEntityMapping resource. Removed the protectionRule resource. Added the registryValueEntityMapping resource. Added the securityGroupEntityMapping resource. Added the urlEntityMapping resource.
v1.0Microsoft GraphSecurity
Added the AlertSubmission member to the auditLogRecordType enumeration. Removed the ReportSubmission member from the auditLogRecordType enumeration. Added the AlertSubmissionResultDetail member to the auditLogRecordType enumeration. Removed the ReportSubmissionResultDetail member from the auditLogRecordType enumeration. Added the ComplianceSitGradingSharePoint member to the auditLogRecordType enumeration. Added the CompliancePolicyGradingSharePoint member to the auditLogRecordType enumeration. Added the AzureAISearchAudit member to the auditLogRecordType enumeration. Added the P4AIRiskScoreRecord member to the auditLogRecordType enumeration. Added the DragonCopilotAdmin member to the auditLogRecordType enumeration. Added the AISpanOutputs member to the auditLogRecordType enumeration. Added the EopSubmissionFeedEntity member to the auditLogRecordType enumeration. Added the SonarFileDetonationEntity member to the auditLogRecordType enumeration. Added the SonarSubmissionEntity member to the auditLogRecordType enumeration. Added the SonarUrlDetonationEntity member to the auditLogRecordType enumeration. Added the SubmissionEntity member to the auditLogRecordType enumeration. Added the SonarDetonationEntity member to the auditLogRecordType enumeration. Added the MicrosoftTeamsUserConcern member to the auditLogRecordType enumeration. Added the VivaGlintAgenticCampaign member to the auditLogRecordType enumeration. Added the MSPVectorSearchContentMetadata member to the auditLogRecordType enumeration. Added the FabricPolicy member to the auditLogRecordType enumeration. Added the SecurityCopilotAgentIdentityManagement member to the auditLogRecordType enumeration. Added the CopilotSessionSharing member to the auditLogRecordType enumeration. Added the DragonCopilotAccess member to the auditLogRecordType enumeration. Added the DragonCopilotClinicalData member to the auditLogRecordType enumeration. Added the DragonCopilotSession member to the auditLogRecordType enumeration. Added the aISpanOutputsAuditRecord resource. Added the alertSubmissionAuditRecord resource. Added the alertSubmissionResultDetailAuditRecord resource. Added the dynamicProperties property to the auditData resource. Added the auditRecordTypeDictionary resource. Added the azureAISearchAuditRecord resource. Added the compliancePolicyGradingSharePointAuditRecord resource. Added the complianceSitGradingSharePointAuditRecord resource. Added the copilotSessionSharingAuditRecord resource. Added the eopSubmissionFeedEntityAuditRecord resource. Added the fabricPolicyRecord resource. Added the microsoftTeamsUserConcernAuditRecord resource. Added the mspVectorSearchContentMetadataAuditRecord resource. Added the p4AIRiskScoreRecord resource. Added the securityCopilotIdentityManagementAuditRecord resource. Added the sonarDetonationEntityAuditRecord resource. Added the sonarFileDetonationEntityAuditRecord resource. Added the sonarSubmissionEntityAuditRecord resource. Added the sonarUrlDetonationEntityAuditRecord resource. Added the submissionEntityAuditRecord resource. Added the vivaGlintAgenticCampaignAuditRecord resource. Added the MosAgentInfoRecordV2 member to the auditLogRecordType enumeration. Added the SecurityDevelopmentLifecycleAILog member to the auditLogRecordType enumeration. Added the MDASH member to the auditLogRecordType enumeration. Added the DefenderSecurityForAIConfiguration member to the auditLogRecordType enumeration. Added the SparkCoreCustomLivePool member to the auditLogRecordType enumeration. Added the mosAgentInfoRecordV2 resource type. Added the securityDevelopmentLifecycleAILogAuditRecord resource type. Added the mDASHAuditRecord resource type. Added the defenderSecurityForAIConfigurationAuditRecord resource type. Added the sparkCoreCustomLivePoolRecord resource type. Added the dragonCopilotAccessRecord resource type. Added the dragonCopilotAdminRecord resource type. Added the dragonCopilotClinicalDataRecord resource type. Added the dragonCopilotSessionRecord resource type. Added the a365AiExecuteTool resource. Added the a365AiInferenceCall resource. Added the a365AiInvokeAgent resource. Added the a365AiRunSummary resource. Added the a365SpanOutputs resource. Added the aadRiskDetectionAuditRecord resource. Added the aedAuditRecord resource. Added the agentAdminActivityRecord resource. Added the agentSettingAdminActivity resource. Added the aiAppInteractionAuditRecord resource. Added the aiExecuteToolAuditRecord resource. Added the aiInteractionsChangeNotificationAuditRecord resource. Added the aiInteractionsExportAuditRecord resource. Added the aiInteractionsSubscriptionAuditRecord resource. Added the aiInvokeAgentAuditRecord resource. Added the aipDiscover resource. Added the aipFileDeleted resource. Added the aipHeartBeat resource. Added the aipProtectionActionLogRequest resource. Added the aipScannerDiscoverEvent resource. Added the aipSensitivityLabelActionLogRequest resource. Added the airAdminActionInvestigationData resource. Added the airInvestigationData resource. Added the airManualInvestigationData resource. Added the attackSimAdminAuditRecord resource. Added the attackSimAuditRecord resource. Added the auditConfigAuditRecord resource. Added the auditSearchAuditRecord resource. Added the azfwApplicationRuleAggregationEventRecord resource. Added the azfwDnsQueryEventRecord resource. Added the azfwNetworkRuleEventRecord resource. Added the azureActiveDirectoryAccountLogonAuditRecord resource. Added the azureActiveDirectoryAuditRecord resource. Added the azureActiveDirectoryStsLogonAuditRecord resource. Added the campaignAuditRecord resource. Added the ccraiPolicyViolationRecord resource. Added the cdpClassifierHealthRecord resource. Added the cdpColdCrawlStatusRecord resource. Added the cdpConsumptionResourceRecord resource. Added the cdpContentExplorerAggregateRecord resource. Added the cdpDlpSensitiveEndpointAuditRecord resource. Added the cdpLogRecord resource. Added the cdpOcrBillingRecord resource. Added the cdpResourceScopeChangeEventRecord resource. Added the cdpdlmaiInteractionInsightsRecord resource. Added the cloudUpdateDeviceConfigAuditRecord resource. Added the cloudUpdateProfileConfigAuditRecord resource. Added the cloudUpdateTenantConfigAuditRecord resource. Added the complianceConnectorAuditRecord resource. Added the complianceDLMExchangeAuditRecord resource. Added the complianceDLMSharePointAuditRecord resource. Added the complianceDLPApplicationsAuditRecord resource. Added the complianceDLPApplicationsClassificationAuditRecord resource. Added the complianceDLPEndpointAuditRecord resource. Added the complianceDLPEndpointDiscoveryAuditRecord resource. Added the complianceDLPEnforcementAuditRecord resource. Added the complianceDLPExchangeAuditRecord resource. Added the complianceDLPExchangeClassificationAuditRecord resource. Added the complianceDLPExchangeClassificationCdpRecord resource. Added the complianceDLPExchangeDiscoveryAuditRecord resource. Added the complianceDLPSharePointAuditRecord resource. Added the complianceDLPSharePointClassificationAuditRecord resource. Added the complianceDLPSharePointClassificationCdpRecord resource. Added the complianceDLPSharePointClassificationExtendedAuditRecord resource. Added the complianceExchangeOcrAuditRecord resource. Added the complianceManagerActionRecord resource. Added the complianceSettingsChangeAuditRecord resource. Added the complianceSupervisionExchangeAuditRecord resource. Added the connectedAIAppInteractionAuditRecord resource. Added the consumptionResourceAuditRecord resource. Added the contentStoreMetadataRecord resource. Added the copilotAgentManagementAuditRecord resource. Added the copilotForSecurityLoggingAuditRecord resource. Added the copilotForSecurityTriggerAuditRecord resource. Added the copilotInteractionAuditRecord resource. Added the copilotPluginSettingAuditRecord resource. Added the copilotPromptBookSettingAuditRecord resource. Added the copilotSettingAuditRecord resource. Added the copilotWorkspaceSettingAuditRecord resource. Added the coreReportingSettingsAuditRecord resource. Added the cortanaBriefingAuditRecord resource. Added the criticalAssetManagementClassificationRecord resource. Added the crmEntityOperationAuditRecord resource. Added the crossTenantAccessPolicyAuditRecord resource. Added the customerKeyServiceEncryptionAuditRecord resource. Added the dataCenterSecurityCmdletAuditRecord resource. Added the dataGovernanceAuditRecord resource. Added the dataInsightsRestApiAuditRecord resource. Added the dataLakeExportOperationAuditRecord resource. Added the dataSecurityInvestigationAuditRecord resource. Added the dataShareOperationAuditRecord resource. Added the defenderCaseManagementAuditRecord resource. Added the defenderPreviewFeaturesRecord resource. Added the deployFeatureActivityRecord resource. Added the deviceDiscoverySettingsAuthenticatedScansRecord resource. Added the deviceDiscoverySettingsExclusionRecord resource. Added the deviceDiscoverySettingsRecord resource. Added the discoveryAuditRecord resource. Added the dlpEndpointAuditRecord resource. Added the dlpImportResultAuditRecord resource. Added the dlpSensitiveInformationTypeRulePackageCmdletRecord resource. Added the dynamics365BusinessCentralAuditRecord resource. Added the ehrConnectorAuditBaseRecord resource. Added the exchangeAdminAuditRecord resource. Added the exchangeAggregatedMailboxAuditRecord resource. Added the exchangeAggregatedOperationRecord resource. Added the exchangeMailboxAuditGroupRecord resource. Added the exchangeMailboxAuditRecord resource. Added the fabricAuditRecord resource. Added the healthcareSignalRecord resource. Added the hostedRpaAuditRecord resource. Added the hrSignalAuditRecord resource. Added the hygieneEventRecord resource. Added the informationBarrierPolicyApplicationAuditRecord resource. Added the informationWorkerProtectionAuditRecord resource. Added the insiderRiskScopedUserInsightsRecord resource. Added the insiderRiskScopedUsersRecord resource. Added the integratedAppsAppAdminActivityAuditRecord resource. Added the integratedAppsAppSettingsAdminActivityAuditRecord resource. Added the irmActivityAuditTrailRecord resource. Added the irmUserDefinedDetectionRecord resource. Added the kaizalaAuditRecord resource. Added the labelAnalyticsAggregateAuditRecord resource. Added the labelContentExplorerAuditRecord resource. Added the largeContentMetadataAuditRecord resource. Added the m365ComplianceConnectorAuditRecord resource. Added the m365SearchSectionsRecord resource. Added the m365daadAuditRecord resource. Added the m365odspAssetMetadataRecord resource. Added the mailSubmissionData resource. Added the managedServicesAuditRecord resource. Added the managedTenantsAuditRecord resource. Added the mapgAlertsAuditRecord resource. Added the mapgOnboardAuditRecord resource. Added the mapgPolicyAuditRecord resource. Added the mapgRemediationAuditRecord resource. Added the mcasAlertsAuditRecord resource. Added the mdaAuditRecord resource. Added the mdaDataSecuritySignalRecord resource. Added the mdatpAuditRecord resource. Added the mdcEventsRecord resource. Added the mdiAuditRecord resource. Added the meshWorldsAuditRecord resource. Added the microsoft365BackupBackupItemAuditRecord resource. Added the microsoft365BackupBackupPolicyAuditRecord resource. Added the microsoft365BackupGranularBrowseTaskAuditRecord resource. Added the microsoft365BackupRestoreItemAuditRecord resource. Added the microsoft365BackupRestoreTaskAuditRecord resource. Added the microsoft365CopilotScheduledPromptAuditRecord resource. Added the microsoftDefenderExpertsXDRAuditRecord resource. Added the microsoftFlowAuditRecord resource. Added the microsoftFormsAuditRecord resource. Added the microsoftGraphDataConnectConsent resource. Added the microsoftGraphDataConnectOperation resource. Added the microsoftPurviewDataCatalogOperationRecord resource. Added the microsoftPurviewDataMapOperationRecord resource. Added the microsoftPurviewMetadataPolicyOperationRecord resource. Added the microsoftPurviewPolicyOperationRecord resource. Added the microsoftPurviewPrivacyAuditEvent resource. Added the microsoftPurviewUnifiedCatalogOperationRecord resource. Added the microsoftStreamAuditRecord resource. Added the microsoftTeamsAdminAuditRecord resource. Added the microsoftTeamsAnalyticsAuditRecord resource. Added the microsoftTeamsAuditRecord resource. Added the microsoftTeamsDeviceAuditRecord resource. Added the microsoftTeamsRetentionLabelActionAuditRecord resource. Added the microsoftTeamsSensitivityLabelActionAuditRecord resource. Added the microsoftTeamsShiftsAuditRecord resource. Added the mipAutoLabelExchangeItemAuditRecord resource. Added the mipAutoLabelProgressFeedbackAuditRecord resource. Added the mipAutoLabelSharePointItemAuditRecord resource. Added the mipAutoLabelSharePointPolicyLocationAuditRecord resource. Added the mipAutoLabelSimulationSharePointCompletionRecord resource. Added the mipAutoLabelSimulationSharePointProgressRecord resource. Added the mipAutoLabelSimulationStatisticsRecord resource. Added the mipExactDataMatchAuditRecord resource. Added the mipLabelAnalyticsAuditRecord resource. Added the mipLabelAuditRecord resource. Added the mosAgentInfoRecord resource. Added the ms365dCustomDetectionAuditRecord resource. Added the ms365dIncidentAuditRecord resource. Added the ms365dSuppressionRuleAuditRecord resource. Added the msdeCustomCollectionAuditRecord resource. Added the msdeGeneralSettingsAuditRecord resource. Added the msdeIndicatorsSettingsAuditRecord resource. Added the msdeResponseActionsAuditRecord resource. Added the msdeRolesSettingsAuditRecord resource. Added the msticNationStateNotificationRecord resource. Added the multiStageDispositionAuditRecord resource. Added the myAnalyticsSettingsAuditRecord resource. Added the noisyAlertPolicyAuditRecord resource. Added the officeNativeAuditRecord resource. Added the omePortalAuditRecord resource. Added the onDemandSharePointClassificationAuditRecord resource. Added the onPremisesFileShareScannerDLPAuditRecord resource. Added the onPremisesSharePointScannerDLPAuditRecord resource. Added the oneDriveAuditRecord resource. Added the organizationalDataInM365AuditRecord resource. Added the outlookCopilotAutomationAuditRecord resource. Added the owaGetAccessTokenForResourceAuditRecord resource. Added the p4aiAssessmentCategoryRecord resource. Added the p4aiAssessmentFabricScannerRecord resource. Added the p4aiAssessmentLocationResultRecord resource. Added the p4aiAssessmentRecord resource. Added the peopleAdminSettingsAuditRecord resource. Added the physicalBadgingSignalAuditRecord resource. Added the placesDirectoryAuditRecord resource. Added the plannerChatMessageAuditRecord resource. Added the plannerChatMessageListAuditRecord resource. Added the plannerCopyPlanAuditRecord resource. Added the plannerGoalAuditRecord resource. Added the plannerGoalListAuditRecord resource. Added the plannerPlanAuditRecord resource. Added the plannerPlanListAuditRecord resource. Added the plannerPlanSensitivityLabelAuditRecord resource. Added the plannerRosterAuditRecord resource. Added the plannerRosterSensitivityLabelAuditRecord resource. Added the plannerTaskAuditRecord resource. Added the plannerTaskListAuditRecord resource. Added the plannerTenantSettingsAuditRecord resource. Added the policyConfigChangeAuditRecord resource. Added the powerAppsAuditAppRecord resource. Added the powerAppsAuditPlanRecord resource. Added the powerAppsAuditResourceRecord resource. Added the powerBIAuditRecord resource. Added the powerBIDlpAuditRecord resource. Added the powerPagesSiteAuditRecord resource. Added the powerPlatformAdminDlpAuditRecord resource. Added the powerPlatformAdminEnvironmentAuditRecord resource. Added the powerPlatformAdministratorActivityRecord resource. Added the powerPlatformLockboxResourceAccessRequestAuditRecord resource. Added the powerPlatformLockboxResourceCommandAuditRecord resource. Added the powerPlatformServiceActivityAuditRecord resource. Added the powerPlatformTenantIsolationRecord resource. Added the privaPrivacyAssessmentOperationRecord resource. Added the privaPrivacyConsentOperationRecord resource. Added the privacyDataMatchAuditRecord resource. Added the privacyDataMinimizationRecord resource. Added the privacyDigestEmailRecord resource. Added the privacyOpenAccessAuditRecord resource. Added the privacyPortalAuditRecord resource. Added the privacyRemediationActionRecord resource. Added the privacyRemediationRecord resource. Added the projectAuditRecord resource. Added the projectForTheWebAssignedToMeSettingsAuditRecord resource. Added the projectForTheWebProjectAuditRecord resource. Added the projectForTheWebProjectSettingsAuditRecord resource. Added the projectForTheWebRoadmapAuditRecord resource. Added the projectForTheWebRoadmapItemAuditRecord resource. Added the projectForTheWebRoadmapSettingsAuditRecord resource. Added the projectForTheWebTaskAuditRecord resource. Added the publicFolderAuditRecord resource. Added the purviewInsiderRiskAlertsRecord resource. Added the purviewInsiderRiskCasesRecord resource. Added the purviewMCRecommendationRecord resource. Added the purviewPostureAgentAuditRecord resource. Added the quarantineAuditRecord resource. Added the recordsManagementAuditRecord resource. Added the reportSubmission resource. Added the reportSubmissionResultDetail resource. Added the restrictedModeAuditRecord resource. Added the retentionPolicyAuditRecord resource. Added the rtiOperationsAgentAuditRecord resource. Added the sbpConfigurationEventRecord resource. Added the sbpUsageEventRecord resource. Added the scoreEvidence resource. Added the scorePlatformGenericAuditRecord resource. Added the scriptRunAuditRecord resource. Added the searchAuditRecord resource. Added the securityComplianceAlertRecord resource. Added the securityComplianceCenterEOPCmdletAuditRecord resource. Added the securityComplianceInsightsAuditRecord resource. Added the securityComplianceRBACAuditRecord resource. Added the securityComplianceUserChangeAuditRecord resource. Added the sensitiveInfoRemediationAgentDataRecord resource. Added the sensitivityLabelActionAuditRecord resource. Added the sensitivityLabelPolicyMatchAuditRecord resource. Added the sensitivityLabeledFileActionAuditRecord resource. Added the sentinelAIToolAuditRecord resource. Added the sentinelGraphAuditRecord resource. Added the sentinelJobAuditRecord resource. Added the sentinelKQLOnLakeAuditRecord resource. Added the sentinelLakeDataOnboardingAuditRecord resource. Added the sentinelLakeEncryptionAuditRecord resource. Added the sentinelLakeOnboardingAuditRecord resource. Added the sentinelNotebookOnLakeAuditRecord resource. Added the sentinelPackageAuditRecord resource. Added the sharePointAppPermissionOperationAuditRecord resource. Added the sharePointAuditRecord resource. Added the sharePointCommentOperationAuditRecord resource. Added the sharePointContentSecurityPolicyAuditRecord resource. Added the sharePointContentTypeOperationAuditRecord resource. Added the sharePointESignatureAuditRecord resource. Added the sharePointFieldOperationAuditRecord resource. Added the sharePointFileOperationAuditRecord resource. Added the sharePointListItemOperationAuditRecord resource. Added the sharePointListOperationAuditRecord resource. Added the sharePointSharingOperationAuditRecord resource. Added the skypeForBusinessCmdletsAuditRecord resource. Added the skypeForBusinessPSTNUsageAuditRecord resource. Added the skypeForBusinessUsersBlockedAuditRecord resource. Added the sonarDetonationContentMetadata resource. Added the supervisoryReviewDayXInsightsAuditRecord resource. Added the syntheticProbeAuditRecord resource. Added the teamCopilotInteractionAuditRecord resource. Added the teamsEasyApprovalsAuditRecord resource. Added the teamsEvalDataHubAdminOperationAuditRecord resource. Added the teamsEvalDataHubDataAccessAuditRecord resource. Added the teamsEvalDataHubPermissionChangeAuditRecord resource. Added the teamsHealthcareAuditRecord resource. Added the teamsUpdatesAuditRecord resource. Added the tenantAllowBlockListAuditRecord resource. Added the threatFinderAuditRecord resource. Added the threatIntelligenceAtpContentData resource. Added the threatIntelligenceExportAuditRecord resource. Added the threatIntelligenceMailData resource. Added the threatIntelligenceObjectAuditRecord resource. Added the threatIntelligenceUrlClickData resource. Added the todoAuditRecord resource. Added the trainableClassifierAuditRecord resource. Added the uamOperationAuditRecord resource. Added the unifiedGroupAuditRecord resource. Added the unifiedSimulationMatchedItemAuditRecord resource. Added the unifiedSimulationSummaryAuditRecord resource. Added the universalPrintManagementAuditRecord resource. Added the universalPrintPrintJobAuditRecord resource. Added the urbacAssignmentAuditRecord resource. Added the urbacEnableStateAuditRecord resource. Added the urbacRoleAuditRecord resource. Added the userTrainingAuditRecord resource. Added the usxWorkspaceOnboardingAuditRecord resource. Added the vfamCreatePolicyAuditRecord resource. Added the vfamDeletePolicyAuditRecord resource. Added the vfamUpdatePolicyAuditRecord resource. Added the vivaAmplifyAuditRecord resource. Added the vivaEngageEventsAuditRecord resource. Added the vivaEngageNetworkAssociationAuditRecord resource. Added the vivaEngageSegmentAuditRecord resource. Added the vivaGlintAdvancedConfigurationAuditRecord resource. Added the vivaGlintFeedbackProgramAuditRecord resource. Added the vivaGlintOrganizationalDataAuditRecord resource. Added the vivaGlintPulseProgramAuditRecord resource. Added the vivaGlintPulseProgramRespondentRateAuditRecord resource. Added the vivaGlintQuestionAuditRecord resource. Added the vivaGlintRoleAuditRecord resource. Added the vivaGlintRubiconAuditRecord resource. Added the vivaGlintSupportAccessAuditRecord resource. Added the vivaGlintSystemAuditRecord resource. Added the vivaGlintUserAuditRecord resource. Added the vivaGlintUserGroupAuditRecord resource. Added the vivaGoalsAuditRecord resource. Added the vivaLearningAdminAuditRecord resource. Added the vivaLearningAuditRecord resource. Added the vivaPulseAdminAuditRecord resource. Added the vivaPulseOrganizerAuditRecord resource. Added the vivaPulseReportAuditRecord resource. Added the vivaPulseResponseAuditRecord resource. Added the wdatpAlertsAuditRecord resource. Added the webContentFilteringAuditRecord resource. Added the windows365CustomerLockboxAuditRecord resource. Added the workplaceAnalyticsAuditRecord resource. Added the yammerAuditRecord resource. Added the yammerUserHidingAuditRecord resource. Added the auditCoreRoot resource. Added the auditLog relationship to the security resource. Added the auditLogQueryStatus enumeration type with members: notStarted, running, succeeded, failed, cancelled, unknownFutureValue. Added the auditLogUserType enumeration type with members: Regular, Reserved, Admin, DcAdmin, System, Application, ServicePrincipal, CustomPolicy, SystemPolicy, PartnerTechnician, Guest, unknownFutureValue. Added the auditLogRecordType enumeration type.
v1.0Microsoft GraphApplications
Added the applicationDataType enumeration type. Added the csaStarLevel enumeration type. Added the dataProtection enumeration type. Added the dataRetentionLevel enumeration type. Added the fedRampLevel enumeration type. Added the holdType enumeration type. Added the passwordPolicy enumeration type. Added the pciVersion enumeration type. Added the restEncryptionType enumeration type. Added the sslVersion enumeration type. Added the userOwnership enumeration type. Added the applicationLocation resource. Added the applicationRiskFactorCertificateInfo resource. Added the applicationRiskFactorGeneralInfo resource. Added the applicationRiskFactorLegalInfo resource. Added the applicationRiskFactorLegalInfoGdpr resource. Added the applicationRiskFactors resource. Added the applicationRiskFactorSecurityInfo resource. Added the applicationRiskScore resource. Added the applicationSecurityCompliance resource. Added the deprecationDate property to the applicationTemplate resource. Added the endpoints property to the applicationTemplate resource. Added the isEntraIntegrated property to the applicationTemplate resource. Added the lastModifiedDateTime property to the applicationTemplate resource. Added the riskFactors property to the applicationTemplate resource. Added the riskScore property to the applicationTemplate resource. Added the licenseRequired resource.