A cloud-based identity and access management service for securing user authentication and resource access
I do not believe you can reset this, short of re-enabling the users in AAD, letting provisioning process them, and then disabling them again. The message you're seeing effectively means that the switch from entitled -> not entitled (active true -> false, in this case..) was already observed and processed. Was the mapping for the SCIM active attribute different in the past? I've seen people fall into this situation by changing to a bad mapping, such as accountEnabled -> active, and then trying to remove the user from scope via some other method besides accountEnabled = false, such as unassigning from the application.