In ASM registered device still requires MDM profile when returns to service should work

[Dacemotion]

Dear community,
I´ve got following problem:
When erasing a device and wanting it to return to service afterwards, I use this configuration:

Return to Service is checked, a valid network configuration is scoped. The option:"Install MDM profile after erasure" is NOT checked, because all our devices are registered in ASM. The documentation says:
"If the device is registered in Apple School Manager, the MDM configuration can be omitted."

Now when I confirm these settings, I get an error in the activity log saying "Für „Wiederinbetriebnahme“ ist ein MDM-Profil auf diesem Gerät erforderlich." Meaning: "A MDM-profile on the device is required for "return to service"". No erasure takes place.
So I cannot use this option, although it is described this way in the documentation.

https://learn.jamf.com/bundle/jamf-school-documentation/page/Return_Device_to_Service.html 

Does anybody experience the same problem or knows a possible solution?

Thank You in advance, Daniel

[_scripter]

Hi

Yes! I have a script that was working last time I tested it, and now suddenly I'm getting this error...

Please let me know if you find a solution!

[KuiperJack]

You need to tick all the boxes, including:

Install MDM profile after erasure
Required for all unsupervised devices and devices that were not enrolled with Automated Device Enrollment.

[C0dy]

But @Dacemotion and @_scripter were both talking about devices that are ADE enrolled because they are in ABM/ASM - they are therefore supervised too. This issue has yet to be resolved.

[KuiperJack]

I know.

All my devices are ADE enrolled.

i also had that alert.

it disappears when I tick the last box and it enrolls back in JAMF School.

Only Location Services are off but for that there is another case open

Allthough I think that is something apple needs to fix (if they are willing to since it is something they see as something a user needs to decide)

[C0dy]

Location is a privacy thing, Apple will never budge on collection location without user consent.

But this is a Jamf issue, their error checking is not inline with Apple requirements or their own docs. Return to service doesn't need an MDM profile if in ABM - so why does Jamf practically require it which just complicates workflows?