When the setting ANSI_NULLS is set to ON (SQL Server default), the NULL-check is redundant because NULL <> NULL and [any value] <> NULL.
Thus, only "u.bi_user_passport_puid = u.bi_owner_passport_puid" would suffice. When one or both are NULL, the outcome will always be negative.
You can check the setting with the command:
DBCC USEROPTIONS
If the set option "ansi_nulls" is in the list, it's ON.