How does dynamic data masking behave differently when a masked column is used in a JOIN, WHERE clause, or exported through an application, compared to a simple SELECT query?

Dynamic data masking only affects the data returned in the actual result set displayed to an unauthorized user, meaning the real underlying values are still used internally for operations like joins and filtering, which is important to understand since masking does not prevent the real data from influencing query logic, only from being visually displayed.

-- The real email value is used for the join and filter,
-- but the displayed result will still be masked
SELECT c.Name, c.Email
FROM Customers c
JOIN Orders o ON c.CustomerId = o.CustomerId
WHERE c.Email = 'realvalue@example.com';