What's New in BI for Intune

The 6 most recent releases are listed below. For older versions, see the release archive.

Version 70.0 Oct. 14, 2026

Release Date: October 14, 2026
AppSource Version: 1066

Summary

BI for Intune v70 adds Windows Protection support to App Protection reporting, expands filtering on the App Protection and Cloud PC Provisioning State pages, and adds a direct link to risky user details in the Azure portal.

This release also resolves an issue that prevented the App Protection page from populating, removes duplicate records from the App Protection State object, corrects swapped Sign-In Risk Level and Sign-In Risk State values, and updates all report links to the current Intune admin center.

Two semantic model parameters now default to False. See the Important Notes section.

Product Enhancements

Updated report links to use https://intune.microsoft.com instead of https://endpoint.microsoft.com.
Added App Protection Platform, Policy Name, and Policy Platform filters to the App Protection page.
Added the Cloud PC Provisioning Type field and filter to the Cloud PC Provisioning State page.

New Features

Added Windows Protection support to App Protection reporting.
Added a Risky User Details link to the Azure portal on the Risky Users page.

Bug Fixes

Fixed swapped values in the Sign-In Risk Level and Sign-In Risk State fields on the User Sign-Ins object.
Resolved an issue introduced in version 69 that prevented the App Protection page from populating.
Resolved duplicate records in the App Protection State object. When the same device, app, and policy are reported multiple times, the record with the latest sync date is retained.
Resolved an issue where affected provisioned Cloud PCs reported the Intune Device ID in place of the Azure AD Device ID. BI for Intune now retrieves the correct value when the source data supplies the wrong ID.

Semantic Model Changes

Added field User Risk Link to the User Risky object.
Added field Cloud PC Provisioning Type to the Cloud PC Provisioning State object.
Updated the App Protection Type, App Protection Policy Type, App Protection, and App Protection State objects to support Windows Protection.
Updated link fields to use the current Intune admin center: Device Link on Device, Device App Reliability Link on Device App Reliability, Device Performance Link on Device Performance, Proactive Remediation Link on Proactive Remediation, User Link on User, Manager Link on User Manager, and User Sign-Ins Link on User Sign-Ins.

Important Notes

Changed the default value of the AzureAD Application Assignment Enable parameter from True to False. Review this setting if you use application assignment reporting. See Semantic Model Parameters.
Changed the default value of the AzureAD Proactive Remediation Assignment Enable parameter from True to False. Review this setting if you use proactive remediation assignment reporting. See Semantic Model Parameters.
Hid the iOS/iPadOS Update Policies and macOS Update Policies pages because the corresponding policies are deprecated in Intune.
Always back up your custom reports before upgrading.

Version 69.0 July 20, 2026

Release Date: July 20, 2026
AppSource Version: 1065

Summary

BI for Intune v69 adds visibility into device encryption and local credential recovery by introducing the new Device Recovery Key and Device Local Credential objects. These objects report whether BitLocker recovery keys and Windows LAPS local administrator credentials are backed up, how many keys are stored, and when backups and refreshes occur.

This release also enhances the Encryption Status page with new fields and filters for recovery key and local credential backup status, and adds a field to the Device object indicating whether an operating system recovery key is stored.

In addition, a new semantic model parameter allows environments affected by a Microsoft Graph issue to continue loading a limited subset of Proactive Remediation data. See the Important Notes section.

This version requires two additional Microsoft Graph permissions. See the Important Notes section.

Product Enhancements

Updated the Encryption Status page by adding OS Recovery Key Stored and Local Credential Stored to the main table and filter pane to improve visibility into device recovery key and local credential backup status.
Added the ability to load Proactive Remediation data in environments where a Microsoft Graph issue would otherwise return an empty result, using the new AzureAD Proactive Remediation Assignment Enable parameter. See the Important Notes section.

New Features

Added new object Device Recovery Key to provide visibility into BitLocker recovery key backup status, including the number of keys stored and when they were first and last created.
Added new object Device Local Credential to provide visibility into Windows LAPS local administrator credential backup status, including the last backup and next refresh.

Semantic Model Changes

Added field OS Recovery Key Stored to the Device object.
Added new fields to the Device Recovery Key object: First Created Date, First Created Date (Days), Last Created Date, Last Created Date (Days), Recovery Key Count, Recovery Key Stored, Volume Type.
Added new fields to the Device Local Credential object: Last Backup, Last Backup (Days), Local Credential Stored, Next Refresh, Next Refresh (Days).
Added new parameter AzureAD Proactive Remediation Assignment Enable to the semantic model (Default: True). This parameter controls whether Proactive Remediation assignment details are collected during sync. In environments affected by a Microsoft Graph issue, set it to False to allow the remaining Proactive Remediation data to load. See the Important Notes section.

Important Notes

[Action Required] This version requires two additional permissions on the app registration in Microsoft Entra ID. Add BitlockerKey.ReadBasic.All and DeviceLocalCredential.ReadBasic.All. Without these permissions, the new recovery key and local credential data will not be reported. See Entra App Permissions.
If BitlockerKey.ReadBasic.All is not granted, the OS Recovery Key Stored field on the Encryption Status page displays False for all records, even on devices that have a recovery key backed up.
In some environments, Microsoft Graph returns a 503 error when BI for Intune requests Proactive Remediation assignment details, which causes the related data to return empty. This is a defect in the Microsoft API, not in BI for Intune, and PowerStacks has been working with Microsoft to have it corrected for more than a year. In an affected environment, it is not possible to retrieve the detailed deployment information for proactive remediations. To allow the rest of the Proactive Remediation data to load, set the AzureAD Proactive Remediation Assignment Enable parameter to False so that BI for Intune does not request the assignment details that trigger the error. If you would like to pursue a correction, PowerStacks can help you gather evidence of the Microsoft issue so you can open a support case with Microsoft. Contact support@powerstacks.com.
Always back up your custom reports before upgrading.

Version 68.0 June 17, 2026

Release Date: June 17, 2026
AppSource Version: 1061

Summary

BI for Intune v68 is a maintenance release that resolves a timeout issue introduced in v67 affecting App Deployment and Driver Updates data collection.

Bug Fixes

Resolved a timeout issue introduced in v67 that could cause App Deployment and Driver Updates data collection to time out during sync.

Version 67.0 June 7, 2026

Release Date: June 7, 2026
AppSource Version: 1059

Summary

BI for Intune v67 expands compliance reporting capabilities by introducing a relationship between Compliance Policy and Compliance Policy Setting data. This enhancement makes it easier to understand which settings are configured within a specific compliance policy and provides additional context when reviewing compliance configurations.

This release also enhances the Device Compliance and Device Compliance Settings pages with Policy Name filtering and drill-through capabilities, making it easier to analyze policy-specific compliance data.

In addition, compliance reporting data has been migrated to the Microsoft Export API and new semantic model parameters have been added to provide greater control over synchronization behavior and Compliance Policy State data collection.

Product Enhancements

Migrated Compliance Policy State and Compliance Policy Setting State data collection to the Microsoft Intune Export API to improve reliability and support larger datasets.
Added a new relationship between the Compliance Policy and Compliance Policy Setting objects, allowing compliance settings to be viewed in the context of the policy that configured them.
Updated the Device Compliance Settings page by adding Policy Name to the main table, filter pane, and drill-through pane.
Updated the Device Compliance page by adding Policy Name to the drill-through pane.

Semantic Model Changes

Renamed semantic model parameter AzureAD Export URL Wait (s) to AzureAD Export URL Post Wait (s) (Default: 1 second). See the Important Notes section.
Added new parameter AzureAD Export URL Get Wait (s) to the semantic model (Default: 1 second). This parameter controls the delay between Export API status checks during sync.
Added new parameter AzureAD Compliance Policy State Enable to the semantic model (Default: True). This parameter controls whether Compliance Policy State data is collected during sync.

Important Notes

Renamed semantic model parameter AzureAD Export URL Wait (s) to AzureAD Export URL Post Wait (s). This is a breaking change. Custom reports, documentation, or automation referencing the previous parameter name must be updated.
Always back up your custom reports before upgrading.

Version 66.0 May 10, 2026

Release Date: May 10, 2026 AppSource Version: 1058

Summary

BI for Intune v66 hardens the application deployment status sync against a Microsoft Intune Export API edge case. When the DeviceInstallStatusByApp export occasionally completed with a null export URL, sync jobs would fail mid-run. The new validation logic catches the null URL case and the updated handling clears the error message customers were seeing (Microsoft.Data.Mashup.ErrorCode = 10277).

If you’ve seen intermittent sync failures on application deployment data, this release resolves them.

Product Enhancements

Updated handling for the Microsoft Intune Export API DeviceInstallStatusByApp endpoint to address intermittent synchronization failures caused by incomplete API responses.

Bug Fixes

Fixed an issue that could cause synchronization failures with the following error message: We cannot convert the value null to type Text.. Microsoft.Data.Mashup.ErrorCode = 10277
Resolved a condition where the Microsoft Intune Export API returned a status of Completed while the export URL value was unexpectedly returned as null.
Added additional validation logic to ensure a valid export URL is present before processing completed export jobs.

Semantic Model Changes

Important Notes

This issue was caused by unexpected behavior from a Microsoft Intune API response associated with application deployment status exports.
Customers experiencing intermittent synchronization failures related to application deployment status data should update to this release as soon as possible.
Always back up your custom reports before upgrading.

Version 65.0 Feb. 21, 2026

Release Date: February 21, 2026 AppSource Version: 1057

Summary

BI for Intune v65 introduces expanded authentication reporting capabilities. This release adds the new User Sign-Ins Auth Details object, providing deeper visibility into authentication methods, requirements, and outcomes.

These enhancements support improved investigation and reporting of user sign-in activity across your environment.

New Features

Added new object User Sign-Ins Auth Details to provide expanded visibility into authentication activity and sign-in requirements.

Semantic Model Changes

Added new fields to the User Sign-Ins Auth Details object: Authentication Date, Authentication Date (Days), Authentication Method, Authentication Method Detail, Requirement, Result Detail, Succeeded.

Important Notes

Always back up your custom reports before upgrading.