Macs lose Wi-Fi after about 90 days when Intune delivers the ACME certificate
Who this is for
You use Microsoft Intune to deliver a custom macOS configuration profile (.mobileconfig) that contains an ACME certificate payload (com.apple.security.acme) and a Wi-Fi payload, and your Macs use that certificate to join an 802.1X network.
Symptoms
Macs that connected fine suddenly can't join the secure Wi-Fi network, or quietly fall back to another network.
In System Settings > General > Device Management, the Wi-Fi profile shows an ACME Certificate marked Expired, and the profile's Installed date is months ago.
macOS asks the user to select a certificate for the network, and none is listed.
The certificate doesn't show up in Keychain Access. That's expected: it's hardware-bound and stored where only the profile that created it can use it.
Why it happens
The ACME payload requests a certificate when the profile is installed. Intune doesn't reinstall a custom profile that hasn't changed, so the Mac never asks for a new certificate before the old one expires. Each Mac drops off the network when its certificate's lifetime runs out, counted from when it got the profile. In many setups that lifetime is 90 days; check the expiry date shown on the certificate for yours.
Fix: re-push the profile with a new PayloadUUID
Changing the profile's top-level PayloadUUID makes it a new version. Intune redeploys it, macOS replaces the installed profile, and the ACME payload requests a fresh certificate.
Open the right .mobileconfig. Use the file that contains the ACME certificate payload and the Wi-Fi payload. If you also deploy your root certificate in a separate profile, don't use that one: re-pushing it only reinstalls the root and never requests a certificate.
Find the top-level PayloadUUID. Jump to the bottom of the file. After the closing
</array>ofPayloadContent, the outer dictionary hasPayloadDisplayName,PayloadIdentifier,PayloadType(set toConfiguration) andPayloadUUID.Replace only that PayloadUUID with a new value. On a Mac, run
uuidgen. In PowerShell, run[guid]::NewGuid().ToString().ToUpper().Don't change the PayloadIdentifier. macOS uses it to recognize the profile and replace it. A new identifier would install a second Wi-Fi profile next to the expired one.
Don't change the UUIDs of the payloads inside PayloadContent. The Wi-Fi payload points at the ACME payload by its UUID, and changing either breaks that link.
Optionally, raise
PayloadVersion(for example from 1 to 2) so the new version is easy to spot.
Upload it to the same Intune profile. In the Intune admin center, go to Devices > macOS > Configuration, open the profile, edit Configuration settings, select the edited file, then Review + save.
Sync a test Mac. In Devices > All devices, open the Mac and select Sync. Otherwise it picks up the change at its next check-in.
Note: re-saving the profile without changing the file, or re-uploading an identical file, doesn't trigger a new certificate. The PayloadUUID has to change.
Verify
In System Settings > General > Device Management, the profile's Installed date is today and the ACME certificate shows a new expiry date.
The Mac joins the secure network on its own. If it doesn't, turn Wi-Fi off and on, or pick the network from the menu.
Other Macs assigned to the profile renew as they check in with Intune. Macs that are asleep or offline renew the next time they check in.
Prevent it
Repeat the PayloadUUID change well before the certificates expire. With a 90-day certificate, every 60 days gives you a buffer. Set a calendar reminder, or automate it with the Microsoft Graph API. If you'd like a sample script to automate this renewal, contact Smallstep support.
Learn more
Connect Intune to Smallstep (macOS): the full Intune and macOS setup with Smallstep.
ACME basics: how ACME certificate requests work.
ACMECertificate payload (Apple): every key in the ACME payload, including hardware-bound keys and attestation.
Custom settings for macOS devices in Intune (Microsoft): how custom .mobileconfig profiles are created and uploaded.
