Answer
The path is case-sensitive — use /ifsapplications/SCIM/v2 (uppercase SCIM), not /scim/v2, which is a common cause of an otherwise-correctly-configured request returning 404. Beyond the URL itself, the full setup sequence needs: the IFS_scim client enabled in IFS, a SCIM offline token generated from the 'SCIM Access Manager' screen, and that token pasted into Azure as the secret token when creating the connection — critically, as an Azure 'Enterprise application,' not an 'App registration,' since only the Enterprise application has the provisioning configuration SCIM sync depends on.