Exchanging NServiceBus messages with native implementation of Azure Service Bus

Question

Consuming a message published with NServiceBus, using IQueueClient/Functions-ServiceBusTrigger (Microsoft.Azure.ServiceBus)

I'm working in a WebJob using .NET Core and Microsoft.Azure.ServiceBus to consume a message that has been published by a separate service using NServiceBus. My initial approach with this WebJob was to use a class Functions.cs with a method ProcessMessage that uses the attribute ServiceBusTrigger

Below is an example of how my Function.cs looks like:

public class Functions
{
   public Task ProcessAuditLogMessage([ServiceBusTrigger("MyQueue")] 
      Message message)
   {
      var messageBody = Encoding.UTF8.GetString(message.Body);
      var auditLogMessage = JsonConvert
            .DeserializeObject<MyMessage>(messageBody);

      _logger.Information("Hello World");

      return Task.CompletedTask;
    }
}

In Program.cs, I have:

class Program
{
   static async Task Main()
   {
      var serviceCollection = new ServiceCollection();
      serviceCollection.AddWebJobs(o => o.AllowPartialHostStartup = true);

      var builder = new HostBuilder()
         .UseServiceProviderFactory(
              new AutofacServiceProviderFactory(serviceCollection))
         .ConfigureContainer<ContainerBuilder>(b =>
         {
            BuildAutofacContainer();
         })
         .ConfigureWebJobs(b =>
         {
            b.AddServiceBus(o =>
            {
               o.ConnectionString = configProvider.AuditLogServiceBus;
             });
          });

      var host = builder.Build();

      using (host)
      {
         await host.RunAsync();
      }
   }

   private static IContainer BuildAutofacContainer(IServiceColletion 
          serviceCollection)
   {
      ...
   }
}

I was expecting that this logic would consume the messages published in the Queue but so far the messages get moved to the Dead-letter count with a DeadLetterReason: MaxDeliveryCountExceeded and the error description Message could not be consumed after 10 delivery attempts which gives me the indication that at least there is an attempt to get these messages delivered to my consumer.

Unfortunately that's all I have in terms of error messages/logs (I'm in the process to set up some logs from my Azure Dashboard and see if I can get more detailed logs)

Has anyone come across the scenario o having to consume messages, that have been published with NServiceBus, using Microsoft.Azure.ServiceBus instead of NServiceBus (on the consumer side). Maybe I'm missing something...