# Check the explicit EPM report permission when a reader receives HTTP 403

> Why can an Intune reader lose access to EPM report data despite device-configuration read permission?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-268-check-the-explicit-epm-report-permission-when-a-reader-receives-http-403/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:27:28+00:00
- Modified: 2026-09-10T01:23:48+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Why can an Intune reader lose access to EPM report data despite device-configuration read permission?

## Potentially affected

Use this diagnostic for an intended EPM report consumer, including an existing custom-role reader. Keep authorization failure separate from an authorized report that has no recent matching data.

## DSE recommendation

Inspect the dedicated report permission before adding broad administration rights.

## Article

## Source facts

Access to Endpoint Privilege Management reports in the Intune portal or Microsoft Graph requires the EPM Policy Authoring View Reports permission, identified as EpmPolicy.ViewReports in Graph. Device configurations Read, which previously allowed access, is no longer sufficient. Without that permission, the privilegeManagementElevations endpoint returns HTTP 403. Separately, report content depends on each device’s configured reporting scope and is processed once every 24 hours. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/epm/monitor-reports).

## Applicability

Use this diagnostic for an intended EPM report consumer, including an existing custom-role reader. Keep authorization failure separate from an authorized report that has no recent matching data.

## DSE recommendation

Inspect the dedicated report permission before adding broad administration rights. Ask the Intune role owner to confirm the reader’s approved reporting responsibilities and effective role assignment. If a change is justified, grant the specific reporting capability through the organization’s scoped role process. Do not add policy creation, assignment, or elevation-approval authority merely to recover read access.

## Verification

With the intended identity, compare the report request before and after the approved role adjustment. Confirm a report can be read and that unrelated management operations remain unavailable. Then evaluate reporting scope and processing delay if expected entries are missing. Save the endpoint, response status, and role evidence without exporting sensitive elevation details unnecessarily.

## Official references

[Microsoft Learn: Monitor your Endpoint Privilege Management policies for Microsoft Intune](https://learn.microsoft.com/en-us/intune/epm/monitor-reports).

## Primary reference

- Name: Monitor your Endpoint Privilege Management policies for Microsoft Intune - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/epm/monitor-reports
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check the explicit EPM report permission when a reader receives HTTP 403,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-268-check-the-explicit-epm-report-permission-when-a-reader-receives-http-403/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.