Activate Microsoft Fabric Eventstream as a source or destination using Logic App API

Hi Deeksharma 

Thank you for your question on the Microsoft Fabric Community Forum.

This issue arises because the Resume API alone does not activate a Microsoft Fabric Eventstream unless it has been properly published and is in a valid state. In your setup, the Eventstream remains inactive due to the missing publish step, which means the backend lacks a compiled, deployable version to start. The Resume API does not accept parameters such as startType; it only requires a straightforward POST request with authentication. To address this, please ensure your Logic App uses a system-assigned managed identity with Contributor or higher permissions on the Fabric workspace. The Eventstream should have at least one healthy source and destination before proceeding. The recommended process is to publish the Eventstream using the publish API, then resume it with the resume API. If the Eventstream remains inactive after a 200 OK response, consider a short retry interval, as backend provisioning may take some time. Following these steps will help ensure successful activation and data flow between your configured source and destination through Logic App API automation.

For further guidance, refer to the official documentation

Topology - Resume Eventstream - REST API (Eventstream) | Microsoft Learn

I hope this information is helpful. . If you have any further questions, please let us know. we can assist you further.

Regards,

Microsoft Fabric Community Support Team.