Hello Everyone, We are currently conducting tests and POCs to push (and potentially read) data from Kafka brokers and Azure Event Hubs. Event Hubs Test Our Event Hubs test worked successfully: We added the following NARs as extensions: nifi-azure-nar-2.4.0.nar nifi-azure-services-api-nar-2.3.0.nar After a manifest refresh in EFM, we were able to use the PutAzureEventHub processor. We configured the flow, published the new version, and confirmed that the MiNiFi agent could successfully send data to the Event Hub. Kafka Test Issue We are now trying to create a flow in MiNiFi to push data into a Kafka topic. We followed the same steps as the Event Hubs test and added the following NAR files: nifi-kafka-service-api-nar-2.4.0.nar nifi-kafka-nar-2.4.0.nar What works: After refreshing the manifest, we can see two Kafka processors, including PublishKafka, which we need for the test. What doesn’t work: We cannot add the KafkaConnectionService, which is required to configure the PublishKafka processor. Even after adding the nifi-kafka-service-api-nar-2.4.0.nar and performing a refresh manifest, the KafkaConnectionService controller service does not appear. We also tried Kafka NARs version 2.2.0, with the same result. Environment Details: MiNiFi version: Java 2.24.08 EFM version: 2.2.0.0-86 All NARs were downloaded from the Cloudera Sonatype Nexus repository. Request Could you please advise on: Are we missing a specific Kafka NAR or dependency to get KafkaConnectionService to appear? Is there a version compatibility issue between MiNiFi 2.24.08, EFM 2.2.0.0-86, and the NARs we are using? What steps are recommended to enable Kafka connectivity in this setup? Best regards ... View more