Blog Post

Intune Customer Success
4 MIN READ

Updated experience for Intune device compliance reports

Intune_Support_Team's avatar
Intune_Support_Team
Silver Contributor
Jun 16, 2023

By: Tyler Castaldo – Sr. Product Manager | Microsoft Intune

 

Reporting is crucial to any organization’s device compliance story. This is even more important when using Azure Active Directory (Azure AD) Conditional Access policies that restrict access to your organization’s resources based on Intune compliance status. As we’ve continued to receive feedback from customers on how to make this reporting better, we’ve been working on specific improvements to the device compliance reports in Intune. Some of these are available today, while others are just around the corner. We also published a Message Center: MC591858 detailing these updates.

 

These improvements focus on:

  1. Modernizing our reporting infrastructure.
  2. Providing a consistent and simple report experience
  3. Updating the compliance policy monitoring experience.

 

Modernizing the compliance reporting infrastructure

To improve consistency between reports, including between top-level summaries and their detailed sub-reports or views, we’re consolidating back-end data sources, wherever possible. Using fewer data sources means these reports pull from the same data, ensuring consistency throughout the Intune admin center.

 

This infrastructure change also gives us the opportunity to make queries more efficient. In cases where the data source consolidation doesn’t allow us to load reports faster, such as data heavy, comprehensive reports, we’ve redesigned these as organizational reports. These organization reports will appear in the Reports section in Intune admin center and will have an improved, long-running-task experience that allows you to run a report in the background, from start to finish, while you perform other tasks in the admin center. Regardless of whether you run an operational report or a monitor, generated automatically, or an organizational report that’s generated manually, these reports are designed to load without timing out.

 

We’re also standardizing all compliance reports to show only one compliance state per device (or one compliance state per policy per device). If multiple users share the same device, only the user who used the device during the last compliance update will appear in reporting. If a compliance policy is deployed to a device group and no user was signed in during the last compliance update, “System account” will be displayed instead (this includes the built-in compliance policy). This change will clarify the latest compliance state of the device as well as eliminate double counting in aggregate reports (such as the Policy compliance and Setting compliance reports).

 

This infrastructure update allows us to support policies based on the settings catalog, which means we’re adding Linux support to all compliance reports (except the Windows health attestation report that is only scoped to Windows devices).

 

Simplifying the reporting experience

In addition to improving the data and performance of the reports, the updates to the infrastructure, coupled with improvements to the user interface tools, ensures all compliance reports will support:

  • Efficient paging for reports with many rows
  • Exporting data in CSV format
  • Searching for partial values in all columns
  • Filtering columns that have a constant set of values (such as operating systems)
    • Those with varying values, such as devices or usernames, can still be searched on
  • Sorting all columns
  • Scope tags
    • Important: Scope tag support means that some admins who were able to see all compliance details, or numbers of compliant or noncompliant devices or settings for the entire tenant, might no longer have access to this data. We recommend reviewing your role-based access control (RBAC) roles and scope tags to ensure all admins have the access they need for their specific roles.

 

Updating the compliance policy monitoring experience

As part of our reporting experience improvements, we’re also redesigning the overview and properties experience for compliance policies to be a similar reporting experience for device configuration profiles and the overall new Devices experience currently in public preview.

 

These are the specific changes you’ll see in the coming weeks:

  • The pane navigation will be retired and replaced by a single pane split into two tabs, Overview and Properties.
    • The Overview tab will contain:
      • A device compliance summary in bar chart format. This summary links to a detailed Device status report, which includes the same paging, exporting, searching, filtering, and sorting functionality described earlier.
      • A link to a refreshed Per-setting status report, which will also have the paging, exporting, searching, filtering, and sorting functionality.
    • The Properties tab will contain the same information and experience as seen today in the Properties pane under the Manage header in the pane navigation. This is still the place you’ll go to edit existing policies.

 

We’re retiring the following elements:

  • The circular (donut) summary charts on the current Overview pane—being replaced by the Device compliance summary and Device status report.
  • The Essentials section—this information can already be found in the Properties pane and will continue to appear in the Properties tab.
  • The User status report—the data found in this report today can be found in the new Device status report by either:
    • Sorting the device report by the User Principal Name column.
    • Searching for a specific username in the search box, which will limit the records to those matching that user.

 

Additional improvements and updates

We’ve already made improvements to the following reports and monitors:

  • Under Reports > Device compliance > Reports
    • Device compliance
    • Device compliance trends
    • Noncompliant devices and settings
    • Devices without compliance policy
  • Under Devices > Monitor
    • Noncompliant devices
    • Policy noncompliance
  • Within a device’s Monitor section
    • Device compliance
  • Under Devices > Compliance policies  
    •  Retire noncompliant device

 

In addition to the updates to the compliance monitoring experience discussed above, we’re also going to release new versions of the Policy compliance and Setting compliance reports under Reports > Device compliance > Reports, then remove the existing versions that are currently under Devices > Monitor once the preview ends in the coming weeks.

 

We hope these improvements enhance your management experience, stay tuned to What’s new in Intune for the release! If you have any questions or feedback leave a comment below or reach out to us on Twitter @IntuneSuppTeam.

Updated Nov 09, 2023
Version 3.0

21 Comments

  • JamesMooney's avatar
    JamesMooney
    Copper Contributor

    I've seen a lot of issues of late with devices reporting back Defender score and failing compliance even though they meet the policy requirements.

  • HRtech's avatar
    HRtech
    Copper Contributor

    For the past week I've had two machines showing "Not Compliant" for Secure Boot but secure boot is on for both machines. Tried manually syncing and even changed the Compliance status validity period to 1 day but they still haven't updated. Are these updates affecting this issue?

  • harevalo's avatar
    harevalo
    Copper Contributor

    Everyone is correct, compliance number don't match on any screen/report you go to. We want to use Intune as single source to track progress.

     

    When is this "upcoming update" happening? Everyone would benefit from reports being cleaned up and showing correctly.

  • Nick_Powell115's avatar
    Nick_Powell115
    Copper Contributor

    As of writing this, my Intune Admin Center is still showing discrepancies in reports vs individual compliance records. A generated report will show multiple devices as non-compliant, but if I go to Devices > All Devices > %DEVICENAME% > Device Compliance it will show the device as compliant with assigned policies.

     

    Is there any update as to when the Intune Admin Center will properly report compliance status across all sections of individual records, reports, etc.?

  • Anwer1007's avatar
    Anwer1007
    Copper Contributor

    Is this impact affected for all MAC OS enroller devices???

  • Andrew Emmett's avatar
    Andrew Emmett
    Copper Contributor

    macOS devices that operate on a 1-1 basis work great, but will this affect macOS devices that are deployed in a Shared Configuration.  I think you sometimes refer to these as 'Enrolled without User Affinity' or 'Userless Devices'. I work in an education environment with both personally assigned and Shared Classroom devices. When you look at shared devices from the device perspective, the assigned compliance policies are flagged as compliant, however the overall machine compliance status is not. This means that we have to make CA exceptions for Labs/Classrooms that are user by multiple users (who are licenced btw). It seems weird that you can't calculate the compliance of the device as I assume you're actually evaluating the compliance state of all the assigned compliance polices and using this to decided the status of the device. Is this an intentional design or can you explain why compliance for shared macOS devices operate differently to Windows & iOS?

  • AlphaSeb's avatar
    AlphaSeb
    Copper Contributor

    Thats much needed. Device compliance is really a nightmare in the moment. Reporting different statuses in different views, no proper errors. Custom Compliance Policies show as "Not Applicable" even though they are.

  • Geza1's avatar
    Geza1
    Copper Contributor

    I don't care about the looks, I would be just super happy if Intune would not report different states in different views, and compliance reporting would be accurate. Now sometimes in 1 view it shows you're out of compliance, in another that you're in compliance, in some views it doesn't show some compliance status at all. As someone relying on this for our security I'm super annoyed when we get some kind of errors for 10-20% of our userbase. When that means thousands of users it can be catastrophic.