Container Application Job not triggered when a message arrives to the Service Bus

Question

I've set up a Container App Job intended to trigger when a message arrives in an Azure queue. Despite following the instructions and trying multiple configurations, the job is not running as expected. Since this is specifically a Container App Job rather than a standard Container App, I'm wondering if there are different configuration requirements.

The current scaling rules for the Container App Job are:

Any guidance or insight would be greatly appreciated, as most of the available documentation focuses on Container Apps rather than Container App Jobs specifically.

Answer 1

Hi Dante Loayza (Admin),

Thanks for reaching out to Microsoft Q&A.

The job isn't triggering because the Service Bus event trigger isn't being picked up by KEDA. This usually happens when the wrong connection string is used (namespace instead of queue/topic level), the scale rule metadata is incorrect (queueName=[REDACTED], namespace=[REDACTED]", or auth binding), or the managed identity lacks Service Bus Data Receiver permissions.

In some cases, suspending or updating the job breaks the trigger entirely, and recreating the Container App Job is the only fix. If the job runs when started manually, the container is fine and the problem could be in the Service Bus trigger configuration.

Hope this helps!

---

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know