I see that Azure states “RedundantError” while trying to provision the user. This is not an error but more of an information message from Azure. The RedundantExport message means that the user properties are the same on Freshservice just as they are in Azure, and therefore, no provisioning or updating was required for the user.
The state of entry in both the source (Azure) and target systems (Freshservice in this case) already matches, and hence, no changes need to be made.
In certain cases, we have noticed that the Provision on Demand feature triggers two requests. The first request updates the properties on Freshservice, and hence the second request returns a “RedundantExport” message stating that the values are the same.