There's a bug in various places in Power Platform (Dataverse) that MS Support won't acknowledge, so I'm putting it here in hopes it makes it to the product team.

Here are the general repro steps:

1) Create an Azure SQL table with a DATE column and populate the column with date values.

2) Use the Virtual Connector Provider to create a virtual table in Dataverse.

3) Set the corresponding date/time column to Date Only and publish.

a) Note, per Microsoft’s documentation, a Date Only column has “No time zone conversion.”

4) Create a subgrid on a Dataverse form to show the virtual table records.

5) The dates shown in the subgrid do not match the dates in Azure SQL; the dates are one-day behind, so a time zone conversion is being done even though the column is set to Date Only.

6) Open the form for the virtual table record and the date does match the date in Azure SQL. This shows that Dataverse is inconsistent with how it displays date-only data through the virtual table connector provider (or virtual tables in general?)

7) The date in the subgrid does not match the date shown on the form (for the same record).

8) Enable the “New look” in Dataverse. This changes the grids to Power Apps grid control. Now the dates in the grid match Azure SQL. However, the Power Apps grid control only displays a few records for a virtual table (through the virtual table connector provider), so switching to this grid isn't practical either.

Someone please prove me wrong that these grid issues are "by design" or not a bug. I've talked with numerous MS Support engineers and some acknowledge that it's a bug and others say it's by design or I'm doing something wrong. And the "product team" just tells MS Support to tell me that it's by design and there's no problems. Whatever.