Share via

Defender for Endpoint Vulnerability Management Browser Extensions not populating

George Zerphey 176 Reputation points
2025-01-07T21:04:33.3333333+00:00

We recently started a trial of the Defender Vulnerability Management add-on and applied the licenses to our users. Everything seems to be working fine, but unfortunately on a small handful of the browser extensions and hardware information are populating.

Is there something I'm missing in the process to have that information show up in the system? I know there is a delay in newly licensed features taking effect, but I assumed a day or two would be all we need for that. At this point its been about 5 days and only 8 or about 700 devices have shown up.

Thank you,

Microsoft Defender for Cloud
Microsoft Defender for Cloud
An Azure service that provides threat protection for workloads running in Azure, on-premises, and in other clouds. Previously known as Azure Security Center and Azure Defender.
1,469 questions
Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,205 questions
Microsoft Defender for Cloud Apps
Microsoft Defender for Cloud Apps
A Microsoft cloud access security broker that enables customers to control the access and use of software as a service apps in their organization.
164 questions
0 comments
Accepted answer
  1. Raja Pothuraju 11,170 Reputation points Microsoft Vendor
    2025-01-08T11:43:35.4133333+00:00

    Hello @George Zerphey,

    Thank you for posting your query on Microsoft Q&A.

    Based on your description, I understand that you signed up for the Defender Vulnerability Management add-on free trial and assigned licenses to users to gather information on browser extensions and hardware/firmware assessments. However, even after five days, no data has populated for browser extensions or hardware/firmware assessments.

    After consulting with the Product Group (PG) team, I got to know that this is a known issue on our end. Many customers have reported similar problems through support tickets. Our engineering team has identified the issue, and a fix has been released. The fix is expected to be deployed globally to all tenants by the end of this week.

    I recommend waiting 2–3 more days and then checking the status. If the issue persists beyond this week, please let me know so I can escalate it further with my team to ensure it gets resolved.

    I hope this information is helpful. Please feel free to reach out if you have any further questions.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Thanks,
    Raja Pothuraju.

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.