Microsoft Fabric: Microsoft.Fabric.ItemReadSucceeded and ItemReadFailed events will retire [MC1000268]

Message ID: MC1000268

In Microsoft Fabric, workspace item events in Fabric Real-Time hub (preview) allow you to receive notification when actions (such as when new artifacts are created or existing artifacts are deleted) occur for your workspace items. These events can be consumed via Fabric Eventstreams or used to alert on other actions or workflows in Fabric, such as running a data pipeline or sending an email notification using Fabric Data Activator alerting capabilities.

On March 17, 2025, the event types Microsoft.Fabric.ItemReadSucceeded and Microsoft.Fabric.ItemReadFailed, which are part of workspace item events in Fabric Real-Time hub (preview) will not be available for new event subscriptions. If users in your organization try to create new subscriptions after March 17, 2025, they will not be able to select these event types.

On March 17, 2025, the event types Microsoft.Fabric.ItemReadSucceeded and Microsoft.Fabric.ItemReadFailed will not be available as part of workspace item events in Fabric Real-Time hub (preview) for existing event subscriptions created prior to March 17, 2025. If users in your organization consume these event types in subscriptions, they will stop receiving the events on March 17, 2025.

Microsoft Fabric: Microsoft.Fabric.ItemReadSucceeded and ItemReadFailed events will retire [MC1000268]

We will share plans to replace the retiring events in a future Message center post.

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation as appropriate, and share details about Workspace item events.

Learn more about Fabric Real-Time Hub: Introduction to Microsoft Fabric Real-Time hub – Microsoft Fabric | Microsoft Learn

Source: Microsoft

Mike Rosoft

7 February 2025, 11:40 pm

The retirement of the Microsoft.Fabric.ItemReadSucceeded and ItemReadFailed events is certainly a noteworthy change for both admins and users within the Microsoft Fabric ecosystem. As we approach the March 17, 2025 deadline, it’s important to consider how this update will impact the day-to-day operations for both groups.

For admins, the good news is that no immediate action is required on your part. The transition will occur automatically, which means you can focus on more pressing matters—like deciphering the latest “tech jargon” or figuring out how to keep the coffee flowing in the break room! However, it’s crucial to notify your users about this change and update any related documentation. This proactive communication will help alleviate any confusion when these event types become unavailable.

On the user side, the impact may be a bit more pronounced. Users who rely on these specific event types for monitoring workspace items will need to adjust their workflows accordingly. After March 17, 2025, they will no longer receive notifications for item reads, which could affect how they track and respond to changes within their projects. However, the promise of new replacement events in a future Message Center post gives us something to look forward to. Change can be daunting, but it can also open the door to new opportunities!

In terms of overall impact, this update could serve as a catalyst for users and admins alike to explore the broader functionalities of the Fabric Real-Time Hub. Embracing change often leads to innovation, and who knows? You might just discover a more efficient way to manage your workspace items.

So, what do you think? Are you feeling optimistic about these changes, or do you have concerns? Let’s hear your thoughts in the comments below! For more insights on Microsoft Fabric and other updates, be sure to check out more posts at mwpro.co.uk.

1 Comment

Mike Rosoft


7 February 2025, 11:40 pm

The retirement of the Microsoft.Fabric.ItemReadSucceeded and ItemReadFailed events is certainly a noteworthy change for both admins and users within the Microsoft Fabric ecosystem. As we approach the March 17, 2025 deadline, it’s important to consider how this update will impact the day-to-day operations for both groups.

For admins, the good news is that no immediate action is required on your part. The transition will occur automatically, which means you can focus on more pressing matters—like deciphering the latest “tech jargon” or figuring out how to keep the coffee flowing in the break room! However, it’s crucial to notify your users about this change and update any related documentation. This proactive communication will help alleviate any confusion when these event types become unavailable.

On the user side, the impact may be a bit more pronounced. Users who rely on these specific event types for monitoring workspace items will need to adjust their workflows accordingly. After March 17, 2025, they will no longer receive notifications for item reads, which could affect how they track and respond to changes within their projects. However, the promise of new replacement events in a future Message Center post gives us something to look forward to. Change can be daunting, but it can also open the door to new opportunities!

In terms of overall impact, this update could serve as a catalyst for users and admins alike to explore the broader functionalities of the Fabric Real-Time Hub. Embracing change often leads to innovation, and who knows? You might just discover a more efficient way to manage your workspace items.

So, what do you think? Are you feeling optimistic about these changes, or do you have concerns? Let’s hear your thoughts in the comments below! For more insights on Microsoft Fabric and other updates, be sure to check out more posts at mwpro.co.uk.

1 Comment

Leave a Reply Cancel reply