Forum Discussion
Advocate IIData Activator rule creation fails due to existing system topic
Hi Gopi, thanks for the answer. We did find a workaround which was to disable Defender on the storage account, which in turn deleted the Event Grid and system topic. We then went through the Data Activator wizard, and then re-enabled Defender, which added an event subscription to the system topic created by Data Activator.
Super User
We’ve run into this same issue, and the behaviour you’re seeing is expected. Data Activator tries to create its own Event Grid system topic for the storage account, but because Windows Defender for Storage already created one for that same account, the creation fails. Event Grid only allows one system topic per resource, so Data Activator simply can’t create another one on top of it.
Right now Data Activator doesn’t support reusing an existing system topic, and that’s why the wizard fails straight away. Nothing is wrong with your setup — it’s just a limitation of how system topics work today.
The only reliable workaround we’ve been able to use is to keep the Defender-created system topic and attach your own Event Grid subscription to it. From there, send events to something lightweight like a Logic App or Function, and have that trigger your Fabric pipeline. It works fine in production and avoids touching the Defender integration.
Hopefully Microsoft adds support for connecting Data Activator to an existing system topic in the future, but at the moment, this is the only practical way forward.
Hope this helps.
– Gopi Krishna
Advocate IIHi Gopi, thanks for the answer. We did find a workaround which was to disable Defender on the storage account, which in turn deleted the Event Grid and system topic. We then went through the Data Activator wizard, and then re-enabled Defender, which added an event subscription to the system topic created by Data Activator.