Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
PowerMaverik
New Member

Intune DetectedApp issue on Load

Hi,

I'm building a PowerBi report with Intune Data. The connection is via Power Query + Graph.
I want to load DetectedApps with related device. I've found the right table but when i try to apply it load until 1.2MB and then drop with error "the connection was close forcebly". 
Someone are facing the same problem?

1 ACCEPTED SOLUTION
rohit1991
Super User
Super User

Hi @PowerMaverik

 

I'am also facing the similar issue when working with Intune and Power BI, especially when pulling data through Microsoft Graph. That particular DetectedApps endpoint can be pretty heavy it's nested and often includes a long list of managed devices per user or app, which really slows down the load.

 

A few things that helped in my case:

  • Limit the data at the source If you're using Power Query to hit the Graph API directly, try filtering the data in the query itself before it even reaches Power BI. This reduces the amount of data Power BI needs to process.

  • Avoid expanding all columns by default, Sometimes expanding nested fields like managedDevices without filtering first causes massive performance hits.

  • Consider using a staged dataset, I ended up pulling the raw Intune data into an Azure SQL table via a scheduled job, cleaned it up there, and then pointed Power BI to the cleaned table. Not ideal for real-time, but much more stable for regular reporting.

Also, worth checking if you're hitting any throttling limits from Graph during load I've seen that silently break queries mid-load without throwing obvious errors.

If you can share a bit more about how you're connecting (Graph connector, custom connector, or manual query), I might be able to give more specific advice.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

View solution in original post

6 REPLIES 6
v-csrikanth
Community Support
Community Support

Hi @PowerMaverik 

It's been a while since I heard back from you and I wanted to follow up. Have you had a chance to try the solutions that have been offered?
If the issue has been resolved, can you mark the post as resolved? If you're still experiencing challenges, please feel free to let us know and we'll be happy to continue to help!
Looking forward to your reply!

Best Regards,
Community Support Team _ C Srikanth.

v-csrikanth
Community Support
Community Support

Hi @PowerMaverik 

I wanted to follow up since I haven't heard from you in a while. Have you had a chance to try the suggested solutions?
If your issue is resolved, please consider marking the post as solved. However, if you're still facing challenges, feel free to share the details, and we'll be happy to assist you further.
Looking forward to your response!


Best Regards,
Community Support Team _ C Srikanth.

v-csrikanth
Community Support
Community Support

Hi @PowerMaverik 
As highlighted by @rohit1991 @lbendlin ,the proposed approach appears to effectively address your requirements. Could you please confirm if your issue has been resolve
If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.
Best Regards,
Community Support Team _ C Srikanth.

rohit1991
Super User
Super User

Hi @PowerMaverik

 

I'am also facing the similar issue when working with Intune and Power BI, especially when pulling data through Microsoft Graph. That particular DetectedApps endpoint can be pretty heavy it's nested and often includes a long list of managed devices per user or app, which really slows down the load.

 

A few things that helped in my case:

  • Limit the data at the source If you're using Power Query to hit the Graph API directly, try filtering the data in the query itself before it even reaches Power BI. This reduces the amount of data Power BI needs to process.

  • Avoid expanding all columns by default, Sometimes expanding nested fields like managedDevices without filtering first causes massive performance hits.

  • Consider using a staged dataset, I ended up pulling the raw Intune data into an Azure SQL table via a scheduled job, cleaned it up there, and then pointed Power BI to the cleaned table. Not ideal for real-time, but much more stable for regular reporting.

Also, worth checking if you're hitting any throttling limits from Graph during load I've seen that silently break queries mid-load without throwing obvious errors.

If you can share a bit more about how you're connecting (Graph connector, custom connector, or manual query), I might be able to give more specific advice.


Did it work? ✔ Give a Kudo • Mark as Solution – help others too!
PowerMaverik
New Member

Hi, 
Data Warehouse don't get this type of data but only deployed apps and the only way is via Graph.
Thanks for your reply 

lbendlin
Super User
Super User

your data retrieval is taking too long and running into execution timeouts. See if your connector supports modifying this. If not, run more, smaller queries, or run them outside of Power Query. Why not  Use the Intune Data Warehouse - Microsoft Intune | Microsoft Learn ?

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors