M365 Change Tracker

← Home

Microsoft 365 retirements & removals (27)

Upcoming retirements, removals and end-of-support across Microsoft 365.

See also: Exploited CVEs · Breaking & API

In developmentPossibleDynamics 365 Business Central

Dynamics 365 Business Central: USA - Manually upload 1099 forms to the IRIS

<p>The FIRE system will effectively be retired at the end of 2026, and IRIS will be the only electronic filing channel starting January 1, 2027.</p> <p>Users in Business Central can now generate IRIS-compatible 1099 submission files for manually upload instead of the legacy FIRE format.</p> <p>This feature will stay alongside A2A integration wirh IRIS providing full automation in reporting 1099 forms.</p>

LaunchedPossibleDynamics 365 Business Central

Dynamics 365 Business Central: Supply chain management - Use subcontracting capabilities in production processes

<p>The standard Dynamics 365 Business Central solution already meets many global needs. We expand that solution to meet local needs by adding capabilities that include:</p> <ul> <li>Logistics flows that manage subcontractor transfers for raw materials and components, along with warehouse handling and item tracking.</li> <li>Flexible pricing that considers the work center, item, dates, and quantity.</li> <li>Finished goods receipts with item tracking and warehouse handling from purchase orders.</li> <li>Logistics flows that manage subcontractor transfers of finished goods.</li> <li>Enhanced usability and more transparency in production processes.</li> </ul> <p><strong>Special note for Italian localizations</strong></p> <p>The Italian localization currently supports logistics for both finished goods and raw materials/components. We deprecate the existing local functionality and provide upgrade logic to facilitate migration to a new W1 solution. You decide when to start the transition by activating a feature key on the <strong>Feature Management</strong> page.</p> <p>Business Value:</p> <p>A complex industrial structure can include external vendors that handle specific tasks within the broader production process. Some companies outsource up to 75 percent of their production. Outsourcing can lead to significant cost savings or access to specialized skills and technologies that might not be available otherwise. A typical example is a company that handles research, design, quality control, and sales in-house but outsources all or large parts of the actual production.</p> <p>Enabled for:</p> <p>Enabled by admins/makers/marketers for end users</p>

In developmentPossiblePower Apps

Power Apps: Manage model-driven app AI features from consolidated settings

<p>Consolidated AI settings make it easier for makers and admins to find and manage AI capabilities for model-driven apps across two complementary surfaces.</p> <p>In Maker Studio, the <strong>Settings</strong> dialog in the model app form designer adds a new top-level <strong>Copilot and AI</strong> tab. Makers can see and adjust all available AI options for the app in one place instead of finding them scattered among all the other settings.</p> <p>In the Power Platform admin center, model-driven app AI settings are consolidated from <strong>Environment &gt; Settings</strong> into <strong>Copilot Hub &gt; Power Apps</strong>. This provides a central location for settings such as Generative pages, Copilot in apps, and the in-app AI skills. The in-app skill settings are organized into these groups:</p> <ul> <li><strong>Data entry:</strong> Form fill assistance.</li> <li><strong>Summary:</strong> Row summaries.</li> <li><strong>Data analysis:</strong> AI-generated charts and natural-language search and filtering.</li> </ul> <p>Labels and descriptions are aligned across Maker Studio and Copilot Hub so makers and admins can understand how the controls relate.</p> <p>As part of this consolidation, the old model-driven app AI switches under <strong>Environment &gt; Settings</strong> will also be retired and removed.</p> <h3>Availability</h3> <table> <thead> <tr> <th>Field</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Applies to</td> <td>Model-driven apps</td> </tr> <tr> <td>Release Channel</td> <td>Weekly</td> </tr> <tr> <td>Version</td> <td>2610.3</td> </tr> <tr> <td>Feature Scope</td> <td>Admins or makers</td> </tr> </tbody> </table>

LaunchedDynamics 365 Business Central

Dynamics 365 Business Central: Ecommerce - Keep Shopify connections current

<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>

In developmentPossibleSharePointMicrosoft Viva

SharePoint: Viva Connections multi-home site management moving to SharePoint admin center

Viva Connections multi-home site management is moving from the Microsoft 365 admin center (MAC) to the SharePoint Admin Center (SPAC). Administrators will be able to create and manage multiple Home sites, configure audience targeting, manage home site priority order, and remove Home sites directly from SPAC. Existing entry points in the Microsoft 365 admin center will direct administrators to the new SPAC experience. As part of this update, legacy Viva Connections (VC) instances and draft/enabled management concepts are being deprecated as Viva Connections administration is consolidated into SharePoint Home site management. Existing VC experiences will be upgraded to full Home sites.

In developmentPossibleMicrosoft Copilot (Microsoft 365)

Microsoft Copilot (Microsoft 365): Dynamic Tool Discovery for Declarative Agents and Federated Copilot Connectors

We're introducing dynamic tool discovery for declarative agents in Microsoft 365 Copilot. Developers can now add, update, or retire tools on their MCP servers without republishing the agent - so end users get the latest agent capabilities immediately, with no deployment cycle in between. Support for federated Copilot connectors will be a fast follow to declarative agents at a later stage. Dynamic tool discovery is backed by Microsoft's enterprise RAI and security protections, and customers retain full control over agent deployment and availability to users and groups.

Rolling outPossibleMicrosoft TeamsMicrosoft Copilot (Microsoft 365)

Microsoft Teams: Spoken language detection is now automatic

Spoken language detection is now fully automatic. Teams will automatically detect each speaker’s spoken language and update it in real time as the conversation evolves. Manual spoken language selection will no longer be available. This applies to both live captions and transcripts when Interpreter is enabled or when multilingual speech recognition is turned on in meeting options, helping deliver more accurate language recognition and a more consistent multilingual meeting experience.

Rolling outPossibleMicrosoft Teams

Microsoft Teams: Automatic removal of EXIF data from shared images

Teams will automatically remove hidden metadata (EXIF) from images shared in conversations. This privacy protection helps prevent sensitive information such as photo location and device details from being shared without your knowledge.

CancelledPossibleMicrosoft Copilot (Microsoft 365)

Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Users can create agents scoped on Custom connector containers

<ol> <li>Makers can now scope their data in their agent created on custom connector data at a particular container.</li> <li>These containers will be defined during creation/updating of the custom connector.</li> </ol> <p>Note: This roadmap item is no longer accurate and will be removed from the roadmap. We apologize for any inconvenience.</p>

LaunchedPossibleMicrosoft Viva

Microsoft Viva: Focus Area simplification and enhancements

Beginning with this feature release, Focus Areas will be associated with survey cycles and goal periods will be retired. Users will be able to select the same Focus Area across multiple cycles. The Focus Area Overview report will be filterable to groups of interest (e.g. managers only). Draft/deleted Focus Areas will no longer be included in Focus Area calculations.

LaunchedPossibleMicrosoft Purview

Microsoft Purview compliance portal: Communication Compliance - Policy insights

The Communication Compliance homepage will provide two columns that offer a quick overview of policy performance: the first column shows the number of scanned parent items in real time, giving visibility into scanning progress; the second column keeps you informed about parent items that meet policy conditions, ensuring you stay updated on potential issues requiring attention and maintaining control over communication compliance. This item is no longer accurate and is being removed from the roadmap. We apologize for the inconvenience.

UpcomingMicrosoft Entra IDEntra Connect

Enhanced admin authorization for Microsoft Entra Connect Sync configuration changes

We're enhancing the security posture of Microsoft Entra Connect Sync by introducing interactive admin authorization for configuration changes. With this update, an authorized administrator will need to sign in and explicitly approve changes to sync settings, ensuring that configuration updates are intentional and made by the right person.

UpcomingMicrosoft Entra IDEntra Connect

Migrate from Microsoft Entra Connect Sync to Microsoft Entra Cloud Sync

As organizations look to strengthen identity security and advance their Zero Trust strategies, many are looking for simpler, more reliable ways to manage hybrid identity. To support these needs, we’re beginning the transition from Microsoft Entra Connect Sync to the cloud‑native Microsoft Entra Cloud Sync - helping reduce on‑premises complexity while improving security, reliability, and day‑to‑day manageability.