SQL Server Azure VM with 512e SSD Storage - Error 9012

I have been given a SQL Server Azure VM that has 512e storage attached for data and log files, according to fsutil fsinfo ntfsinfo [drive letter]:\. It is a DR replication node from an on-premises server with 512 storage drives. The VM is reporting 9012 error, which could be due to the storage or due to the difference between the replication server and the primary server. I am trying to assess if this is a cause for concern for both Availability Groups delay and for optimal SQL Server setup, if I were to turn it into a primary. Everything I am reading seems to say that 512e and SQL Server is not recommended. But the articles are from 2011 - hasn't anything changed in 11 years? Or is 512e still not the way to go. Azure documentation does not mention any of this and I can only gather that 512e may be optional for the new SSD disks. Note: Enabling trace flag 1800 did not resolve the error. Microsoft don't even recommend HDD, listing them as recommended for Dev only now. I am waiting to see if I have ability to open a support ticket, but wanted to know people's experience here too.