Forum Discussion
Rest API For Eventstream could not create resource: Cross-workspace destination(s) found
I am trying to creata an Eventstream through the REST API, but get an error during creation because my Eventhouse destinatiion belong to a diffrent workspace then my Eventstream. Is this a limitation in the REST API for fabric?
I am able to create the same eventstream through the Fabric portal without any problems. If this is a limitation in the REST API is there any plan to implement support for cross workspace destination soon?
Good point arildandasbouve. Agreed to all your points.
The point I was making through doc was it was no where mentioned about cross WS and it is failing in your case , so it is evident that cross Ws is not supported.
REST APIs are still evolving, might be in future it will be possible to have crosss workspace ES.
worth raising a ticket with MS though.
3 Replies
Hello arildandasbouve
Microsoft Fabric enforces strict workspace isolation, meaning that data and resources within one workspace cannot directly interact with those in another workspace through certain APIs, including the Eventstream REST API
This doc explains the operations supported by the Eventstream REST API, including creating and managing Eventstreams within a workspace. It emphasizes that Eventstreams are designed to operate within a single workspace, which aligns with the reported limitation of cross-workspace interaction through the API
https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/eventstream-rest-api
no official information about this feature release yet
Please keep an eye on for latest updates https://learn.microsoft.com/de-at/fabric/fundamentals/whats-new
If this helps please accept the answer and give kudos
Thank you for your quick response, but i can not see any documentation from your references that there is a cross workspace limitstion built in. And why is this limitation not forced on the fabric portal, where this is possible to configure?
And about the workspace isolation argument, there is good arguments for separating eventstreams from destination items like Eventhouse when it comes to capacity isolation and control. So to sum up I do not see why your arguments works only for the API and not for the Portal
Good point arildandasbouve. Agreed to all your points.
The point I was making through doc was it was no where mentioned about cross WS and it is failing in your case , so it is evident that cross Ws is not supported.
REST APIs are still evolving, might be in future it will be possible to have crosss workspace ES.
worth raising a ticket with MS though.
