Your scenario is totally make sense, nothing wrong with that. A user will have multiple accounts in some HR products. I have faced same scenario in SuccessFactors.
- You can filter accounts from Authoritative source while aggregation if it is ok to not to read that account at all, but it might have consequences like you might not know when a user gets disabled and if it doesn’t have one more account.
IdentityNow Account Filtering during Account Aggregation - Compass (sailpoint.com)
- If you need to have both accounts (enabled, disabled) in Identity, then update your transforms (Account Attribute) to read enable account data using filter attributes accountPropertyFilter, check the optional attributes in Transform.
Hope this helps.
Thanks
Krish