File Picker and shared components

[SharePickle]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

No response

Issue description

I was wondering if we're allowed to use Microsoft's shared components like File Picker and Live Persona Card?
I see that Live Persona Card used by PnP Controls re-using the Microsoft's component from shared library, basically requesting the library and rendering the LPC, something like this:

await SPComponentLoader.loadComponentById(LIVE_PERSONA_COMPONENT_ID);

Is it OK if I load the File Picker component the same way as PnP controls loads LPC card and just re-use it?
We've got our own versions of LPC and File Picker, but these components changed so much we can't keep up with everything.
My idea is to re-use built-in components for better user experience.

So to summarize, is it OK to use or is it not allowed?

[Ashlesha-MSFT]

Hello @SharePickle,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

Loading internal SharePoint components (e.g., File Picker or Live Persona Card) using SPComponentLoader is technically possible, but not a supported approach in SPFx. These components are part of Microsoft’s internal implementation and are not included in the public API surface, so they can change or break without notice.

While some libraries like PnP controls may use similar techniques internally, they actively maintain their implementations to handle such changes. If you choose to use this approach directly, the maintenance and risk would be on your side.

Recommendation: Use supported options such as PnP SPFx React Controls, or build custom components using Fluent UI and Microsoft Graph.