Take on e of your test-devices and remove the config for this device in your Zero-Touch (not Zero-Trust :D) Portal.
After that assign the configuration to this device again, wipe the device and start again.
You need also to ensure that the device can reach the relevant Google services so use an unrestricted Wifi or mobile data for the enrollment.
In general your reseller is your support contact for your ZT-Portal and you need to reach out to them in order to get it working!
But i want to mention something in addiotion you could try on your own (risk):
If this works you can export your devices from ZT, change the config column to 0 and read it into ZT-Portal.
After that doing the same again but with the profile ID to assign the profiles back to the devices.
_____________________________________________________________________________________
As a last thing you can try is as your devices enrolling like a consumer device, when asked for a Google account enter following instead (DPC identifier): afw#sophos
This will force the device to grab the sophos apk and device behavior like a managed device. You will be asked for something like an enrollment ID as soon as the sophos apk is installed and needs to be entered.
An alternative to this is using QR-enrollment (see the sophos enrollment documentation about how this is being created).
But all this last mentioned things (DPC identifier/ QR code) are just for verifying that the general enrollment works and test your configurations and so on from MDM side and doesn't solve your real issue regarding ZT detection.
I'm pretty sure if the manual thing won't work, the csv won't make a difference so your reseller is 100% in charge to investigate (maybe with Google) why this happens and/or what's wrong here.
I know about this "info message" but normally it took immediatelly place when i changed it on some less devices. Maybe this is different when done on a large number.
Your file should look like this:
"modemtype","modemid","serial","manufacturer","model","profiletype","profileid"
"IMEI","123456789012345","","Manufacturer","","ZERO_TOUCH","123456789"
Again, in this case your reseller needs to get in touch with Google as they need to figure out whats going on wrong here. And that goes thru thepartner portal afaik.
Yes it does go through the partner portal. They're potentially uploading them incorrectly.
@Tomasz_T I may be able to help. Message me.
Pick a contact method from here to reach me outside of the community. In short the issue you're facing is due to your reseller not correctly registering the devices.
