I have the following setup and need assistance with routing
Ultimate end goal of all of this is to allow Azure Files to be accessible on a non domain joined Windows 10 PC to authenticate using Azure AD (synced on from on prem AD in DR vNet). I'm able to successfully connect & authenticate to Azure Files on domain joined PC however for SMB traffic to be allowed for remote/home PC's an Azure P2S route was recommended but as of now I'm unable to successfully authenticate while connected to Azure Point to Site VPN because I don't have line of sight to my Azure VM running AD DS in DR vNet (192.168.39.0/24) network?
address space 192.168.39.0/24
DR subnet 192.168.39.128/25
VM with AD DS role (192.168.39.100)
DR-P2S Peering enabled with Gateway Transit Enabled
This network also has a policy based VPN to on prem
address space 10.0.0.0/16
P2S-DR Peering enabled 192.168.39.0/24 with gateway transit enabled
Virtual Network Gateway with Point-to-Site configuration
Route-based with P2SvNet virtual network
Address Pool 10.1.1.0/24
Client Windows 10 Machine
Azure VPN Marketplace client software successfully connects to the P2SVNet gets an ip address in space 10.1.1.2 and can connect to 10.0.0.0/16 space however it does not connect to 192.168.39.0/29 network
I can ping and rdp to resources on 10.0.0.0/16 vNet but no luck with DR route.