How to rename the endpoints based on country on Autopilot Device Preparation 

Hi Steve! Wondering what you would recommend for a naming convention Intune policies for MSPs? Not sure if you may have discussed this - also how do you approach CSPs and Settings Catalog? Should I have one profile for every setting or should I try to package them with use case/target devices? Any advice would be greatly appreciated! 

Also - how to recommend monitoring for policy conflicts for co-managed environments? 

You are both pronouncing it correctly. :)

Thanks for the response!

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?

Are you aware of any tool to see if a Windows PC has been previously registered(still registered to a tenant?). Use case is refurb/pre-used devices being handed out to a new user. Need to be able to see if PC is registered without opening the OEM box.  

Pre-provisioning mode takes a lot of time while running the ‘Account Setup’ phase because of app validation, etc. So in a scenario where Loaner devices (short term use) are required to be provisioned, Pre-provisioning takes a long time and is not a preferred option. I think this is where we are pivoting to use Self deployment method. It finishes the ESP pretty fast when the device is handed over to a user. Can you provide any inputs or suggestions based on your experience with building Loaner devices using Autopilot? Thank you.

You just put "Task Sequence" and "Manual configuration" in the same sentence. I'm wondering if you know what a Task Sequence is and how it works ?

Welcome MSPs! Today we're talking about Windows Autopilot. We'd love to hear your questions and feedback so please share your thoughts here in the comments.