Hi,
If I understand what you are trying to do correctly, then, I will start with, you probably shouldn't do it.
However....
two things will need to be in-place.
- You need your name resolution to work. With your local/isp DNS enabling internet access, you have a problem with then resolving the AD Domain for the join to work. Normally you would point your client DNS to your AD domain controller for DNS. But then you need to be able to resolve internet DNS
- You need network access - Refer https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/config-firewall-for-ad-domains-and-trusts
- You probably have an azure NSG (network security group) blocking all inbound access (except RDP from the sound of it)
- Not sure where your client is but if it is also behind a firewall or the like, there may be further port blocakages there.
- If your client is behind a NAT (network address translation) device/service i.e. Home router/isp then you may not be able to do it anyway.
Another option may be to create a point to site VPN in azure (or site to site VPN dependng on your situation).
There may be other options but these are my initial thoughts.
Regards,