The solution would depend both on user account type and device type.
Microsoft accounts (personal)
Currently only personal Microsoft accounts (e.g. @outlook.com) are fully supported for passwordless login to Windows 10/11 using Authenticator app.
Azure AD accounts (work or school) on Azure AD joined devices
There is a feature which is called Web sign-in and ...
I would suggest to carefully read the following article which basically answers your question.
By default, adding a private endpoint would not block access to the public endpoint but it all depends on the connectivity settings that are configured.
Based on my knowledge, there is no built-in function to fulfill your needs in exchange online side, you may need seek for a 3rd party tool to achieve your goal. I have found a blog on your issue for your reference and it may be helpful to you.
For those who are interested, it turned out the file supplied, which was labelled CA certificate, was a private certificate where the supplier itself was the "local certificate authority". With that CA certificate, a self signed client certificate was generated. Azure Logic App's HTTP request action does not support those kinds of self signed ...
Run netstat -antop | grep 8888 which will give you the process ID that is running on that port, which you can then use to find out what is actually running. "sun-answerbook" is just what namp has in it's list of what application first used that port when it was created, it is not accurate.
From a Linux VM, I tried to bind to the AD using ldapsearch and I got
"invalid credentials" with the following command
Most likely the account you tested with does not have the correct password hash synced from AAD to AAD DS yet: https://docs.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-create-instance#enable-user-accounts-...
The answer and comments from Sam are quite right, you need to separate users with different login names; and you are violating the license by running Windows 10 Pro on Azure.
One current, supported, and validly licensed method for doing this is to deploy Azure Virtual Desktop. AVD provides a managed Azure service that combines remote desktop gateway and ...
I've figured out the solution. It was two-fold:
I used ssh -R '*:5002:localhost:5002' xx.xx.xx.xxx instead of ssh -R 5002:localhost:5002 xx.xx.xx.xxx. The asterisk makes sshd to listen to port 5002 on all interfaces. Otherwise it would just listen on the loopback interface.
I also had to allow port 5002 in the Windows Defender Firewall of the Azure Win10 VM....
Went into the Azure portal, raised a New Support Request (took a while to find the right Service type), , filled out the diagnostic panel (funny spelling for diagnostic), , and got told that there was a firewall rule blocking traffic. Fixed that and now HOPL is back online!