Forum Discussion
enrolling in Intune MacBook Pro with an M5 Pro
Hi everyone
We have tested the Wi-Fi and ethernet profile without success with Apple businesses manager.
The Wi-Fi and the ethernet connection itself works, but the enrollment process into Intune does not complete successfully.
At this stage, we cannot sign in, and neither the Wi-Fi nor the Ethernet connection appears to be working.
The device is a 14-inch MacBook Pro with an M5 Pro chip, running macOS 26.5.1 the device connects to the server, the settings begin to apply, but the process suddenly stops, and we are then unable to log in.
These are steps followed :
Synchronize the device from Apple Business Manager to Intune.
Assign the enrollment profile to the device.
Perform a device wipe/reset.
Start Automated Device Enrollment (ADE).
Complete the device setup and user sign-in.
The device successfully enrolls into Intune.
Intune begins deploying configuration profiles, compliance policies, security policies, and applications.
During the policy application process, Wi-Fi connectivity stops responding.
The device loses network connectivity and cannot continue synchronizing policies. We are unable to sign in because the enrolment process has not been finalized. As a result, we have to wipe the Mac and start the process again each time.
We have disabled some policies, but we are still experiencing the same issue.
Have anyone experienced any issues like that ?
Regards,
1 Reply
Hi, for ADE enrollment on a new Mac, I would check the basics before going deep into Intune.
Good steps:
1. Confirm the Mac serial appears in Apple Business Manager.
2. Confirm it is assigned to the correct Intune MDM server.
3. Sync the enrollment program token in Intune.
4. Confirm the enrollment profile is assigned.
5. Test enrollment on a simple network with no proxy/captive portal.
If Wi-Fi works but enrollment does not complete, the issue may still be network access to Apple or Microsoft enrollment endpoints. I would also check the Intune enrollment failures page for the exact error.