Forum Discussion
Activate Microsoft Fabric Eventstream as a source or destination using Logic App API
I need to build a working setup where Microsoft Fabric Eventstream can be dynamically enabled as both a source and a destination through Logic App API automation.
Currently, I am able to:
Successfully connect and authenticate using Logic Apps.
Retrieve the Eventstream ID, source ID, and destination ID using the Get Definition API.
However, when I attempt to use the Resume API option to activate the Eventstream from Logic Apps, it is not starting as expected. The Eventstream remains inactive, even though the API call executes without errors.
Expected Outcome:
The Eventstream should be activated (resumed) dynamically via Logic App API so that data flow can be initiated between the configured source and destination.
link for refrence:
https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/eventstream-rest-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.
5 Replies
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .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.
Hi Deeksharma
I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.
Thank You.Hi Deeksharma
We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
Hi Deeksharma
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.
Thank You.
