Skip to main content
Question

Mac Updates Prompting for iCloud Login on AD-Joined Jamf-Managed Devices

  • January 30, 2026
  • 6 replies
  • 46 views
Naqeeb1
Forum|alt.badge.img

Hello everyone,

We currently have Macs that are joined to Active Directory and managed via Jamf Pro. We’ve recently noticed that whenever a piece of software or an application is outdated and an update is initiated, the system prompts for an iCloud (Apple ID) login. This was not the case previously.

We have already tried restricting the Apple ID preference pane and iCloud via Jamf, but the issue still persists.

Has anyone else experienced this, or does anyone have insight into what might be causing it and how it can be resolved?

Any advice or suggestions would be greatly appreciated.

    6 replies

    Chubs
    Forum|alt.badge.img+23
    • Chubs
    • Jamf Heroes
    • January 30, 2026

    Hello everyone,

    We currently have Macs that are joined to Active Directory and managed via Jamf Pro. We’ve recently noticed that whenever a piece of software or an application is outdated and an update is initiated, the system prompts for an iCloud (Apple ID) login. This was not the case previously.

    We have already tried restricting the Apple ID preference pane and iCloud via Jamf, but the issue still persists.

    Has anyone else experienced this, or does anyone have insight into what might be causing it and how it can be resolved?

    Any advice or suggestions would be greatly appreciated.

    This will only happen if the app was downloaded and installed via the App Store (or VPP with no assigned license or unsupervised). 
     

    are you deploying the app via JAMF?  May want to make sure that the app license is applied to it. Being domain bound or not won’t have any correlation TBH. 

    I find your lack of faith disturbing
    Chubs
    Forum|alt.badge.img+23
    • Chubs
    • Jamf Heroes
    • January 30, 2026

    Or are the apps you’re referencing Apple apps such as the newly released creator studio apps and such?

     

    Do you have any apps that require an in app purchase to validate?

    I find your lack of faith disturbing
    Naqeeb1
    Forum|alt.badge.img
    • Naqeeb1
    • Author
    • New Contributor
    • January 30, 2026

    Thanks for the response.

    Yes, the apps in question are Apple apps. They are deployed through Jamf Pro using Apple School Manager (ASM) with device-based assignment (not user-based Apple IDs).

    These Macs are AD-bound and fully managed, and the apps are pushed via Jamf without requiring users to sign in with an Apple ID. Despite this, when an app is outdated and an update is triggered, macOS prompts for an iCloud / Apple ID login, which wasn’t happening previously.

    Chubs
    Forum|alt.badge.img+23
    • Chubs
    • Jamf Heroes
    • January 30, 2026

    Thanks for the response.

    Yes, the apps in question are Apple apps. They are deployed through Jamf Pro using Apple School Manager (ASM) with device-based assignment (not user-based Apple IDs).

    These Macs are AD-bound and fully managed, and the apps are pushed via Jamf without requiring users to sign in with an Apple ID. Despite this, when an app is outdated and an update is triggered, macOS prompts for an iCloud / Apple ID login, which wasn’t happening previously.

    Which Apple apps?  And being domain bound has zero to do with application licensing just a FYI 🙂

    I find your lack of faith disturbing
      M
      Forum|alt.badge.img+16
      • mainelysteve
      • Contributor
      • January 30, 2026

      Alongside the Creator Studio subscription nonsense Apple released universal versions of the “iWork” apps. Anything under version 15.x is macOS only and will attempt to update to 15.x+ and prompt for that Apple Account because it’s a new(er) version with a different bundle id. You need to get into ASM and request licenses for the new apps and deploy those. 

       

       

       

      Chubs
      Forum|alt.badge.img+23
      • Chubs
      • Jamf Heroes
      • January 30, 2026

      Alongside the Creator Studio subscription nonsense Apple released universal versions of the “iWork” apps. Anything under version 15.x is macOS only and will attempt to update to 15.x+ and prompt for that Apple Account because it’s a new(er) version with a different bundle id. You need to get into ASM and request licenses for the new apps and deploy those. 

       

       

       

       

      This is what I was aiming at.  The newly released stuff will posture for this if you didn’t rescope them.

      Thanks Steve!

      I find your lack of faith disturbing
      Terms & ConditionsCookie settingsAccessibility statement