I believe the actual answer to this question is to ring up the geniuses writing this policy, and counter that it should be worded "diffent passwords for each account." Which I think is the actual intent. People should not be reusing passwords among different accounts.
Then go one step further and propose unifying all authentications to a single account. It is easier to secure with MFA, easier to terminate access, easier to address in the form of a lost password, easier to provision/deprovision - and (when the site/provider supports it) makes it possible to remove application-local accounts which usually have stanant passwords that are ripe for brute-forcing.
Going as "required" by the security team" would mean separate passwords for each external website not integrated with SSO/SAML/OIDC, frequently forgotten, rarely updated.
Without being too demeaning, this is such an awful policy (to apply to internal sites using the same authentication source anyway). It necessitates creating multiple, local accounts, which then ALL have to be disabled/deactivated upon termination - leaving you prone. Not to mention - the unlikelihood of being able to maintain a unfied password policy against all of the various solutions.