Thanks for the comments, just a few questions to the gallery.
What platform is this issue with. I’m only seeing IOS devices in your comments, so wanted to double check.
Also, are you having this issue with shared devices or just re-deployment? Unclear from all the comments. Do you want to keep all installed apps on the devices? Depending on your platform, you should be able to already do this for shared devices.Sven commented
Windows devices please. It would be awesome to decide if apps should be kept or not.
Confirmed that it is currently by design that conditional access allows only one identity per device at this time. We hear that you need this and we’re looking into it. I’ve changed the title and category to indicate that this is related to conditional access.
Again, this is just for multiple identities from the same company. If you’re looking for having one device with identities from two different companies for MDM, that idea is here:
And if you’re looking for having multiple identities for MAM, that idea is here: https://microsoftintune.uservoice.com/forums/291681/suggestions/34627435
As of the week of August 27, you can use a template to control how the machine will be automatically named. So not exactly static, but gets you away from total random. From the discussion, sounds like not total random was good enough for some, but not all, so I will switch this back to “noted”.
more detail about what we released in August:
When you create an autopilot deployment profile, you can designate a name, which must be 15 characters or less, and can contain letters, numbers, and hyphens. Names can’t be all numbers. Use the SERIAL macro to add a hardware-specific serial number. Alternatively, use the RAND:x macro to add a random string of numbers, where x equals the number of digits to add.
It’s only available with the Windows Insider build for now.