A Business Central administrator for your system, without the hire

What a Business Central administrator does day to day

The administrator is not the accountant and not the developer. The role sits between them. It covers adding and removing users and assigning permission sets. It also covers watching the job queue and managing environments. On top of that, the administrator schedules updates, installs extensions and looks first when something acts oddly.

In a small company, these tasks fall to whoever is best with computers. As a result, they get done late or not at all. Accounts stay active after people leave. Failed jobs go unnoticed, and updates arrive as a surprise. A named administrator with a simple routine prevents most of that.

Users, licenses and permission sets

For Business Central online, you assign licenses in the Microsoft 365 admin center. The user then appears in Business Central. Permission sets control what each person may do inside. Ideally, you assign them through security groups. That way, a new sales user gets the right access from the group, not from a copied profile.

We set up groups by job role. We also remove broad permissions that were handed out during the project. Then we write down who approves access changes. When someone changes jobs or leaves, their access changes with them. The permissions guide on this site explains the mechanics. This service is about doing it consistently.

Environments, copies and updates for your administrator

The admin center lists every production and sandbox environment in your tenant. From there, an administrator creates sandboxes and copies production into one for testing. The same person can restore an environment to an earlier point and set the window for Microsoft updates.

Microsoft ships two major release waves each year, plus smaller monthly updates. First, we choose the update date with you. Next, we refresh a sandbox and confirm that your extensions and integrations still work. Only then does production update. We also remove old sandboxes so they do not confuse people.

Job queues, extensions and telemetry

Much of Business Central runs in the background. Examples are posting batches, cost adjustment, report schedules and integration syncs. Each one is a job queue entry, and each can fail quietly. So we check the queue, read the error, fix the cause and restart the entry. We also set up notices so a failure reaches a person.

Extensions need the same attention. Apps from AppSource apps publish new versions, and custom extensions must stay compatible with each release. Telemetry in Azure Application Insights shows slow pages, long reports and errors that users never mentioned. As a result, we can deal with them before they become complaints.

A Business Central administrator as a service or in-house

Some companies want the role handled for them. In that case, our consultants take on the routine and keep a written log of what changed and why. We also report on open points in a regular call. Your team still decides who gets access and when updates happen. We carry out the work and raise anything that needs a decision.

Others prefer to grow their own administrator. Then we coach a member of your staff through real tasks on your tenant. We leave a short runbook for each duty and stay on hand as a second line. Either way, the knowledge is written down. So it does not sit in one person's head.

Business Central administrator questions

Do we need a full-time Business Central administrator?

Most small and mid-sized companies do not. The duties are real but part-time. Expect a little each week, and more around updates or staff changes. A shared service usually covers it well. So does a trained internal person with outside backup. We help you work out which Business Central administrator setup fits, based on how many users and integrations you run and how often your setup changes.

What access does an outside administrator need?

Microsoft supports delegated administration. It lets a partner manage environments without holding one of your paid licenses. For work inside the application, we use a dedicated account with only the permissions that the agreed tasks require. Every action is then traceable to that account. You can remove the account whenever you wish, and we keep a written list of what it can do.

Is a Business Central administrator the same as a developer?

No. An administrator sets up, monitors and maintains the system. A developer writes AL code. The administrator decides when an extension is installed or updated and checks that it works, but does not write it. We provide both roles, separately or together. Your Business Central administrator never needs to write code. Because the two jobs differ, we keep their access apart as well.

Can you administer an on-premises installation?

Yes. On-premises systems add server tasks that Microsoft handles for online tenants. Examples are database backups, service tier maintenance and applying cumulative updates. So we agree which of those your IT team keeps and which we take on. We put that split in writing, so everyone knows who acts when a server needs attention.

Who decides when updates are applied?

You do, within the period Microsoft allows for each release. We propose a date after testing in a sandbox. You approve it, and then we schedule it in the admin center for a quiet time outside your busy hours. If the date clashes with a close, we move it inside the allowed period and tell your team.

More on running the system

The administrator role overlaps with several other topics. These pages explain the admin center itself, security design and permission mechanics. They also cover the wider managed service that a Business Central administrator can be part of. If you want to see which setup fits your team, the contact page is the next step. For the product detail, see Microsoft Learn: the Business Central administration center.