Looking for the DeviceID value from webhook generated by Microsoft Teams Admin Center

Question

Looking for the DeviceID value from webhook generated by Microsoft Teams Admin Center

camaro1987 0

Dear Support Team,

I am looking for the DeviceID value included in a webhook generated by the Microsoft Teams Admin Center

Our system relies on the DeviceID from the webhook payload to associate the device with a Configuration Item (CI) in another system.

Could you please advise where the DeviceID can be found? Ideally, we would like to confirm whether this value is visible in the Microsoft Teams Admin Center GUI and, if so, where exactly it can be located.

Please find example of webhook which we receive below

Thank you in advance for your assistance.

Best regards,

Obraz użytkownika

camaro1987 0 Punkty reputacji

2026-02-26T11:09:53.93+00:00

Thank You for guidence.

Do You know why I cannot see devices registered in Microsoft Entra Admin Center but can see devices in Microsoft Teams Admin Center?
Anonimowe

2026-03-02T22:23:46.4033333+00:00
Hi @camaro1987,

Thank you for your follow-up question.

The reason you can see devices in the Microsoft Teams Admin Center but not in the Microsoft Entra Admin Center is that Teams devices are not all registered in Entra ID in the same way. As a result, their visibility can differ between the two portals.

Below are the most common reasons this occurs:

1/ Teams‑certified devices vs. Entra‑registered devices:

Many Teams‑certified devices, such as Teams Rooms, Teams Phones, and Teams Displays, are primarily managed and surfaced through the Teams Admin Center. Although these devices authenticate to Microsoft services, they do not always appear as standard Entra ID devices under Devices > All devices, especially if they are not Azure AD joined in the traditional sense.

2/ Different device registration models:

In addition, some Teams devices are:

Signed in using resource accounts

Registered as service‑associated endpoints

Managed through Teams device management rather than full Entra device registration

In these scenarios, the Teams Admin Center displays the device for operational management, while the Entra portal may not list it as a user‑associated or fully joined device object.

3/ Permission and visibility limitations:

Even when a device does exist in Entra, it may not be visible if your account does not have sufficient directory‑level permissions. To view all device objects in Entra, you typically need one of the following roles:

Global Administrator

Cloud Device Administrator

Intune Administrator

Directory Readers (read‑only)

Without one of these roles, the device list in Entra can appear incomplete.

4/ Timing and synchronization behavior:

Finally, depending on how a device was onboarded and managed, there may be delays between when it becomes visible in the Teams Admin Center and when it appears, if at all, in the Entra Admin Center.

It’s also important to note that even if a device does not appear in the Entra Admin Center UI, the DeviceID included in Teams webhook payloads is still a valid backend identifier used by Microsoft. This explains why you may receive a DeviceID via webhook that cannot be directly located in the Entra device list.

For large‑scale correlation scenarios, such as CMDB integration, using Microsoft Graph remains the most reliable approach, as it exposes device objects and identifiers beyond what is visible in the Teams Admin Center UI.

I hope this helps clarify the difference in device visibility between the two portals. Please don’t hesitate to reach out again if you have any further questions or need additional clarification.

Best regards,

Odpowiedzi: 2

Twoja odpowiedź

camaro1987 0 Punkty reputacji

2026-02-26T11:09:53.93+00:00

Thank You for guidence.

Do You know why I cannot see devices registered in Microsoft Entra Admin Center but can see devices in Microsoft Teams Admin Center?

Answer 1

camaro1987 0

Thank You for the answer. Is there way to export DeviceID from Microsoft Teams Admin Center in bulk? I have couple hundreds devices to extract.

Anonimowe

2026-02-23T22:29:39.59+00:00
Hi @camaro1987,

Thank you for your follow‑up question.

At this time, the Microsoft Teams Admin Center does not provide a built‑in way to export DeviceID values in bulk. As mentioned earlier, the Teams Admin Center UI does not surface the backend DeviceID at all, so there is no export option available from that interface.

However, since Teams devices are registered as Microsoft Entra ID device objects, bulk extraction is possible from the Entra side instead of Teams. In practice, there are two supported approaches commonly used for scenarios like yours:

Option 1: Export devices from Microsoft Entra Admin Center

In the Microsoft Entra admin center, you can go to Devices > All devices and export the device list.

This export includes the Device ID, which corresponds to the same identifier used in Teams webhook payloads. This approach works well if you’re comfortable matching devices by name or other attributes after export.

Please note that you’ll need appropriate permissions (such as Global Administrator, Intune Administrator, Cloud Device Administrator, or Directory Reader) to access and export this data.

Option 2: Use Microsoft Graph for bulk extraction

For environments with hundreds of devices, the most scalable and reliable approach is to use Microsoft Graph to query Entra ID devices programmatically. This allows you to:

Retrieve Device IDs in bulk

Correlate them directly with webhook payloads

Integrate the data into your CMDB or automation workflows

This is the method most organizations use when the DeviceID is required for system‑to‑system integration rather than manual verification.

You may also want to consider posting your question in the Find Answers | Microsoft Power Platform Community.

This forum is dedicated to Power Platform topics and is supported by a knowledgeable community, including Microsoft experts and partners. By posting there, you may gain access to more specialized insights that could help identify a potential workaround more effectively.

I’m suggesting this because our Power Platform resources here are limited, and we want to avoid providing incomplete guidance. The Power Platform Community is better positioned to offer targeted assistance and also allows others to learn from your experience.

I hope these suggestions help clarify the validation process and support your workflow moving forward.

Wishing you a great day.

Answer 2

Hi @camaro1987,

Thank you for posting your question in the Microsoft Q&A forum.

To help clarify, the DeviceID that appears in Microsoft Teams webhook payloads is not displayed in the Teams Admin Center. While the Teams Admin Center provides useful information such as device name, hardware details, IP address, firmware version, and activity status, it does not surface the backend DeviceID that is included in webhook events.

That said, you can view this DeviceID in the Microsoft Entra Admin Center, as Teams devices are registered there as Entra ID device objects.

To locate the DeviceID in Entra, you can follow these steps:

Go to the Microsoft Entra admin center.
Navigate to Devices > All devices.
Search for the device using its name, operating system, or other available attributes.
Select the device to open its details.
In the Properties section, you’ll find the Device ID, which matches the ID shown in the Teams webhook payload, along with other identifiers such as the Object ID and Join Type.

This DeviceID is the same unique identifier used in webhook events and can be reliably used for correlation with your CMDB or automation workflows.

Please also note that viewing device details in the Entra Admin Center requires specific permissions. You’ll need at least one of the following roles:

Global Administrator
Intune Administrator
Cloud Device Administrator
Security Administrator (read access)
Directory Readers (read‑only access to device objects)

If you don’t currently have one of these roles assigned, you can ask an IT administrator with the appropriate permissions to retrieve this information on your behalf.

I hope this explanation helps clarify the behavior and supports your next steps. Please feel free to let me know how it goes or if you need any additional assistance. I’ll be happy to help.

I look forward to your reply.

If the answer is helpful, click on "Accept Answer" and please vote positively. If you have additional questions about this answer, click on "Comment".

Note: Follow the steps in our documentation to enable email notifications if you want to receive the email notification related to this thread.