This has bit me too many times. Behavior will often times appear correct during local development when all code is running in the same time zone, but then fails in deployed environments if for example a web server's time zone is UTC.

See also:

• Feature proposal: remove implicit construction of DateTimeOffset from DateTime dotnet/runtime#32954
• Comparison between DateTime (SQL Server column) and DateTimeOffset (parameter passed to EF) not consistent with in-memory behavior dotnet/efcore#24308