Event details
For a few reasons we prefer to configure the device using Immy.bot. We use Autopilot strictly to install the Immy.bot agent and then auto-onboard the device using Immy.
This allows us to "own" the process and be ethically sticky with the client. If we configure everything within the client's tenant, then if we are replaced as an MSP, we have essentially built the automations/processes for the incoming MSP. Using Immy to configure the machine, if we leave, the tools leave as well. That certainly increases our internal development cost as we are not billing our clients for that development, but long-term, we believe that will help us reduce client turnover.
We have to be very careful in the language of our agreements and what we quote as deliverables in various projects to ensure we are acting ethically.
Currently we add the devices using a tuple through the partner center to instead of having the OEM/Reseller add them as there is normally a cost associated with having the OEM add the devices.
Is there something I am not considering that would make using Autopilot/Intune a more desirable process?
- Maggie_DakevaApr 21, 2026
Microsoft
Could you clarify what your goal is with using a tool like this? Is this for more control over provisioning process because you see gaps with the native experience, or is it more so you have full control over the solution? Also, can you help me understand how you see this reducing client turnover?