Share via

Unable to integrate SharePoint as a data source in "Vibe Power Apps".

Avani Lalith Kumar 0 Reputation points
2026-05-19T15:16:05.0366667+00:00

While trying to integrate SharePoint as a data source, I’m unable to import it in Vibe Coding, as it keeps loading for a long time. I checked the estimated duration for importing 1,000 rows from SharePoint, and it shows approximately 1–3 hours.

Is there any alternative way to import SharePoint data faster?

Ref. Image:
User's image

Does anyone have any suggestions? Thanks in advance for your help!

Microsoft 365 and Office | SharePoint | Development
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Hin-V 15,085 Reputation points Microsoft External Staff Moderator
    2026-05-19T16:56:36.7566667+00:00

    Hi @Avani Lalith Kumar

    Thank you for sharing your concerns. 

    First, I’d like to clarify that this is a user‑to‑user support forum. Moderators participating here do not have access to backend systems, nor can we directly intervene in Microsoft product functionality. Our role is limited to providing technical guidance and sharing best‑practice recommendations based on reported issues, requests, and scenarios.       

    Based on my research, this behavior appears to be related to how Power Apps Vibe processes SharePoint data source. When connecting directly to a SharePoint list, the platform relies on the SharePoint connector, which can become slower with larger datasets, especially when the list contains many columns or complex field types. Additionally, SharePoint integration in Vibe is currently read-only and primarily optimized for rapid prototyping, rather than large-scale data operations. 

    Reference: Use SharePoint lists as a data source in Power Apps vibe (preview) - Power Apps | Microsoft Learn 

    For improved performance, you may want to consider moving your data into Dataverse. As the native data platform for Power Apps (including Vibe apps), Dataverse typically provides faster and more efficient data access, since queries run directly within the platform rather than through external connectors. 

     image

    You can refer via: Performance considerations for Power Apps - Power Apps | Microsoft Learn 

    Please note that this summary is based on my own findings and may not fully address your concerns. Since this forum does not have a dedicated Power Platform tag, you may receive more relevant guidance by posting your question in the Find answers across the Microsoft Power Platform Community. The reason I suggest posting a new topic there is that in the general Q&A Forum, resources and expertise on Power apps are limited. In the Microsoft Power Platform Community Forum, you’ll find the most qualified group of respondents, and other partners who regularly read the forums can share their knowledge or learn from your interaction.  

    If you have any additional concerns, feel free to comment below. I would be more than happy to assist. 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.   

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.