Azure Active Directory device management FAQ
Q: How can I register a macOS device?
A: To register macOS device:
The users that are included in your conditional access policy need a supported version of Office for macOS to access resources.
During the first access attempt, your users are prompted to enroll the device using the company portal.
Q: I registered the device recently. Why can’t I see the device under my user info in the Azure portal?
A: Windows 10 devices that are domain-joined with automatic device registration do not show up under the USER info. You need to use PowerShell to see all devices.
Only the following devices are listed under the USER info:
- All personal devices that are not enterprise joined
- All non-Windows 10 / Windows Server 2016
- All non-Windows devices
Q: Why can I not see all the devices registered in Azure Active Directory in the Azure portal?
A: Currently, there is no way to see all registered devices in the Azure portal. You can use Azure PowerShell to find all devices. For more details, see the Get-MsolDevice cmdlet.
Q: How do I know what the device registration state of the client is?
A: The device registration state depends on:
- What the device is
- How it was registered
- Any details related to it.
Q: Why is a device I have deleted in the Azure portal or using Windows PowerShell still listed as registered?
A: This is by design. The device will not have access to resources in the cloud. If you want to remove the device and register again, a manual action must be to be taken on the device.
For Windows 10 and Windows Server 2016 that are on-premises AD domain-joined:
Open the command prompt as an administrator.
dsregcmd.exe /debug /leave
Sign out and sign in to trigger the scheduled task that registers the device again.
For other Windows platforms that are on-premises AD domain-joined:
- Open the command prompt as an administrator.
"%programFiles%\Microsoft Workplace Join\autoworkplace.exe /l".
"%programFiles%\Microsoft Workplace Join\autoworkplace.exe /j".
Q: Why do I see duplicate device entries in Azure portal?
For Windows 10 and Windows Server 2016, if they are repeated attempts to unjoin and re-join the same device, there might be duplicate entries.
If you have used Add Work or School Account, each windows user who uses Add Work or School Account will create a new device record with the same device name.
Other Windows platforms that are on-premises AD domain-joined using automatic registration will create a new device record with the same device name for each domain user who logs into the device.
An AADJ machine that has been wiped, re-installed and re-joined with the same name, will show up as another record with the same device name.
Q: Why can a user still access resources from a device I have disabled in the Azure portal?
A: It can take up to an hour for a revoke to be applied.
For lost devices, we recommend wiping the device to ensure that users cannot access the device. For more details, see Enroll devices for management in Intune.
Q: Why do my users see “You can’t get there from here”?
A: If you have configured certain conditional access rules to require a specific device state and the device does not meet the criteria, users are blocked and see this message. Please evaluate the rules and ensure that the device is able to meet the criteria to avoid this message.
Q: I see the device record under the USER info in the Azure portal and can see the state as registered on the client. Am I setup correctly for using conditional access?
A: The device record (deviceID) and state on the Azure portal must match the client and meet any evaluation criteria for conditional access. For more details, see Get started with Azure Active Directory Device Registration.
Q: Why do I get a "username or password is incorrect" message for a device I have just joined to Azure AD?
A: Common reasons for this scenario are:
Your user credentials are no longer valid.
Your computer is unable to communicate with Azure Active Directory. Check for any network connectivity issues.
The Azure AD Join pre-requisites were not met. Please ensure that you have followed the steps for Extending cloud capabilities to Windows 10 devices through Azure Active Directory Join.
Federated logins requires your federation server to support a WS-Trust active endpoint.
Q: Why do I see the “Oops… an error occurred!" dialog when I try do join my PC?
A: This is a result of setting up Azure Active Directory enrollment with Intune. For more details, see Set up Windows device management.
Q: Why did my attempt to join a PC fail although I didn't get any error information?
A: A likely cause is that the user is logged in to the device using the built-in administrator account. Please create a different local account before using Azure Active Directory Join to complete the setup.
Q: Where can I find instructions for the setup of automatic device registration?
A: For detailed instructions, see How to configure automatic registration of Windows domain-joined devices with Azure Active Directory
Q: Where can I find troubleshooting information about the automatic device registration?
A: For troubleshooting information, see: