The Intune specialist your team doesn't have to become.

The short version

Intune Ready takes on Microsoft Intune configuration and deployment work for managed service providers whose clients need it but whose own teams would rather not build deep Intune specialty in house. Each engagement is scoped as a project with one fixed price agreed before work begins, covering tenant configuration, device enrollment across Windows, iOS, Android and macOS, Windows Autopilot, compliance policies and Conditional Access, and ending with documentation your technicians can work from. You keep the client relationship: Intune Ready works behind your team or alongside it, whichever you prefer, and does not approach your client for other work. The three arrangements MSPs use most are overflow, when an Intune rollout lands in a month that is already full; specialty, when a client's compliance or Conditional Access requirements go past what the team has done before; and rescue, when a tenant is half-configured and someone needs to finish it properly. Because the price is fixed before the work starts, you can quote your client a known number rather than an open-ended estimate.

When MSPs bring us in

Three situations account for most partner engagements. If a client project looks like one of these, the arrangement is already well understood on both sides:

1. Overflow. An Intune rollout lands in a month your engineers are already committed. The work is well within your team's reach — there is simply no room for it before the client expects it done.
2. Specialty. The client's requirements run past what your team has built before: layered compliance policy, Conditional Access design that has to hold up to an audit or an insurer's questionnaire, or consistent behaviour across Windows, iOS, Android and macOS at once.
3. Rescue. Somebody started the tenant and left. Partial enrollment, policies nobody documented, devices that report compliant without meeting any real standard — cleanup before configuration, and it is rarely the job anyone wants to inherit at a fixed price without knowing Intune well.

How a partner engagement runs

• 1
  Scoping call. Usually 30 minutes, with or without your client on the line. Device count, platforms in play, licensing, and whatever configuration already exists in the tenant.
• 2
  Fixed price, in writing. One number for the defined scope, before any work starts. Anything unusual enough to fall outside the normal ranges is identified here, not discovered halfway through.
• 3
  Build. Tenant and enrollment configuration, compliance and configuration profiles, Windows Autopilot, Conditional Access — under your brand or as a named specialist, whichever you chose at scoping.
• 4
  Handover. Documentation written for someone who was not in the build, plus admin training for the technicians who take the account back.
• 5
  Done. The engagement closes. The environment is yours to run, and the client relationship never left you.

What stays yours

The same line applies to everything around the build. The helpdesk, the client agreement, procurement, the rest of the Microsoft 365 estate and the ongoing relationship are yours — Intune Ready is there for the Intune project and nothing else. What's included at each service tier sets out the build deliverable by deliverable, which is usually the quickest way to draw the line for a specific client.

Why a fixed price matters to a partner

An open-ended estimate is difficult to resell. A fixed price is not: you know the cost before you quote, so you can commit your client to a firm number and price your own work on top of it with the margin visible up front. What it costs to set up Intune for a small business publishes the ranges and what moves them — device count, how many platforms, and how much half-finished configuration has to be cleaned up first.

The credentials behind the delivery are public: nine active Microsoft certifications, including the Microsoft 365 Certified: Endpoint Administrator Associate credential built specifically for Intune and endpoint management, with the full record on the credentials page.

Working solo rather than as a firm?

Independent IT contractors use the same arrangement at a smaller scale — subcontract the Intune build inside your own engagement, or refer the client for that piece of work. It is set out on the companion page for independent IT contractors, including how to price it when you are the one invoicing the client.

Common questions from MSPs

Can an MSP subcontract Microsoft Intune work to a specialist?

Yes — that is one of the two arrangements this page exists for. Intune Ready is brought in by managed service providers as a fixed-price specialist for a defined piece of Intune work: a tenant configuration, a cross-platform enrollment rollout, a Windows Autopilot setup, a Conditional Access design, or a partial deployment that needs finishing. The scope and the price are agreed before work begins, so the engagement has an end rather than an open meter. Independent IT contractors use the same arrangement on smaller jobs, described on the companion page for independent IT contractors.

Do you work under our brand, or do you appear in front of the client?

Either, and it is your call before the engagement starts. Some partners keep delivery entirely behind their own brand and pass the work through as their own; others introduce Intune Ready as the named specialist on the project, which can be the easier story when a client is buying a skill set rather than a body. The work, the documentation and the fixed price are the same in both cases. What changes is whose name is on the client-facing side of it.

Will you approach our client for other work afterwards?

No. When you bring Intune Ready into an account, the client relationship is yours and stays yours. Intune Ready does not solicit your client during the engagement or after it, and does not use the engagement as a route into the rest of their environment. If the client raises work beyond the agreed scope, it goes back to you.

What is in scope for a partner engagement, and what stays with us?

In scope is the Intune build itself: tenant and enrollment configuration, Windows, iOS, Android and macOS enrollment, baseline compliance and configuration profiles, Windows Autopilot, Conditional Access, and the handover documentation. Out of scope is everything you already do — the helpdesk, the client relationship, procurement, the rest of the Microsoft 365 estate, and whatever else your agreement with the client covers. The service tiers page breaks the build down deliverable by deliverable, which is usually the fastest way to see where the line falls for a specific client.

How is a partner engagement priced?

As one fixed price, quoted for the defined scope before any work starts — the same way every Intune Ready engagement is priced. There is no hourly meter and no invoice that arrives larger than the quote. What that comes to for a given client depends on the device count, the number of platforms and how much existing partial configuration has to be cleaned up; what it costs to set up Intune for a small business publishes the ranges and what drives them. Knowing the number before you quote is what lets you commit your client to a firm figure.

What do your technicians get at handover?

Documentation written to be used by someone who was not in the build: what was configured, why each policy exists, how enrollment works on each platform, and what to check when a device does not comply. Admin training and knowledge transfer are part of the engagement, so the people who take the account back can run it. The intent is that your team owns the environment at the end, not that it depends on whoever built it.

What happens after the rollout is finished?

The engagement ends. Your team holds the documentation and the training, and the environment is yours to run — for most partners that is the point of routing the work to a fixed-price specialist rather than hiring for it. If you would rather keep Intune Ready involved beyond handover, that is available, and it is scoped and quoted for the specific situation. Independent contractors who want the same arrangement at a smaller scale will find the details on the companion page for independent IT contractors.