Small and medium business | Business Central, N...

System User Job Queue

(5) Share

Report

Posted on by SoeBlu

Hi! How can we configure the Job Queues in Business Central to run under the user ID of a system user, without setting up an authentication email within the Office 365 framework?

I have come up with two solutions so far:

1. Temporary Change of Office 365 Authentication Address:
- Temporarily replace the Office 365 authentication address of the system user with that of a real admin user, set up the job queues as the system user, and then have someone else revert the changes. This is cumbersome and problematic if a job crashes.

2. Alternative Authentication Method:
- Set up a separate Business Central instance with a different authentication method to avoid dependency on Office 365. However, I would prefer to avoid this solution.

Are there more efficient approaches to solving this problem?

Thank you!

System: BC23 On-Premise

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Sohail Ahmed 11,095 Super User 2025 Season 2 on at

Like (2)

Report

System User Job Queue

Hope this might be helpful:

To configure Job Queues in Business Central to run under a "system user" without relying on a constantly monitored Office 365 email or complex workarounds:

The most efficient and standard method is to create a dedicated, non-interactive Azure AD user (e.g., svc.bc.jobs@yourdomain.com). This user should be assigned a Business Central license and the necessary permission sets. You then assign this user's ID to the User ID field for each Job Queue entry. This provides a secure, auditable, and stable context for job execution without needing a "real admin" email for authentication or complex instance setups.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 93,438 Super User 2025 Season 2 on at

Like (1)

Report

System User Job Queue

Hi, hope the following can give you some hints.

https://community.dynamics.com/forums/thread/details/?threadid=4b019707-a403-ef11-a1fd-7c1e52001c13

https://community.dynamics.com/forums/thread/details/?threadid=ef624c95-730e-4d0b-940d-ae52c057deb0

Thanks.

ZHU

Was this reply helpful? Yes No
SoeBlu 80 on at

Like (0)

Report

System User Job Queue

You then assign this user's ID to the User ID field for each Job Queue entry.

How can I assign a job queue entry to another user? Not in the standard system without additional programming, right?

I can only start the job queue and then it runs under my user ID.

I think I will do a little programming to make this possible.

Thanks for the answers so far.

Was this reply helpful? Yes No
Matteo Fiocco 258 on at

Like (1)

Report
System User Job Queue

Hi @SoeBlu,

One solid option is to create a dedicated service user with NavUserPassword or Windows authentication, depending on what your environment supports. You can:

Create a new user (e.g. SERVICEUSER) in the Users page.

Set it up with NavUserPassword (with a manual password) or link it to an AD account if you're using Windows auth

Give it the necessary permissions like SUPER and JOBQUEUE.

Then, in your Job Queue Entry, simply set the "User ID" to this user.

If the job doesn’t require user-specific context (like email sending or language settings), you can also leave the "User ID" field blank. In that case, the job runs under the service account that’s running the NST (Business Central Server Tier). This works well for simple background tasks.

The workaround you mentioned with swapping the O365 auth address can technically work, but it’s fragile and risky if a job crashes or the token expires. Spinning up a whole new instance just to avoid O365 also feels a bit heavy unless you’re already going that route for other reasons.

Let me know what auth modes your environment supports and I can help you figure out the cleanest setup.

Cheers,

Matteo

Was this reply helpful? Yes No
SoeBlu 80 on at

Like (0)

Report

System User Job Queue

Hi Matteo!

If the job doesn’t require user-specific context (like email sending or language settings), you can also leave the "User ID" field blank. In that case, the job runs under the service account that’s running the NST (Business Central Server Tier). This works well for simple background tasks.

I don't know how to leave the user ID blank in the standard system. As soon as I restart the job with my now created system user, the user ID is filled with this user.

Cheers,

Was this reply helpful? Yes No