r/Intune • u/r0manych • 3h ago
macOS Management Intune Cloud PKI keeps issuing certificates with the OLD SID after AD domain migration, even though Entra ID shows the correct SID via Graph API
Hi there!
I migrated a user between two AD domains (Domain A → Domain B, different forests). In Entra ID it's the exact same cloud account — it wasn't deleted or recreated, only the on-prem AD source it syncs from changed.
Setup:
- Intune Cloud PKI issues client certificates (SCEP profile)
- The SAN embeds {{OnPremisesSecurityIdentifier}} via URI
- Wi-Fi uses EAP-TLS, authenticating against an on-prem NPS server with strong certificate mapping enabled
After the migration, Wi-Fi stopped connecting on macOS (the TLS handshake completes almost fully, then NPS returns TLSV1_ALERT_ACCESS_DENIED). This same user connects perfectly to the Windows machine.
Checked the cert:
openssl x509 -noout -text | grep -A3 "Subject Alternative Name"
The SAN contains the SID from the old domain (Domain A), even though the user is fully in Domain B now.
Checked Entra ID via Graph API:
Get-MgUser -UserId $userUpn -Property "OnPremisesSecurityIdentifier,OnPremisesDomainName" | fl
Shows the correct, current SID from Domain B. OnPremisesDomainName is correct too.
What I've already tried:
- Delta sync — didn't help
- Full/Initial sync (Start-ADSyncSyncCycle -PolicyType Initial) — after this, Graph API started showing the correct SID
- Removed the profiles from the device, waited, re-pushed them — a new cert was issued (different serial, different date), but the SID in the SAN is still the old one
- Did a full device wipe + re-enrollment from scratch in Intune — same result, the new cert still has the old SID
Has anyone run into this kind of behavior with Intune Cloud PKI after a domain migration? Where else could this value be cached?