Share via

App Builder (Frontier) – Can't select a SharePoint connection?

Lena 0 Reputation points
2026-05-29T12:19:08.31+00:00

Hii everybody,

I am currently using the App Builder (Frontier) in Microsoft 365 Copilot and am encountering inconsistent behavior regarding the SharePoint connection.

Problem:

When I explicitly ask about a SharePoint connection in the chat or try to configure one, the App Builder responds that it cannot do so or does not support it.

However, I’ve already had a case where, after a lot of back-and-forth, I managed to get the App Builder to suggest or use a SharePoint connection.

👉 This seems inconsistent to me:

On the one hand: “SharePoint connection not possible”

On the other hand:

  • Used in the background
  • and sometimes possible after several iterations in the prompt

Questions:

  • How do I get the Builder to connect my current app to SharePoint?
  • Is there a way to reliably get the App Builder to use an existing SharePoint list or site?
  • Is this inconsistent behavior a known issue in the Frontier Preview?

Thank you so much!

Kind Regards

Microsoft 365 and Office | SharePoint | Development
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teddie-D 16,370 Reputation points Microsoft External Staff Moderator
    2026-05-29T14:41:21.3633333+00:00

    Hi @Lena 

    What you’re seeing is expected behavior with App Builder (Frontier) and does not appear to be caused by a configuration issue on your side. 

    There are two separate SharePoint-related behaviors in App Builder, which can make the experience confusing: 

    -SharePoint-backed resources: App Builder can create and use SharePoint-based assets (such as sites or Microsoft Lists) as part of the app’s internal storage.  

    -External SharePoint connections: App Builder does not currently provide a supported or documented way to connect an app directly to an existing SharePoint list or site. 

    So, when App Builder shows SharePoint connection is not supported, that is expected. When it appears to work after several prompts, it is typically generating new app data internally or approximating the requested behavior, rather than establishing a persistent connection.

    There is currently no supported way in App Builder (Frontier) to reliably bind an app to an existing SharePoint list or site. App Builder is designed primarily as a lightweight no-code app creation experience and does not yet expose configuration options for external data connections. 

    Currently, there is no publicly documented guidance confirming this as a specific known issue. Since Frontier is still experimental, some responses may vary depending on the prompt or session. That can make it feel inconsistent, even though direct SharePoint integration is not officially supported today. 

    Reference: App Builder agent available via Frontier starting October 28 - M365 Admin 

    This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.        

    I hope this information is helpful.  

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

    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?

    0 comments

  2. AI answer

    2026-05-29T12:19:27.5766667+00:00

    App Builder’s behavior with SharePoint is constrained by its current design and preview limitations, which explains the inconsistency being observed.

    Key points from the current capabilities and limits:

    1. How App Builder connects to data
      • App Builder apps “can only connect to data in Microsoft Lists and do CRUD operations.”
      • App data is stored “either in the app or in SharePoint lists,” and App Builder “currently supports the SharePoint connector.”
      • The SharePoint site that backs an app is created and managed automatically; it is “managed separately” from the app itself and must be deleted manually if no longer needed.
      This means App Builder is allowed to use SharePoint (via Lists and the SharePoint connector) but manages that wiring itself. It is not a general-purpose connection UI like Power Apps where connectors are explicitly configured step by step.
    2. Why the behavior feels inconsistent
      • App Builder is an AI-driven, experimental Frontier feature. The documentation explicitly calls out that “you might see a blank screen, errors, or parts of the app that don’t work as expected,” and that it “doesn’t always get things right on the first try.”
      • It also notes that the agent “may have difficulty with complex design requirements.” Requests about specific connection wiring or reusing existing sites/lists can fall into that category.
      • As a result, prompts that are very similar can sometimes lead to different internal choices by the agent (for example, creating a new list vs. surfacing that it “can’t” connect), which matches the “sometimes it uses SharePoint in the background, sometimes it says it can’t” experience.
    3. How to get the Builder to connect an app to SharePoint Within current limits, the reliable pattern is:
      • Design the app around Microsoft Lists as the data source (for example: “Create an app that tracks issues in a list with columns X, Y, Z”).
      • Let App Builder generate the schema and backing list. That list will be stored in the app’s SharePoint site using the supported SharePoint connector.
      • Manage the resulting SharePoint lists and site from SharePoint admin tools as needed; App Builder does not expose a rich connector configuration surface.
      There is no documented, supported way in App Builder to manually pick or bind a specific SharePoint connector instance the way Power Apps does, nor to override the internal connection handling.
    4. Using an existing SharePoint list or site
      • The documentation states that apps “can only connect to data in Microsoft Lists,” but it does not document a reliable, supported flow for binding an App Builder app to an arbitrary existing SharePoint list or site chosen by the maker.
      • It instead emphasizes that App Builder generates the schema and uses SharePoint lists as its storage behind the scenes.
      • Because of that, there is no guaranteed method described to always attach an app to a pre-existing list or site; any success achieved via prompt experimentation is not a documented, stable behavior.
    5. Is this a known Frontier/preview limitation?
      • App Builder is part of the Frontier program, which explicitly provides “early access to experimental features” that “may change” and where limitations are expected.
      • Known limitations include: only Microsoft Lists as data source, only the SharePoint connector, no manual code editing, and that the agent may struggle with complex requirements.
      • The general class of “inconsistent or partially working behaviors” is acknowledged: users “might see … parts of the app that don’t work as expected,” and the guidance is to iterate with the agent and test thoroughly before sharing.

    In practice, for now:

    • Treat SharePoint usage as something App Builder manages automatically when it creates and stores data in Microsoft Lists.
    • Do not rely on being able to consistently bind to an existing SharePoint list or site; that scenario is not documented as supported.
    • Expect some inconsistency in the preview and validate each app’s data connections and behavior before rolling it out.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.