Permissions needed regranting - reconnect tenants
If the issue remains after reconnecting the tenant, this could be due to Microsoft Replication Delay.
We have confirmed that this behavior is expected as part of the Auto-pilot cleanup feature. There can be replication delays when the Auto-pilot hash is being removed in Intune — in some cases, it may take several hours after the removal command is issued. The code is designed to time out after a certain period, requiring the job to be resubmitted.
This degradation or delay occurs within Intune/Entra and can even be reproduced manually when removing the hash directly from the UI.
We recommend running these types of jobs ahead of the migration cutover window to allow sufficient time for the removal process in case delays occur.
In summary, the logic issues a Graph API call to remove the record and then waits for confirmation of the deletion. If the record is not removed after a prolonged period, the job fails and can be resubmitted manually later.
