Hello @Allan Au
Thank you for reaching out to the Microsoft Q&A platform.
If the device you're attempting to RDP from is not Entra ID enabled and the host you're connecting to is not domain joined, you may encounter difficulties with the RDP connection. Entra ID relies on certain configurations and prerequisites to enable secure authentication, and deviating from those configurations may result in authentication failures or other issues.
In the scenario you described, where neither the device nor the host meets the requirements for Entra ID authentication, it's possible that the RDP connection will not succeed. However, without specific details about your Azure setup and configurations, it's challenging to provide a definitive answer.
To troubleshoot the issue further, you could review the Azure AD and VM configurations to ensure that the necessary settings are in place for both the device and the host. Additionally, checking for any error messages or logs related to the RDP connection attempt could provide valuable insights into the underlying issue.
Regarding the issue you are facing with the event log not showing up in the Event Viewer under the Applications and Services Logs\Microsoft\Windows\AAD\Operational, it is possible that the event logging is not enabled on the VM. To enable event logging, you can follow these steps:
- Open the Local Group Policy Editor on the VM by running
gpedit.msc
. - Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Hello for Business.
- Double-click on the policy "Use Windows Hello for Business operational logs" and set it to "Enabled".
- Click "Apply" and "OK" to save the changes.
After enabling event logging, you should be able to see the logs in the Event Viewer under the Applications and Services Logs\Microsoft\Windows\AAD\Operational.