Access fileshare with AAD authentication on a non-a(a)d VM

[dim peak]

Hello, I am having trouble accessing an Azure file share from my virtual machine.
The file share is located in VNet A, which uses the IP range 10.0.0.0/16. My VM is located in VNet B, which also uses the IP range 10.0.0.0/16. The VM is not domain-joined(not possible with current configuration).
Given the overlapping IP addresses and the file share being on a different VNet, I suspect this is a problem with either the network connection or authentication.
Should we adjust the VNet addresses(really big hassle for this small issue), or is there something else that can resolve this issue?

I added the public IP and VNET to be able to access the fileshare. When connecting from a local laptop thats AAD joined I can access the fileshare. So it seems to be an issue that the VM is not AAD joined, but joining AAD is not an option.
Using shared keys is also not a preferable option.

[white hull]

You should honestly just put in the work to fix your address space overlaps. You could put a VPN gateway in each vnet and then NAT between them, but you're adding network complexity and cost for no reason to avoid a simple problem.

This is all assuming you want private access to your storage file share.