Hi @srebhan, thank you for your time. We propose using the MSFabric plugin as the output plugin, as Microsoft Fabric is positioned as a standalone product offering (distinct from Azure) and includes components like Eventhouse and Eventstream/Eventhub as part of its underlying storage components. Fabric users should not have to manage multiple plugins or complex configurations to interact with these components. Instead, they can simply provide the connection string and have data seamlessly flushed to the appropriate storage.
As the target audience consists of Fabric users, they will naturally expect plugins that are compatible with Fabric itself, rather than directly with components like Eventhouse or Eventstream.. Additionally, the plugin can be extended to support storage types introduced within the Fabric ecosystem in the future.

@asaharn any update regarding what we discussed on Slack, i.e. to implicitly define the required parameters with the connection string and the plugin will then parse those out without an explicit, endpoint-specific configuration?

Hi @srebhan, Apologies for the delay, I will mostly complete it by the end of this week

@srebhan have pushed the changes

Hi @srebhan, updated the changes.

@asaharn I took the freedom to push some required changes. Let me know if the code is OK for you!

Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip.
Downloads for additional architectures and packages are available below.

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

@srebhan Thankyou. Have checked the changes, we can proceed.

Hi @skartikey I have pushed the changes. Requesting for a re review.

Thankyou @srebhan and @skartikey