Role purpose
The Business Systems Administrator keeps the company's business systems running smoothly for everyday users. They are the first point of contact for business-systems questions and the person who keeps Microsoft Dynamics 365 Business Central (BC) correctly configured and up to date.
This is a service and operations role, not an analysis or building role. Its job is to unblock people quickly, keep the systems healthy, and hand anything that needs deeper analysis, automation or a real change over to the Business Automation Analyst.
Together, the Business Systems Administrator (operations and support) and the Business Automation Analyst (analysis and automation) cover what used to be a single, overloaded role — one keeps the lights on, the other makes things better.
Main responsibilities
User support & helpdesk (L1)
First-line support for business-systems users, Business Central in particular.
- receives requests, does initial triage, and distinguishes incidents, bugs, change requests and process problems
- helps users with error messages and warnings (e.g. missing permissions, features not working)
- resolves common cases directly; escalates deeper analysis or changes to the Business Automation Analyst, and vendor-side problems to the software vendor
- keeps users informed of progress and confirms the issue is really resolved
System administration
Administers and configures the entrusted systems and keeps Business Central current.
- manages system configuration, reference data, user settings and access rights
- manages BC users and licenses
- keeps BC on a current, supported version — tracks announced Microsoft updates, informs users in advance, and ensures updates happen on schedule
- keeps BC extensions and installed apps up to date, and verifies they work after installation
Everyday process operations
Keeps the routine running and spots problems early.
- checks that day-to-day processes and data flows work as expected
- identifies recurring problems and deviations and flags them for a proper fix
- helps resolve routine operational problems
Documentation & knowledge (AI-assisted)
Keeps support knowledge cheap to maintain.
- maintains user guides, FAQs and a knowledge base of known problems and their solutions
- uses AI to draft guides, triage and summarize requests, and speed up routine support
Goal & success measures
The role is measured not by tickets closed, but by users being unblocked quickly and by fewer problems recurring. Success shows as:
- users get fast, reliable help and systems stay correctly configured
- BC is always on a supported version, with licenses and access under control
- recurring issues are surfaced and handed over to be fixed at the root
- an up-to-date, genuinely useful knowledge base
- smooth escalation: the right things reach the Business Automation Analyst or the vendor
Ideal profile — who we are looking for
The strongest predictor of success is conscientiousness — reliability and follow-through — combined with patience for users and a calm head during incidents. This is a "system operator with a heart for users", not a builder.
Fits the role
- reliable, organized, and genuinely helpful to users
- stays calm during incidents and deadlines
- comfortable with routine, administration and documentation
Does not fit
- someone who dislikes user contact or routine
- someone who wants to analyze, design or build rather than operate and support
Working with other roles
- Business Automation Analyst — the main partner; receives escalated analysis, automation and change requests, and provides guidance on process and configuration.
- Business Owner — shares information about user problems and needs.
- IT Operations Owner — cooperates on operational and infrastructure problems.
- System Owner — cooperates on change adoption and correct system usage.
This role ensures there is no gap between everyday users and the systems they rely on.