Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi there,
I'm currently connecting from MS Outlook Data to Power BI, using the Microsoft Exchange Connector (Online) as main source, and also a sharepoint online list. It worked well when pulling the data from Outlook. I have 40 to 50 email addresses (data tables) for analysis. I open these tables using the exchange connector one by one, and then appending into two big tables to cleanse and transform the data. (Emails Received and Emails Sent)
However, there are two significant issues atm: 1. The refreshing speed is too slow, which takes 30-40 mins or even longer once clicking on refresh button on desktop. Nearly 100-500 per records per table. (40-50 tables)
2. The Power BI online service shows an internal service error when doing scheduled refresh, and the online service refresh is also disabled.
I was wondering if any of my steps brought great issues and slower the refreshing.
I've tried to open these fourty to fifty tables within one query and avoid appending in power query, however the result seems that Power BI online service refresh is still disabled and cannot support scheduled refresh.
There's another way I can think of is using Exchange Desktop connector, and deploying a on-prem gateway running 24/7 maybe...
Should I continue trusting the powerbi exchange online connector and fix my query, or do I need to think of another way of connecting the data? (middle storage methods and then load to powerbi: sql server, MS dataflow, or MS graph api...?)
Thank you in advance, and please let me know if you have any thoughts towards this topic. I'd really appreciate it.
Kind Regards,
p.s. Here is a screenshot with details of failing in Power BI online scheduled refresh by using Exchange Connector (Online):
Hi @jessical_7 ,
This error may be caused by a connection timeout or a large amount of data from the data source. Here are a few things you can try to solve this problem:
Increase the timeout period for data sources.
Reduce the size of the dataset or split it into multiple tables.
Check the permissions and settings of the data source.
Troubleshoot refresh scenarios - Power BI | Microsoft Learn
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 103 | |
| 79 | |
| 57 | |
| 51 | |
| 46 |