APNs certificate shows the wrong Apple ID in HexnodeSolved

Participant
Discussion
4 weeks ago Sep 17, 2026

The APNs certificate in our Hexnode portal is shown as being associated with an old Apple ID. We later found that the certificate ownership needs to be moved to another Apple ID that the team still has access to.

What is the correct order here? Should the APNs certificate be transferred with Apple first, or can the Apple ID displayed in Hexnode be changed before that?

Replies (2)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Sep 17, 2026
Marked SolutionPending Review

Hello @verbnigge ,

For APNs certificates, the Apple ID association is controlled by Apple. The correct sequence is to complete the transfer on Apple’s side first.

Recommended workflow:

  1. Contact Apple Support and request that the existing APNs/MDM push certificate be transferred to the active Apple ID your organization will continue using.
  2. Wait until Apple confirms that the transfer is complete.
  3. In Hexnode UEM, renew the APNs certificate using that same Apple ID.
  4. Upload or complete the renewed APNs certificate workflow in the Hexnode UEM portal.

The important part is to renew the existing APNs certificate with the same certificate identity after Apple completes the transfer. Avoid creating a brand-new APNs certificate unless you intend to re-enroll managed Apple devices, because a different APNs certificate can break MDM communication with already enrolled devices.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
4 weeks ago Sep 17, 2026
Marked SolutionPending Review

Oh, ok then. We’ll have Apple transfer the existing APNs certificate first and then renew it in Hexnode using the active Apple ID.

Save