top of page
Search

What Should a Managed IT Services Agreement Include? An Ohio Business Guide

Jeremy Shoup
Oct 29
5 min read

A managed IT services agreement should make daily support easier to understand before a problem occurs. Business owners should be able to see what is covered, who handles each responsibility, how urgent issues are escalated, and which work may create an additional charge.


That clarity matters for organizations across Dayton, Tipp City, Troy and the Miami Valley. It is especially useful for nonprofits, where technology decisions may involve executive leadership, finance staff, board oversight, grant requirements and limited internal IT resources.


The exact agreement will vary with the provider and the environment. We recommend reviewing both the main contract and any service schedule, statement of work or security addendum. The following checklist can help you identify questions before you sign or renew.


1. A clear description of the covered environment


Start with a written inventory of what the provider is expected to manage. The agreement or an attached service schedule should identify the covered users, workstations, servers, networks, locations and cloud services. It should also explain how newly added users and devices become covered.


  • Employee computers and supported operating systems.

  • Servers, firewalls, switches, wireless networks and other managed infrastructure.

  • Microsoft 365 services such as Exchange Online, SharePoint, OneDrive and Teams.

  • Backup, endpoint protection, email security and monitoring platforms.

  • Business applications and vendors the IT provider will coordinate with.

  • Remote offices, home workers and any onsite support locations.


A broad promise to provide IT support is difficult to measure. A defined environment gives both parties a practical reference when a new request arrives.


2. Help desk coverage and the support process


The agreement should explain how employees request help and what coverage hours apply. Look for the supported channels, after-hours process, escalation path and treatment of onsite visits. If a response target is included, understand when its clock begins, what pauses it, and whether it describes an initial response or a final resolution.


Ask how priorities are assigned. A company-wide outage, one unavailable employee and a routine software request should not enter the same queue with the same urgency. The provider should also explain who at your organization may approve changes, purchases or access requests.



3. Proactive management included in the monthly service


Managed IT should identify the recurring work performed before an employee opens a ticket. Depending on the selected service, this may include monitoring, operating-system patching, supported third-party application updates, asset tracking, routine maintenance and review of security alerts.


The agreement should distinguish included recurring work from separate projects. A provider may manage an existing Microsoft 365 environment as part of the monthly service while treating a tenant migration, office move or server replacement as a separately planned project. The important point is that the boundary is understandable before the work begins.


4. Security responsibilities for both parties


Outsourcing IT does not transfer every technology and cybersecurity responsibility to the provider. NIST Cybersecurity Framework 2.0 calls for supplier, customer and partner roles to be established, communicated and coordinated. CISA likewise advises small and midsized organizations using an MSP to retain control of system access and include expectations for vendor access, activity logs and separate backups in vendor agreements.




A useful agreement or security addendum identifies who manages multifactor authentication, endpoint security, administrative accounts, vulnerability remediation, security awareness, logs and security-policy exceptions. It should also explain what the customer must do, such as promptly reporting employee departures, approving recommended changes and maintaining acceptable-use policies.


For Microsoft 365, clarify who administers identities, access policies, device settings and data-protection choices. Microsoft’s cloud responsibility guidance states that customers retain responsibility for their data, identities, account management and access controls, even though Microsoft operates the underlying cloud infrastructure.




5. Backup, retention and recovery expectations


The agreement should identify which systems and data are backed up, how frequently backup jobs run, how long recovery points are retained and who reviews failures. Ask whether Microsoft 365 email, OneDrive and SharePoint data are included or require a separate backup service.


Recovery deserves its own discussion. Determine who may authorize a restore, how restore requests are prioritized, whether testing is included and what assumptions apply to recovery time. A backup status report shows that a job ran; a restore test provides stronger evidence that selected data can be recovered.


Business leadership should also decide which systems must return first. A nonprofit may prioritize donor records, case-management systems, payroll and program communications differently from another organization.


6. Incident response and notification


The agreement should state how suspected security incidents are reported, who may authorize containment actions, which contacts receive updates and how the provider coordinates with cyber insurance, legal counsel or other specialists. It should describe the customer’s responsibilities as well, including timely reporting of suspicious activity and maintaining current emergency contacts.


NIST recommends including relevant third parties in incident planning, response and recovery. A practical agreement should therefore make the communication path clear before an incident creates time pressure.


7. Pricing rules beyond the recurring fee


The monthly amount alone does not explain the total cost of a managed IT relationship. Review what is included, what is optional and what requires approval. We recommend asking about onboarding, onsite travel, after-hours work, projects, hardware, licensing, shipping and third-party vendor charges.


Also confirm how the fee changes when employees, devices or locations are added or removed. The agreement should explain billing frequency, renewal terms and any minimum quantities. These questions let you compare proposals based on scope instead of comparing monthly totals that may cover different work.



8. Documentation, account ownership and administrative access


Your organization should know who owns its domain, Microsoft 365 tenant, cloud subscriptions, documentation and business data. The agreement should address how credentials and records are stored, who may access them, and what the customer receives during a transition.


Ask whether the provider uses delegated access, individual named accounts or shared accounts. Microsoft recommends minimizing standing high-privilege access, reviewing service-provider permissions and understanding the available audit-log retention for the subscription in use.



9. Onboarding, offboarding and provider transitions


A sound agreement should describe both the beginning and the end of the relationship. Onboarding may include discovery, documentation, tool deployment, account review and remediation of urgent risks. Confirm what is included and which findings require a separate proposal.


The termination section should cover notice, final billing, return of documentation, removal of provider access, transfer of licenses and the handling or deletion of customer data held by the provider. It should also explain whether transition assistance is included or billable.



10. Reporting and regular business reviews


Decide what information leadership needs to evaluate the service. Useful reviews may include recurring issues, security recommendations, device lifecycle needs, backup status, unresolved risks and upcoming projects. Reports should support decisions rather than simply list ticket counts.


For a nonprofit, reporting may also need to support budgeting, grant planning, board communication or insurance questionnaires. Agree on who attends reviews and who can approve the resulting work.


Questions to ask before signing


  • Which users, devices, locations and cloud services are covered?

  • What support requests are included, and what becomes a separate project?

  • How are priorities, response targets and after-hours issues handled?

  • Who manages security controls, backups and incident communication?

  • What licensing, travel, onboarding or project charges may apply?

  • Who owns the accounts, documentation and data?

  • What happens to access, licenses and records when the relationship ends?

  • How often will leadership review risks, recommendations and technology plans?


Discuss your managed IT needs with SimplicIT


We help businesses and nonprofits across Ohio understand what they need from an IT support relationship. If you are comparing managed IT proposals in Dayton, Tipp City, Troy or elsewhere in the Miami Valley, we can review your priorities and explain how support, security, Microsoft 365 and backup responsibilities can be defined.


Bring your current concerns, locations, approximate user count and the systems your team depends on. We will use that information to discuss the right next step without inventing a one-size-fits-all scope.



 
 
 

Recent Posts

See All

Comments


bottom of page