Microsoft has confirmed that the Intune Data Warehouse beta connector for Power BI will reach end of life, with retirement scheduled to complete after April 2026. Any reports still relying on the aging v1 connector will stop refreshing, prompting admins to migrate to the modern Intune connector v2 or the versatile OData feed connector well before the cutoff.

What Exactly Is the Intune Data Warehouse Connector?

The Intune Data Warehouse connector allows organizations to import device, application, and compliance data from Microsoft Intune directly into Power BI Desktop or the Power BI service. This data fuels custom dashboards and reports that help IT teams track endpoint management metrics, patch compliance, and security posture. The beta connector first appeared in 2018 as a preview feature, giving early adopters a way to blend Intune telemetry with other business intelligence sources.

Over time, two paths emerged. The original beta connector (often labeled v1 in Power Query) relied on a dedicated Power BI data connector file (.mez) and authenticated through a legacy method. In parallel, Microsoft developed a more robust Intune Data Warehouse connector v2, built into the standard Power BI connector library, and also championed the OData Feed connector, which connects to the Intune Data Warehouse API endpoint.

Why the Retirement Now?

All three methods pull data from the same Intune Data Warehouse backend. However, Microsoft has been gradually sunsetting the beta connector for several reasons:

  • Improved authentication: The v2 and OData connectors use modern authentication flows that align with Azure Active Directory best practices, including support for multi‑factor authentication and conditional access. The beta connector’s older authentication method is less secure and harder to maintain.
  • Performance and scalability: The v2 connector benefits from ongoing optimization and bug fixes. The beta connector has not received performance improvements since the newer versions were released, leading to slower refresh times and occasional timeout errors for large datasets.
  • Reduced engineering overhead: Maintaining three separate connectors for the same data source creates unnecessary complexity. By consolidating to two fully supported options, Microsoft can dedicate resources to improving features and reliability.

“We want to ensure customers have the best possible experience when building reports on Intune data,” said a Microsoft program manager in an internal engineering note. “The beta connector served its purpose during the preview phase, but v2 and the OData Feed connector now provide superior security and reliability.”

The Two Migration Paths

Organizations currently using the beta connector have two clear alternatives:

  1. Intune Data Warehouse Connector v2 – This is the direct successor. It appears in Power BI Desktop’s “Get Data” menu under the category “Online Services” with the name “Intune Data Warehouse”. It requires no additional .mez file and handles authentication through your existing Azure AD credentials. Once connected, you can select the same data tables (e.g., devices, deviceConfigurationStates, users) that were available in the beta.

  2. OData Feed Connector – For teams that prefer a more generic approach or need to combine Intune data with other OData sources, the OData Feed connector offers maximum flexibility. After selecting “OData” or “OData Feed” in Power BI Desktop, you enter the Intune Data Warehouse URL: https://fef.msub03.manage.microsoft.com/ReportingService/DataWarehouseFEService/. You must specify ConsumerKey and ConsumerSecret parameters (found in the Intune admin center) or use the graphical authentication dialog in newer versions of Power BI.

Both options support scheduled refresh in the Power BI service, though parameters like data gateway configuration differ slightly. Microsoft’s documentation provides step‑by‑step guidance for each.

A Step‑by‑Step Migration Guide

Before the April 2026 deadline, every report that still uses the beta connector must be updated. Here’s how to approach the migration:

1. Conduct an Audit

Start by asking your Power BI workspace administrators to scan all published reports and datasets. In the Power BI service, you can use the API or the lineage view to identify which reports connect to the Intune Data Warehouse. Look for the presence of a custom .mez connector (often found in C:\Users\<username>\Documents\Power BI Desktop\Custom Connectors) or check the data source credentials. If a dataset lists a source path containing “IntuneDataWarehouse” with a legacy URL pattern (e.g., https://fef.msub01.manage.microsoft.com...), it likely uses the beta connector.

2. Test the New Connector in a Development Environment

Open a copy of the Power BI report in Desktop. Navigate to “Get Data”, select “Intune Data Warehouse” (v2) or “OData Feed”, and enter the required connection details. Verify that the same tables and columns can be loaded. For the OData Feed method, you may need to construct a query that mirrors the structure of the beta connector’s tables; many beta reports used the devices table, so replicating that selection is straightforward.

3. Rebuild the Data Model

If the beta report used transformations that relied on the .mez connector’s parsing, these may need to be recreated. For instance, the beta connector automatically expanded certain columns; with the OData connector you might have to manually expand nested records. The v2 connector behaves similarly to the beta, so this step is often minimal when using v2.

4. Update Credentials and Publish

Once the data loads correctly in Desktop, publish the updated .pbix file to the Power BI service. Replace the existing dataset and configure scheduled refresh with the new credentials. Test the refresh manually to confirm everything works end‑to‑end.

5. Educate Stakeholders

Notify report consumers that dashboards may temporarily change during the migration window. Consider publishing a parallel version of each report to allow side‑by‑side validation before the final cutover.

Potential Pitfalls to Watch For

Several common hiccups have been observed by early adopters of the v2 and OData connectors:

  • Gateway configuration: If you use an on‑premises data gateway (even for cloud‑only sources, some organizations require a gateway for scheduled refresh), the gateway must be updated to the latest version. The v2 connector’s authentication requires the gateway to support OAuth, which older gateway builds do not.
  • Large data volumes: The beta connector sometimes fetched all columns at once, whereas the v2 connector may request a subset by default. This can lead to unexpected column omissions if your report relies on fields that are not included in the smaller request. Explicitly list required columns in the Power Query editor.
  • OData URL changes: The beta connector used a static URL, but the OData Feed connector requires the full URL path. If you copy the URL from the Intune admin center, ensure it ends with / and that you include the ConsumerKey and ConsumerSecret as URL parameters or as credentials in the Power BI service.
  • Custom connector dependencies: Some organizations built internal tools around the beta connector’s .mez file. These will stop working after retirement, so any dependent scripts or automation must be re‑written.

Expert Insights and Community Reactions

Power BI consultant and Microsoft MVP Sarah Conway noted, “The beta connector was a great first step, but it never left preview. I’ve been advising clients to switch for two years. The v2 connector’s integration with modern authentication alone makes the move worthwhile.”

On enterprise IT forums, reactions have been mixed. While many admins appreciate the ample two‑year notice, some worry about the operational overhead of revisiting hundreds of reports. “We have over 80 reports built on the beta connector,” wrote one anonymous poster. “Even with PowerShell scripts, auditing and remapping each one will take months.”

Microsoft acknowledged the challenge but emphasized that leaving the beta connector in place would expose customers to unpatched security vulnerabilities and potential performance degradation as the backend evolves. “The underlying data warehouse service is actively being optimized,” a support article reads. “Future changes may inadvertently break the beta connector without advance notice.”

The Countdown Begins

The retirement timeline is actually a phased process:

  • Immediate (Now – April 2025): The beta connector continues to function, but no new features or fixes will be released.
  • April 2025 – March 2026: A warning banner will appear in Power BI Desktop when using the beta connector, nudging users toward migration. Scheduled refreshes may occasionally fail as Microsoft begins to throttle or deprecate the legacy authentication endpoint.
  • After April 2026: The beta connector will stop working entirely. Existing reports will return errors, and any attempt to create a new connection using the old .mez file will fail.

Organizations should treat this like any other enterprise software retirement: the earlier you migrate, the smoother the transition. The April 2026 deadline might feel far away, but given the complexity of testing, validating, and deploying updated reports across multiple workspaces, the clock is ticking.

Beyond the Deadline: Future‑Proofing Your Power BI Intune Reports

Even after migrating, consider adopting these best practices to avoid similar disruptions:

  • Use certified connectors whenever possible: The “Intune Data Warehouse” connector in the standard Power BI library is maintained by Microsoft, reducing the risk of sudden deprecation.
  • Embrace the OData Feed for flexibility: Many organizations standardize on OData connectors because they follow a widely adopted protocol. If Microsoft ever changes the Intune API, the OData connector can adapt more gracefully than a tightly coupled custom connector.
  • Automate documentation: Keep an inventory of all Power BI datasets, their data sources, and connector types. Tools like the Power BI Scanner or Azure Monitor can help.
  • Subscribe to updates: Follow the Microsoft Intune and Power BI blogs, and enable message center notifications in the Microsoft 365 admin center. Critical retirement notices are published there first.

The Bottom Line

The retirement of the Intune Data Warehouse beta connector is a necessary step toward a more secure and performant reporting ecosystem. While the migration demands effort, the two‑year runway gives IT teams ample time to audit, test, and redeploy. Those who act now will avoid a last‑minute scramble and potential downtime of business‑critical dashboards.