Co-Managed IT for Dental Groups: Who Does What and What It Costs
Picture a dental group with nine offices, one IT manager, and a renewal notice from the practice management vendor on his desk. He built the network at office one, knows every front-desk login by heart, and has not taken a full week off since the fourth acquisition. Leadership wants a security report for the cyber-insurance renewal and a technology plan for office ten. He wants help that does not replace him. Nobody has written down who owns what.
This guide gives you that split. It sets out the three shapes co-managed arrangements take, a RACI table across thirteen areas of dental IT work, who should own the tools and the admin accounts, how escalation runs when your manager is asleep or on leave, who produces the security evidence and keeps it, how co-managed plans are priced in the market, the contract terms to insist on, a scored fit test, and a 90-day plan for the move. Regulation text is quoted from the Cornell Legal Information Institute, pricing sources are named, and everything was read on 18 November 2026.
Co-managed IT for a dental group means your IT manager and a dental IT provider share the work under a written split: your person keeps the offices, the people and the vendor relationships, the provider runs monitoring, security tooling, backups, after-hours response and project depth, and one party is accountable for every task. The written split is the product.
- Co-managed IT is a written split between your IT manager and a dental IT provider with exactly one accountable party per task; the split is the product.
- The provider should be accountable for anything that must run when your manager is asleep or on leave: monitoring, patching, servers, network, security operations, backups and after-hours response.
- The group owns every licence, tenant, credential and document; provider engineers use named accounts, and Microsoft's own guidance says fewer than five Global Administrators plus two sealed emergency accounts.
- The HIPAA Security Rule requires the group to identify its own security official; the provider produces most technical evidence, the group keeps it, and documentation is retained for six years.
- Meriplex's and BCS365's pricing guides, read on 18 November 2026, both price co-managed plans at $45 to $175 per user per month; dental offices often run more devices than staff, so per-device or scoped pricing usually fits better. No Legend price is given.
- Score the fit: seven or more points means co-managed; three or fewer means you have a capable person with a laptop, and a fully managed plan is the better buy.
In this guide
- What is co-managed IT for a dental group, and how is it different from fully managed IT?
- Who does what? The co-managed RACI for a dental group
- How should tools and admin access be shared?
- How does escalation and after-hours coverage work with one IT manager?
- Who owns security, and who produces the audit evidence?
- How are co-managed IT plans priced in the market?
- What contract terms should a dental group insist on?
- When does co-managed beat fully outsourced IT, and when does it not?
- What do the first 90 days of a co-managed arrangement look like?
- The IT side: what the provider should be doing that your manager cannot see
- What to ask your IT provider about a co-managed plan
- How Legend Networking works with dental groups
- Frequently asked questions
- The bottom line
What is co-managed IT for a dental group, and how is it different from fully managed IT?
Co-managed IT is an arrangement in which a dental group's own IT employee and an outside dental IT provider divide the IT work under a written responsibility split, with one accountable party for each task. Fully managed IT gives the provider every task; an in-house team gives the employee every task; co-managed assigns each task on purpose.
The word "co-managed" hides three quite different arrangements. Which one you are buying decides the price, the contract and whether your IT manager reads the proposal as help or as a threat.
| Shape | Your IT manager keeps | The provider takes | Best for |
|---|---|---|---|
| Internal lead, outside engine | The offices, staff requests, vendor relationships, onboarding, the technology plan | The monitoring platform, patching, security tooling, backups and restore tests, after-hours response, documentation, project delivery | Groups of roughly four to twenty-five offices with one or two IT staff |
| Internal helpdesk, outside infrastructure and security | First-line tickets, moves and changes, imaging workstation care, training | Servers, network, firewalls, identity, security operations, backup, the technical evidence pack | Groups whose IT staff came from a front desk or an office "IT guy" role |
| Internal infrastructure, outside helpdesk overflow | Servers, network, security standards, projects | First-line helpdesk at set hours, after-hours response, overflow during rollouts and acquisitions | Larger groups with a network engineer who should not be resetting passwords |
Two things are not co-managed IT, although they get sold under the name. The first is your practice management or imaging vendor's remote support: it covers its own product and nothing around it. The second is a break-fix technician your manager calls when stuck; nobody is accountable between calls, which is the whole problem managed IT vs break-fix sets out. If you are still deciding whether to keep an internal person at all, the arithmetic for what an in-house IT person costs a dental practice is in a separate guide; if you want a provider to own every task, that is managed IT services for dental practices, not this model.
Who does what? The co-managed RACI for a dental group
A RACI names, for each area of work, who is Responsible for doing it, who is Accountable for the result, who is Consulted before a decision and who is Informed afterwards. In a co-managed dental group every row has exactly one Accountable party, and the provider is Accountable for anything that must keep running when your IT manager is unavailable.
The table below is the common split for the first shape above (internal lead, outside engine). Edit it row by row; the editing is the negotiation. R = Responsible, A = Accountable, C = Consulted, I = Informed.
| Work area | IT manager | Dental IT provider | Office manager (each location) | Group leadership | Note |
|---|---|---|---|---|---|
| Helpdesk, first line: staff requests, how-do-I questions, new user set-up | R, A | C | I | I | Flips to the provider under the third shape |
| Helpdesk, second and third line: server, network and security faults | C | R, A | I | I | One phone number for the front desk regardless of who answers |
| Endpoints: workstations, imaging PCs, patching, replacement cycle | C | R, A | I | I | Patch rings exclude imaging exceptions agreed in writing |
| Servers and the practice management database | C | R, A | I | I | Includes the clearinghouse and reporting services that run on the server |
| Network: firewalls, switches, Wi-Fi, internet circuits | C | R, A | I | I | One firewall template per office; exceptions in a register |
| Identity and email: Microsoft 365, directory, multifactor sign-in | R for joiners and leavers | A for the tenant and its policies | C | I | HR tells the IT manager; the provider disables within the agreed window |
| Security operations: endpoint detection, log review, alerts, incident response | I | R, A | I | I at incident | The incident reporting path is in the agreement |
| Backup and restore testing | I | R, A | I | I | Restore evidence every month, per office |
| Software and imaging vendors (Dentrix, Eaglesoft, Open Dental, Denticon; DEXIS, Carestream, Planmeca) | R, A for the relationship and the ticket | C on the environment, drivers and remote access | C | I | The vendor talks to one person; that person talks to the provider |
| Projects: new office, acquisition integration, server replacement | A for scope and budget | R for delivery | C | I | Priced per project, never silently inside the monthly fee |
| Compliance evidence: risk analysis input, access reviews, training records | A | R for the technical evidence | R for local records | I | See the evidence table below |
| Phones, internet contracts, printers, cameras, door controls | R, A | C | C | I | Often the manager's biggest time sink; keep it unless the provider prices it |
| Technology plan and budget | R | C | I | A | Leadership signs; the manager writes; the provider supplies the asset data |
How to read and edit the table
Three rules keep the table honest. First, one A per row: if both sides are accountable, neither is, and the Monday-morning imaging failure becomes a conversation about whose job it was. Second, the A follows the hours: whatever must be watched, patched or restored in the middle of the night or during your manager's leave belongs to the side that is staffed in the middle of the night. Third, the vendor row has a single face: your practice management and imaging vendors should always hear from the same person, because scanners cause a large share of the support calls in a dental office, and .NET, TWAIN and driver updates are a common trigger, so careful teams hold those updates for the first months after a new scanner or imaging release. Driver blame travels between three companies unless one person owns the ticket. The server row carries the most hidden detail, from the practice management database to the services the clearinghouse depends on; who fixes what on a dental server takes that row apart.
If your group centralizes some functions and leaves others to each office, read the table alongside what dental groups centralize and what stays local: the RACI here is the split between your IT manager and the provider, while that guide covers the split between the group and its offices. What a group-wide IT arrangement should cover across every location is set out on Legend's DSO IT support page.
How should tools and admin access be shared?
Each tool has one owner, the group owns every licence, tenant and admin identity, and the provider's engineers use named accounts with multifactor sign-in that the group can revoke within the hour. Shared logins, a technician's personal admin account, and a Microsoft 365 tenant registered in the provider's name are the three faults a co-managed review finds first.
The table is the second schedule to attach to the agreement. "Group" means the dental group as the legal owner, whoever administers the tool day to day.
| Tool | Licence or tenant in whose name | Day-to-day administrator | Read or audit access | What happens at exit |
|---|---|---|---|---|
| Remote monitoring and management platform | Usually the provider's platform; the asset data is the group's | Provider | IT manager | Asset inventory exported; agents removed on a dated schedule |
| Endpoint detection and antivirus | Group, or provider's bundled licence stated in the contract | Provider | IT manager | Replacement product in place before removal |
| Backup software and storage | Group | Provider | IT manager | Backup copies and encryption keys stay with the group |
| Microsoft 365 tenant and directory | Group | IT manager and named provider accounts | Leadership through the admin audit log | Provider accounts disabled; emergency-access accounts remain the group's |
| Password vault | Group | Both, in separate folders with shared folders for the handover set | Leadership for emergency access only | Provider folder transferred, then rotated |
| Documentation: network diagrams, runbooks, exception register | Group | Both | Leadership | Exported in an open format, current to the exit date |
| Ticketing system | Provider or group, stated in the contract | Both | Leadership reads the monthly report | Ticket history exported |
| Firewalls, switches and Wi-Fi controllers | Group owns the hardware and the subscriptions | Provider | IT manager | Configurations exported; admin credentials rotated |
| Vendor remote access (practice management, imaging, phones) | Group approves each vendor | IT manager grants per session or per window | Provider sees the session logs | Standing vendor accounts reviewed and closed |
Two published rules settle most arguments about admin accounts. Microsoft's own guidance for Microsoft Entra roles says it "recommends that you assign the Global Administrator role to fewer than five people in your organization", that organizations should keep "two cloud-only emergency access accounts permanently assigned the Global Administrator role" for "break glass" scenarios, and that administrators should hold only the permissions their task needs. Count your Global Administrators today; in a co-managed group the answer is usually your manager, two provider engineers and the two emergency accounts, and no one else. The Security Rule's technical safeguards, read at the Cornell Legal Information Institute, require a covered entity to "Assign a unique name and/or number for identifying and tracking user identity", which is the sentence that ends shared admin logins, and shared payer portal logins in dental groups with them.
How does escalation and after-hours coverage work with one IT manager?
Escalation in a co-managed dental group follows a written severity ladder: the front desk calls one number, first line is answered by whichever side owns it in those hours, anything touching a server, the network or security goes to the provider, and after hours the provider takes every call. Your manager is a named escalation contact, never the only one.
| Severity | Example | First response | Escalates to | Nights, weekends and the manager's leave | Who tells the offices |
|---|---|---|---|---|---|
| S1: clinic stopped | Server down, ransomware suspected, an office with no network or phones | Provider, from the monitoring alert or the single number | Provider lead, IT manager and group leadership together | Provider | IT manager; provider if the manager is unreachable |
| S2: one operatory or function down | Sensor not capturing, an imaging PC off, the sterilisation printer dead | IT manager or provider first line, by the RACI | Provider second line | Provider helpdesk | Office manager |
| S3: degraded | Slow practice software every morning, intermittent Wi-Fi in two operatories | First line logs it; provider investigates | Provider engineer with the IT manager consulted | Next provider shift | Office manager |
| S4: requests | New hire, moved operatory, a how-do-I question | IT manager | Provider only if a tool or policy changes | Next business day | Not needed |
The one-person risk is a common reason groups look at co-managed IT in the first place. Write a leave rule into the agreement: when the IT manager is on leave or sick, the provider is first response for every severity, the office managers are told the date range in advance, and the manager's phone is not the escalation path. Then test it: on a day your manager is out, have an office call the number and time what happens. What the agreement should say about response and escalation is set out in what a dental IT SLA should define; this guide does not state times, because the right targets depend on your hours and your tolerance for a closed column.
Who owns security, and who produces the audit evidence?
The dental group owns security. The HIPAA Security Rule requires a covered entity to "Identify the security official who is responsible for the development and implementation of the policies and procedures", and that official is yours, not the provider's. The provider produces most of the technical evidence, the group keeps it, and both can show it within a day.
The table lists the evidence a group is most often asked for by an insurer, a payer, a buyer or a regulator, the regulation text each item answers (quoted, not interpreted), and who produces and keeps it in a co-managed arrangement.
| Evidence item | Regulation text it answers (45 CFR) | Produced by | Kept by | Cadence |
|---|---|---|---|---|
| Risk analysis | 164.308(a)(1)(ii)(A): "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information" | Provider drafts the technical part; the security official and IT manager own it | Group | Yearly, and after a new office, a new system or an incident |
| Activity and log review | 164.308(a)(1)(ii)(D): "regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports" | Provider | Group | Monthly report |
| Access list, joiners and leavers | 164.308(a)(3)(ii)(C) termination procedures; 164.312(a)(2)(i) unique user identification | IT manager on the HR trigger; provider disables accounts | Group | Per leaver; access review quarterly |
| Log-in monitoring and multifactor coverage | 164.308(a)(5)(ii)(C): "Procedures for monitoring log-in attempts and reporting discrepancies"; (D) password management | Provider | Group | Monthly |
| Backup and restore test | 164.308(a)(7) contingency plan; (ii)(D): "periodic testing and revision of contingency plans" | Provider | Group | Monthly restore evidence per office |
| Incident log and reporting | 164.308(a)(6) security incident procedures; 164.314(a)(2)(i)(C): the business associate contract must require the associate to "Report to the covered entity any security incident of which it becomes aware" | Both | Group | Per incident |
| Periodic evaluation | 164.308(a)(8): "Perform a periodic technical and nontechnical evaluation" | Both | Group | Yearly |
| Workforce training records | 164.308(a)(5) security awareness and training | Office managers | Group | Yearly and at hire |
| Business associate inventory and agreements | 164.308(b) business associate contracts | IT manager | Group | Yearly review |
Two consequences follow from "kept by the group". The documentation rule at 164.316(b)(2)(i) requires a covered entity to "Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later", so evidence that lives only in a provider's portal is a problem the day the contract ends. And the cyber-insurance renewal that started this conversation asks for the same items; dental cyber insurance requirements maps the usual questionnaire to the controls behind it. This guide quotes the rule as published and does not interpret it; your security official and counsel read it for your group.
How are co-managed IT plans priced in the market?
Co-managed IT is priced per user, per device, as a tiered package or as a fixed monthly fee for a scoped list of responsibilities, with projects and after-hours cover often billed separately. Pricing guides from two MSPs, Meriplex and BCS365, read 18 November 2026, both put co-managed plans at $45 to $175 per user per month; neither figure is dental-specific.
| Pricing model | How it is counted | Fits a dental group when | Watch for |
|---|---|---|---|
| Per user | A monthly fee for each staff member supported | Staff count is stable and most people have one device | Operatories: a dental office often runs more devices than staff (operatory PCs, imaging stations, shared front-desk machines), so per-user quotes invite scope disputes over imaging PCs and shared stations |
| Per device | Workstations, servers and network devices each carry a monthly fee | Device-heavy offices where the count is known and audited | The bill grows with every operatory; servers and firewalls carry their own rates |
| Tiered package | Basic, standard and premium bundles | The group wants a simple comparison between proposals | After-hours response often sits only in the top tier |
| Scoped fixed fee | The RACI priced row by row, one monthly total | The internal team is mature and the split is clear | Scope creep without change control; everything outside the schedule is a project |
| Project rates | Hourly or fixed-fee, outside the monthly total | New offices, acquisitions, server or network replacement | Hourly estimates that have no cap |
The published figures, with their sources named. Meriplex's 2026 budgeting guide says "Co-managed IT pricing typically ranges from $45 to $175 per user per month for mid-market organizations", lists per-device rates of "$30–$55" for a workstation, "$90–$180" for a server and "$25–$45" for a network device, and prices project work "at rates ranging from $150–$275/hour or scoped as fixed-fee projects". BCS365's pricing guide gives the same per-user band, "between $45 and $175 per user per month", puts fully managed plans at "between $150 and $400 per user each month", and warns that "Many basic co-managed plans only include support during regular business hours", and that after-hours is often "offered as part of a higher-tier plan or as a separate add-on"; it also says the price rises with each responsibility the provider takes on. Both are general-business guides; a dental group's device-to-user ratio pushes it towards per-device or scoped pricing.
The other half of a co-managed budget is your own person. The Bureau of Labor Statistics' Occupational Employment and Wage Statistics for May 2025, read through the BLS public data API on 18 November 2026, put the national median annual wage at $61,860 for computer user support specialists, $76,220 for computer network support specialists and $175,140 for computer and information systems managers. Add employer costs, tools and leave cover; the loaded arithmetic is worked through in the in-house cost guide linked above. Where the money leaks across a growing group, licence by licence, is the subject of hidden IT costs in dental groups.
This guide gives no Legend price. A co-managed quote depends on which rows of the RACI move, how many offices and devices are in scope and what hours the provider covers, and the only honest number is the one written against your schedule.
What contract terms should a dental group insist on?
The agreement should attach the RACI as its scope schedule, name the escalation path and the after-hours definition, keep every licence, tenant, credential and document in the group's name, include a business associate agreement with incident reporting, price the onboarding of acquired offices, and spell out exit assistance. If a term is not written, it has not been bought.
Scope and service
- The RACI and the tool table are attached as schedules, and a change to either goes through a dated change-control note signed by both sides.
- "After hours", "holiday" and "manager on leave" are defined, with the provider as first response in each case.
- Response and escalation targets are written per severity, in the form what a dental IT SLA should define describes, and the agreement says what happens when they are missed.
- The monthly report pack is listed item by item: patch state by office, backup and restore evidence, open risks, access changes, tickets by category, and the exception register.
Ownership and access
- Every licence, tenant, domain and subscription is registered to the group; where the provider's platform is used, the data export format and timing at exit are stated.
- Provider engineers use named accounts; shared or generic administrator accounts are prohibited in the contract, not just in practice.
- Emergency-access credentials are held by the group in its own vault.
- Documentation is the group's property and is kept current as a deliverable, not a favour.
Security and reporting
- A business associate agreement is signed before any access, and it carries the incident-reporting duty quoted in the evidence table above.
- Subcontractors who will touch systems or data are named, and the agreement says how they are bound.
- The provider states where logs and backups are stored and for how long.
Growth and exit
- Onboarding a new or acquired office is priced in the agreement, with the inventory and access steps that IT due diligence on an acquired practice lists, so the tenth office does not arrive as a surprise invoice. The week-by-week work after closing is laid out in the IT integration checklist for an acquired dental office.
- Term, notice and renewal are plain, and exit assistance is written: a handover period, credential rotation, agent removal, and the exports in the tool table. The practical sequence is in switching dental IT providers without downtime.
- No clause lets the provider withhold documentation, credentials or data over a disputed invoice.
When does co-managed beat fully outsourced IT, and when does it not?
Co-managed beats fully outsourced IT when the group employs someone with real IT skill, has enough offices to keep that person busy with people and projects, and wants local knowledge kept in house. It loses when the "IT manager" is an office manager with a laptop, the person is about to leave, or leadership wants one party to hold responsible.
Score your group. Give one point for each "yes".
| Question | Yes | No |
|---|---|---|
| Does your internal person hold real infrastructure skills (servers, networks, identity), not only front-line fixing? | 1 | 0 |
| Do you have four or more offices, or a plan to get there within two years? | 1 | 0 |
| Is there enough people-facing work (onboarding, training, moves, vendor calls) to fill most of that person's week? | 1 | 0 |
| Does leadership want the technology plan written inside the company? | 1 | 0 |
| Would losing your internal person tomorrow stop the group, rather than slow it? | 1 | 0 |
| Does the group already own its tenant, domains and licences? | 1 | 0 |
| Can your internal person describe today where backups go and when a restore was last tested? | 1 | 0 |
| Will your internal person accept a written RACI in which the provider is accountable for several rows? | 1 | 0 |
| Is anyone watching the network outside clinic hours today? | 0 | 1 |
| Has the group had a security questionnaire, audit or insurance renewal it struggled to answer in the last year? | 1 | 0 |
Seven or more points: co-managed fits, and the first shape in the opening table is the starting split. Four to six: co-managed can work, but start with the second shape and move rows to the internal side as skills are proven. Three or fewer: you do not have an IT manager, you have a capable person with a laptop; a fully managed plan with that person as the provider's single point of contact is usually the better buy, and the questions for choosing one are in how to choose a dental IT company. If the group first needs an outside view of its estate rather than an ongoing split, that is the job described in what a dental IT consultant does and when to hire one. Whichever way the score falls, the provider half still has to be chosen on evidence; the lists of best dental IT companies are a starting shortlist, not an answer.
Co-managed also tends not to fit in three situations the score does not catch. When your internal person has given notice or is close to retirement, sign a fully managed plan now and convert later; a co-managed split written around a departing person is rewritten within the year. When the group's leadership wants a single party to call when the clinic stops, co-managed divides that call by design. And when the internal person is the owner's relative or an associate dentist, the RACI becomes a family conversation; put it in writing anyway or choose the fully managed route. Where the technology plan itself should sit as the group grows, and in what order to standardize, is the subject of DSO technology strategy.
What do the first 90 days of a co-managed arrangement look like?
The first 90 days turn the signed RACI into a working split: the provider inventories every office and account, the two sides agree the exceptions, tooling and identities are consolidated, the escalation ladder is tested on a real day, and the first monthly report pack lands in front of leadership. Nothing clinical changes in that period.
- Days 1 to 15: inventory and access audit. The provider's agents go on every workstation, server and network device, and every administrator account, vendor remote-access account and shared login is listed. The IT manager supplies the vendor contacts and the local quirks the inventory cannot see.
- Days 10 to 30: the RACI and tool table become schedules. Each row is confirmed or edited, exceptions (an imaging PC that cannot be patched, a legacy sensor driver) go into the register, and the business associate agreement and change-control note are signed.
- Days 20 to 45: identity clean-up. Global Administrators are cut to the agreed names, the two emergency-access accounts are created and sealed, multifactor sign-in is enforced on every administrator and remote-access account, and leavers found in the inventory are disabled.
- Days 30 to 60: backup, monitoring and patching move to the provider. A restore test is run per office and the evidence filed; patch rings are set with the imaging exceptions; the monitoring thresholds are tuned so the IT manager is not woken by noise.
- Days 45 to 75: the escalation test. On a day the IT manager is out, an office calls the single number with a staged S2 fault, and the timeline is written up against the ladder. The leave rule is fixed where it failed.
- Days 60 to 90: the first report pack and the plan. The provider delivers the first monthly pack, the IT manager presents it with the exception register to leadership, and the technology plan for the next office is drafted from the asset data rather than from memory.
The IT side: what the provider should be doing that your manager cannot see
Most of a co-managed provider's work is invisible from inside an office, which is why the monthly report matters more than the helpdesk greeting. These are the things that should be happening every month in a dental group, and the line in the report that proves each one.
- Monitoring that watches dental things. Beyond disk and CPU: the practice management database service, the clearinghouse and reporting services on the server, the imaging acquisition services, the backup job on every server, the firewall tunnels between offices. Report line: alerts raised, by office, with time to acknowledge.
- Patch rings with dental exceptions. Front-desk and admin machines patch first; servers patch in a maintenance window; imaging workstations running sensor and CBCT software from DEXIS, Carestream, Planmeca or Dolphin patch only after the vendor's compatibility note, and the exception register says which machines and why. Report line: patch state by office, exceptions with an expiry date.
- Restores, not backups. A backup that has never been restored is a hope. One restore per office per month, of a real file set and periodically of a whole server to a sandbox, with the time it took. Report line: restore evidence with dates.
- Logs kept and read. Sign-in logs, administrator actions, firewall logs and endpoint alerts retained for the period the agreement states, and the review recorded, because the Security Rule text quoted above asks for records to be "regularly" reviewed.
- Vendor remote access under control. Standing vendor accounts closed; access granted per session or per window and logged; the practice management, imaging and phone vendors each hear from one named person.
- Identity hygiene. Global Administrator count, multifactor coverage, stale accounts and shared mailboxes with sign-in enabled, checked monthly against the agreed numbers.
- Documentation that moves with the estate. Network diagrams, firewall templates, the per-office standard and the exception register updated the week something changes, not the quarter after.
- Cost lines. Licences by office, devices approaching end of support, contracts renewing in the next 90 days, so the IT manager's plan rests on data rather than recollection.
What to ask your IT provider about a co-managed plan
About the split
- Which rows of our RACI would you take, which would you refuse, and why?
- Who on your side is accountable for the rows you take, by name and role?
- How do you handle a task that falls between our IT manager and your team on the day it happens?
About access and ownership
- Will every one of your engineers use a named account with multifactor sign-in in our tenant, and can we see the sign-in log?
- Which tools are licensed in our name and which in yours, and what do we export at exit?
- Where do our backups and encryption keys live, and who else can reach them?
About hours and escalation
- What exactly happens when our IT manager is on leave and an office's server stops before the first patient arrives?
- Who tells our offices during an outage, and in what order are our people called?
- Which severities do you answer outside clinic hours under the plan we are discussing, and which are an add-on?
About evidence and growth
- What is in your monthly report pack, and can we see a real one with another group's name removed?
- How do you price the onboarding of an acquired office, and what is your inventory and access checklist for it?
- How many Global Administrators would our tenant have after your onboarding, and who are they?
How Legend Networking works with dental groups
Legend Networking is a Dallas-based dental IT company that has served over 3,500 practices since 2004, with 22+ years in dental IT. Legend provides 24/7 monitoring and a helpdesk staffed 24/7 at 1-800-794-1588, with in-house engineers and no outsourced first-level triage. Onsite dispatch is by appointment across served dental markets, and support is remote-first nationwide. Legend supports the IT environment for the practice software Dentrix, Eaglesoft, Open Dental and Archy, and for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, which are the vendor rows of the RACI above.
The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. For the kind of work that sits in the provider column, see a group technology upgrade covering computers, server infrastructure, networking, software and security, and for where Legend's dental IT support is delivered, see the dental IT support locations.
Frequently asked questions
What is co-managed IT support, in plain terms?
Co-managed IT support is an arrangement in which an organization's own IT employee and an outside IT provider share the work under a written split of responsibilities, with one party accountable for each task. In a dental group the employee usually keeps the offices, staff requests and vendor relationships, and the provider runs monitoring, security, backups and after-hours response.
Does a dental group with an IT manager still need a dental IT company?
Usually, yes, because one person cannot be awake every hour, hold every specialism and take leave. The question is which tasks move, not whether any do. A dental-specific provider also brings the vendor and imaging knowledge the RACI's vendor row depends on, so the group's manager is not learning sensor drivers during a clinic day.
What should the IT manager keep, and what should the provider take?
The manager keeps what needs local knowledge and presence: first-line requests, onboarding, training, moves, vendor relationships and the technology plan. The provider takes what must run every hour and needs tooling: monitoring, patching, servers, network, security operations, backup and restore testing, after-hours response, and the technical evidence pack. Edit the RACI from there.
Who is the HIPAA security official in a co-managed arrangement?
Someone inside the dental group. The Security Rule text at 45 CFR 164.308(a)(2) requires the covered entity to identify the security official responsible for its policies and procedures; an outside provider is a business associate, not that official. The provider produces much of the technical evidence and reports incidents under the business associate agreement, while the official owns the program.
Who should hold the admin passwords and the Microsoft 365 tenant?
The dental group, in its own name and its own vault. Provider engineers use named accounts the group can disable, Microsoft's guidance recommends fewer than five Global Administrators plus two sealed emergency-access accounts, and no shared administrator login exists anywhere. If a tenant, domain or licence sits in a provider's name today, moving it is the first task of the engagement.
What happens when the in-house IT manager resigns?
If the RACI, tool table and documentation were kept as schedules, the provider is already accountable for the rows that keep the clinics running, so the group loses a planner, not its lights. The agreement should let the provider take the manager's rows at a stated rate during the vacancy, and the group's own vault holds every credential the departing person used.
Can a dental group use an IT manager and two outside IT companies?
It can, but every added party needs its own rows in the RACI and its own named accounts, and the vendor row still needs one face. Often a second company exists because the first could not cover a severity or a specialism; price that gap in one agreement instead, and keep the practice management and imaging vendors as vendors, not as a third IT company.
How many offices before co-managed IT makes sense for a dental group?
There is no fixed number. The model starts to make sense when there is enough people-facing and project work to fill an internal person's week and enough devices to need tooling that person cannot run alone; the fit test above uses four offices as its line. A single office with a capable staff member is usually better served by a fully managed plan with that person as its contact.
Is co-managed IT cheaper than fully managed IT?
Per user, usually. Meriplex's and BCS365's pricing guides, read on 18 November 2026, both put co-managed plans at $45 to $175 per user per month, and BCS365 puts fully managed plans at $150 to $400. The whole budget is not automatically cheaper, because the internal salary, benefits, tools and leave cover sit on the group's side. Compare both halves against a fully managed quote for the same RACI.
Who talks to Dentrix, Eaglesoft or the imaging vendor under co-managed IT?
One named person, normally the group's IT manager, who owns the vendor relationship and the ticket; the provider is consulted on the server, workstation, drivers and remote access the vendor needs. When a sensor stops capturing, the vendor, the imaging software and the IT environment are three suspects, and a single owner for the ticket stops the blame moving between them.
What should the monthly co-managed IT report show?
Patch state by office with the exception register, backup and restore evidence with dates, alerts raised and time to acknowledge, access changes including leavers disabled, Global Administrator count and multifactor coverage, tickets by category and office, open risks with owners, and contracts and devices reaching renewal or end of support in the next 90 days. The IT manager presents it to leadership.
The bottom line
If your group already employs IT staff and you want the RACI, the tool table and the evidence list in this guide tested against your offices, start from Legend's DSO IT support page and ask for a Free Dental IT Assessment: a review of your computers, software, network security, backups and performance, with written findings and prioritized recommendations. Bring the edited RACI and your IT manager, so the findings land on your own split. If you would rather see first how Legend's dental IT support works for a single practice, start there.

