Answer
This points to Azure AD application-assignment configuration rather than an IFS-side setting — check with your Azure AD administrator that the affected users (and their specific domains) are actually included/assigned in the identity provider's application access configuration; also note that secondary URLs aren't currently supported when configuring an external identity provider in IFS, which can be a separate contributing limitation for multi-domain SSO setups.