mobile device management (mdm)
2292 TopicsIntune - Issues with Account-Driven User Enrollment Issues on iOS 18.5
Hello everyone, Since the release of iOS 18, Apple has deprecated profile-based user enrollment via the Company Portal app, requiring the use of Account-Driven User Enrollment. While this change enhances user experience, I'm encountering challenges in implementing it. Steps Taken: Apple Business Manager (ABM) Account: Created and linked the ABM account to Intune using the token. Corporate devices are successfully appearing in Intune. MDM Server Configuration: Set Intune as the default MDM server for all devices in ABM. Domain Federation: Established Entra ID federation in ABM to synchronize all users. Intune Enrollment Profile: Created an 'Enrollment Type Profile' of type 'Account-Driven User Enrollment.' MDM Push Certificate: Configured and validated the MDM Push certificate. Issue Encountered: According to https://support.apple.com/guide/deployment/account-driven-enrollment-methods-dep4d9e9cd26/web, starting with iOS 18.2, hosting a service discovery file on a web server is no longer mandatory. The device should automatically contact the ABM organization associated with the Managed Apple ID if no web server is found. On an iOS 18.5 device, I navigate to: Settings > General > VPN & Device Management > Sign in to Work or School Account After entering my Microsoft email address (which matches my Managed Apple ID due to federation), I consistently receive the error: "Your Apple ID does not support the expected services on this device." In ABM, under "Access Management" > "Apple Services," all services are activated. Could I be missing a crucial step in the configuration? Any guidance or insights would be greatly appreciated. Thank you in advance for your help. Best regards,1.1KViews1like8CommentsAutopilot failing while hardwired in but face no issue on the Wi-Fi
We are in the process of migrating from SCCM to Intune. The issue we are facing is that when the device is hardwired in, the autopilot process fails and says network connection lost. When the device is connected to the wireless network, it goes through the entire autopilot process and successfully enrolls the device. Has anyone faced this issue before?36Views0likes1CommentMacOS ADE Error
Hello everyone. I am running into an enrollment error when rolling out ADE for MacoOS devices. I have a macbook pro I have added to Apple Business Manager using the Apple Configurator for IOS. The device appears in ABM, syncs to my Intune MDM, and I have assigned it an enrollment profile. I then Factory Reset the Macbook. Upon first boot it loads the AD Account sign in page and lets me input login credentials, then throws the following error message. "Something went wrong - We're sorry, we ran into a problem. Please retry. If this happens again, factory reset your device to start over or contact your IT support person to do it for you." I have tried changing networks, creating new profiles, removing the device from ABM and Intune and adding it again to the same result. I have my profile set with modern authentication with User Affinity. Any help with this would be appreciated.6.2KViews0likes4CommentsCert Based Auth no longer working on Android devices.
Curious as to how wide spread this is/will be. Windows and iOS is fine, only affecting android. You can easily test this by revoking MFA sessions on a user who is using cert based auth on a android phone. I'm not sure if there has been a update recently to Android Microsoft Office apps where it thinks the certs live inside the intune company portal and is not looking for certs in the phones cert store. BYOD work profile Android 14 phones are being problematic, when a user changed their password and Azure revoked their sessions for a reauth, the issue started occurring. I tested this on another user manually revoking their MFA sessions without changing their password same issue occurred. I also setup a brand new Android phone and had the same issue after enrolling it. The issue is when the user opens outlook or teams and goes to sign in, it will pop up asking to use a cert on the device or a physical key. When selecting on the device the phone will freeze it will then eventually say ""company portal isn't responding" with the options of wait or cancel. Opening chrome in the work profile and going to a office app site will popup asking for the cert and works fine. So the issue doesn't appear to be the phone getting the cert, just the Office Apps are not accessing the Phones cert Store. I can confirm the Cert is inside the work profile as a browser or cert viewer app inside the workprofile can see it, auths work fine when using a browser in work profile, just not outlook or teams inside the work profile.1.4KViews0likes7CommentsWin 10 Security Baseline: Issue with WHFB
Hi, I activated the Intune Win 10 security baseline on a set of devices. I know experience an issue with WHfB. My face and fingerprint is not recognized, rsp. the login process is giving an error, saying that I cannot be identified. One user reports, that when away from company WhfB works as expected, asking for face or fingerprint and as second factor a PIN. I have another policy in Intune that is giving MDM policies precedence over GPO, so I cannot understand why it works for that one user when outside of company. What settings in MDM security Baseline could possibly be the cause resp. be responsible for broken WHfB?2Views0likes0CommentsIntune Re-Enrollment Registry Key "MmpcEnrollmentFlag"
Hey there, In the last few weeks, we encountered issues with clients (Entra Hybrid Joined) losing their Intune connection after setting an incorrect group policy. Although the group policy change was quickly reverted, about 10 clients were removed from Intune. I attempted to re-enroll these clients using various methods (MEMC Co-management, GPO, Scheduled Task, and even using psexec to directly start auto-enrollment), but the enrollment process consistently failed with the following error under Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider\Enrollment: Auto MDM Enroll: Device Credential (0x1), Failed (Bad request (400).) and/or following in CoManagementHandler.log Failed to get management URL with error 0x80070002 Eventually, I discovered a registry key that was not present on the working clients: Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enrollments Value: MmpcEnrollmentFlag Data: 0x00000002 After deleting this key and restarting the enrollment, everything worked immediately. I am curious about how and why this registry key is created and what its function is. Looking forward to your input.Solved12KViews4likes3CommentsOutlook Mobile Stuck in Login Loop on Intune Shared Android Devices
We’re having an issue on our Intune-managed shared Android Enterprise devices that are set up in Dedicated/Kiosk mode. When users try to open the Outlook mobile app, it launches and recognizes the signed-in user through AAD/Intune, but then it just gets stuck in a loop. It keeps showing messages like "Finding your account…" or "Identifying account…", and never actually loads the mailbox or even shows the normal login screen. Has anyone else run into this issue, and is there a known fix or workaround?225Views0likes4CommentsDisable Bluetooth on Android Fully Managed Devices
Hi All, Got an issue on an Android fully managed setup. I have set the option in the config profile to Block the Bluetooth Configuration, and this apply's to the devices, however Bluetooth is enabled by default, which is an issue as it has to be switched off. The config of Bluetooth on the device is locked down as per the setting. Any idea on how to turn Bluetooth off? It's not Samsung device so can't use KNOX. And Managed Home Screen also just blocks the config of Bluetooth and doesn't turn it off. Hoping this is possible 🤞 Thanks570Views0likes2CommentsDeveloper Options on Android Device
Hi all, I have an Android device enrolled in InTune and I'm trying to enable developer options. This would normally be done by tapping on the build number 7 times, however, when I try it on this device, nothing happens. There's no pop-up or error message, just nothing. I've tested on other identical devices and it works. It's got developer options enabled in the configuration policy, compliant in InTune, and was freshly reset/set-up, any ideas why it's not working?182Views0likes3CommentsManged Home Screen: Outlook
We are running into issues with the Managed Home Screen and Outlook. Once the user has logged into the Managed Home Screen and tries to access Outlook, it gets stuck in an authentication loop. Loops: Discovering Accounts -> Accounts Found -> Back to Discovering accounts. This is affecting multiple devices/accounts. This only affects363Views1like8Comments