Skip to main content
Question

Device registration status is getting changed to "Not registered"

  • June 28, 2022
  • 6 replies
  • 124 views
R
Forum|alt.badge.img+3

Hi All,

I have noticed a strange issue after upgrading to 12.4. Post upgrade, automatically the device's registration status has been changed to "Unregistered". I tried registering the device from self-service portal and it got registered. However, compliance information is not getting updated in AAD and due to that unable to access office resources. I did force update of sending Intune integration logs from Jamf Pro --> Device's history --> "macOS Intune Integration Logs" and it's sending the update to Intune. Somehow the compliance is not getting changed.

As part of troubleshooting deleted both the entries from AAD and re-registered the device but still the compliance is not getting updated. Any help is much appreciated.

      6 replies

      S
      Forum|alt.badge.img+2
      • Sidhartha
      • New Contributor
      • July 4, 2022

      We are also facing same issue , any update on this please

      R
      Forum|alt.badge.img+3
      • rmakkapa
      • Author
      • New Contributor
      • July 5, 2022

      We are also facing same issue , any update on this please


      No, still issue persists. working with Jamf support team

      A
      Forum|alt.badge.img+2
      • afisher160
      • New Contributor
      • October 3, 2023

      Was there any solution to this we are now having the same problem on Jamf Pro 10.50

      A
      Forum|alt.badge.img+2
      • afisher160
      • New Contributor
      • October 31, 2023

      The issue was resolved for me in Jamf Pro 11.0.1. And I was given a script to run that will re-establish the registration if it was previously registered. 

      Jamf Pro - Jamf Conditional Access script for Jamf Pro 11.0.1 (service-now.com)

        S
        Forum|alt.badge.img+1
        • sumanaddya
        • New Contributor
        • May 5, 2026

        The issue was resolved for me in Jamf Pro 11.0.1. And I was given a script to run that will re-establish the registration if it was previously registered. 

        Jamf Pro - Jamf Conditional Access script for Jamf Pro 11.0.1 (service-now.com)

        Can you please share the script?

        Steebie
        Forum|alt.badge.img+1
        • Steebie
        • New Contributor
        • May 6, 2026

        I have seen that the first user who logs into company portal on the MacOS device, typically to register the device for device compliance with Entra, is who the compliance information is tied to.  This causes major headaches in some environments when adjusting conditional access policies.

         

        The errored workflow is typically along the lines of:

        • “Technician A” sets up a device for ‘User B’ prior to handing them “MacOS Device”
        • “Technician A” registers the device to Entra to setup Platform SSO so that the user can just log into the device with their company email address (Platform SSO)
        • “Technician A” finishes the device setup, hands it to “User B” and tells them to log in using their email address.
        • “User B” logs in using email, has new device, is a happy camper

         

        The issue that occurs is that the compliance state of “MacOS Device” for “User B” will show N/A and won’t ever update.

        “Technician A”, thinking they were helping, registered the device to Entra.  If you check their list of devices, chances are they have a device record for “MacOS Device” they setup that actually does show the compliance state of that device.

         

        The only fix I’ve found for this is to basically wipe the device, start fresh, and ensure only the USER is who logs into the Entra registration via company portal for Platform SSO.  If the user actually using the device is not the one who registers with entra, the device record of the MacOS device won’t accurately be associated with them.

         

        A big downside is that due to this - and Simplified Platform SSO not being done on Microsoft’s end - is that the user will not be able to log in using their company email address as their UserID to log into MacOS, since by that point Platform SSO is not setup.  They’re stuck using a local account to then register entra platform sso.

         

        Kinda wordy but hopefully it gets the point i’m trying to make across.

        Terms & ConditionsAccessibility statement