Columns do not include Serial Number

[wcneumann219]

The Azure AD All Devices blade does not include an option to display the device's serial number. This can be important when trying to identify devices that were added as Windows Autopilot devices, but never provisioned using Windows Autopilot. When this happens one has orphaned records in Windows Autopilot that can only be removed by removing the device from Intune which then allows one to delete the device from the list of Windows Autopilot devices.

This devices that are in this state can most easily be identified by looking for records in Azure AD / All Devices that have identical Serial Numbers. Right now, you can search for a serial number but you can't view or download records that include the serial number.

This is a different scenario where duplicate Azure AD records exist when one is an Azure AD Registered devices. In our problematic scenario we have two devices that are both Hybrid Azure AD Joined. One is a Windows Autopilot device and the other is a standard device. They may or may not have the same name, but they will have the same serial number. In our case, we even have one device that shows active in both records, i.e., it sometimes reports into one of the two records and sometimes into the other one.

This is not a very common case, but it is very difficult to resolve without being able to identify the affected devices.

Thanks in advance for making this change!

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: a8119688-e88d-2916-3dcf-bf777a5fc80c
• Version Independent ID: e767d695-1c9f-64e4-e6c4-fef07b0f3d2e
• Content: Manage devices in Azure AD using the Azure portal - Microsoft Entra
• Content Source: articles/active-directory/devices/device-management-azure-portal.md
• Service: active-directory
• Sub-service: devices
• GitHub Login: @MicrosoftGuyJFlo
• Microsoft Alias: joflore

[Naveenommi-MSFT]

@wcneumann219 Thanks for your feedback! We will investigate and update as appropriate.

[YashikaTyagii]

@wcneumann219 Thank you for your feedback!

Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.

Teams Q&A forum for technical questions about the configuration and administration of Microsoft Teams on Windows. Microsoft Teams Community forum Thank you for your time and patience throughout this issue.