Try It
Print
Created On
byJohn Marcum

Version 28.0 (AppSource Version 1026)

Copy the URL link to this section to share

BI for Intune Version 28.0, shown as version 1026 in AppSource, was released on October 31, 2023.

Below are the changes in version 28.0:

  • Features:
    • Added a new page, “Windows Driver Updates”. 
      • This new page shows the driver update profiles that are in Intune. You can see approval status for each driver and the status of the drivers installing on devices.
      • New categories and fields in the data model associated with the “Windows Driver Updates” page include:
        • Windows Driver
          • Driver Classification
          • Driver Count
          • Driver Manufacturer
          • Driver Name
          • Driver Version
          • Release Date (Date)
          • Release Date (Days)
        • Windows Driver State
          • Approval Status
          • Category
          • First Deployment (Date)
          • First Deployment (Days)
        • Windows Driver Update
          • Approval Method
          • Driver Update Count
          • Driver Update Name
          • Is Assigned
        • Windows Driver Update Assignment
          • Assignment Group
          • Assignment Type
        • Windows Driver Update State
          • Alert Type
          • Driver Update Aggregated Cancelled
          • Driver Update Aggregated Error
          • Driver Update Aggregated Progress
          • Driver Update Aggregated State
          • Driver Update Aggregated Sub-Status
          • Last Scan (Date)
          • Last Scan (Days)
    • Added new page “UC Driver Updates”.
      • This page is very similar to the “Windows Driver Updates” the difference being the data source. This data is being pulled from the Windows Update for Business Log Analytics workspace.
      • New or changed categories and fields in the data model associated with the “Windows Driver Updates” page include:
        • Update Compliance State Device
          • Removed the “Update Display Name” field. This change might break existing custom reports. You should replace the field with the new “Update Display Name” field from the “Update Compliance State” category.
        • Update Compliance State
          • Added “Update Display Name” field.
        • Update Compliance State Service
          • Added “Update Manufacturer” field.
          • Added “Update Version” field.
  • Enhancements:
    • New fields added to the “Configuration State” category:
      • Last Status Configuration
      • Last Status Configuration (Days)
    • Changes to the “Device Configuration” page:
      • Added field “Last Status Configuration”.
      • Added page filter “Last Status Configuration”.
      • Added page filter “Last Check-In”.
    • Changes to the “iOS/iPadOS Update Policies” page:
      • Added page filter “Last Status Update Policy”.
      • Added page filter “Last Check-In”.
    • Changes to the “macOS Update Policies” page:
      • Added page filter “Last Status Update Policy”.
      • Added page filter “Last Check-In”.
    • Changes made to the “Windows Update Rings” page:
      • Added page filter “Last Status Update Ring”.
      • Added page filter “Last Check-In”.
    • Renamed the “BitLocker Status” page to “Encryption Status”.
      • This was done to reflect that Mac encryption status is also seen on this page.
    • Changes made to the “Encryption Status” page:
      • Replaced “Blank” TPM version with “Unknown” to indicate that the device might have a TPM, but Intune does not report the version.
      • Added page filter “TPM Version”.
    • Changes to the “UC Quality Update” page:
      • Added a KPI for “Not Latest”.
    • Renamed the “Device Scripts” page to “Scripts”.
    • Hotlinks on the “Windows Health” page now goes directly to Endpoint Analytics.
    • To improve sync performance MS Graph API was replaced by by the Export API for the following items:
      • Configuration State
      • Windows Update Ring State
      • iOS/iPadOS Policy Update
      • macOS Policy Update
  • Bug Fixes:
    • Encryption Status Page was blank.
      • This was due to an API change by Microsoft. The model has been updated to use the new Microsoft API.
    • Windows 11 upgrade readiness was showing incorrect information.
      • Changed to a new Microsoft API to get accurate information.
  • Important Notes: