As reported by NIFI-2835, the existing GetAzureEventHub processor does not handle partition distribution among nodes in a NiFi cluster, and handling offset information across NiFi restart.
The processor uses PartitionReceiver directly, however, there's another approach to receive events from Event Hub, that is using EventProcessorHost class.
EventProcessorHost uses Azure Storage to store consumer group offset information so that it can distribute consumer load among consumer instances within the same group. Also this way can handle restart and NiFi cluster scale scenario better.
In addition to above enhancements, we could also add Record data model capability to new ConsumeAzureEventHub. Similar to ConsumeKafkaRecord processor.