Answer
There's no way to apply different authentication-mechanism/identity-provider behavior to just one portal while leaving the rest of the Azure AD setup as-is — the identity-provider logic applies environment-wide. The practical path for external B2B partners is simply to have them authenticate using their own organization's standard email address as their identity (for example via an Azure AD guest account tied to that email), rather than trying to carve out custom per-portal authentication logic.