From a spark to something real

Your idea. A head start.

You don't need to start from a blank canvas. Find a pattern that feels close, understand how it works, and make it your own.

01

Find your experience

Bring intelligence into Copilot, useful experiences into SharePoint, collaboration into Teams, or everyday tools into Connections. Use experience, component and technology filters to find your building block.

Explore the samples
02

Follow the source

Every sample belongs to its original repository. Read its README, prerequisites, permissions and license. Match the sample's SPFx version and supported Node.js tooling before installing.

Check the compatibility guide
03

Add your spark

Run the sample in a development environment, understand its data and permissions, then adapt it. Small improvements count. Share what you learn with the people who build alongside you.

Give something back

One framework. More places to build.

SPFx, the SharePoint Framework, is the extensibility foundation behind these Microsoft 365 experiences. A single solution can bring together different component types and supported hosts. The gallery reflects that: a sample can appear under more than one experience.

  • Copilot: interactive components that turn a conversation into something you can explore and act on.
  • SharePoint: web parts, custom forms and extensions for useful pages, portals and connected workspaces.
  • Teams: tabs, personal apps and connected collaboration experiences, where the source explicitly supports them.
  • Connections: Adaptive Card Extensions that bring timely information and actions into the flow of work.

A few things worth knowing

  • Samples are community learning resources, not production support commitments. Review code, permissions and dependencies before use.
  • Older versions stay discoverable. A version badge is a declaration from source metadata, not a guarantee that a sample runs on today's tooling.
  • Some legacy metadata is being corrected. Sample details identify known issues; the source README and package files remain authoritative.
  • Bot-powered ACE examples use their own framework. They do not receive a made-up SPFx version.
  • Your saved collection stays in your browser. This gallery does not add analytics, accounts or cross-site collection tracking.
How the catalog is built
Microsoft 365 and Power Platform Community Contributor badge

Sharing is caring.

Share what you know.

Contribute a sample, improve the docs or help someone get started. Sample contributors can opt in to the PnP Recognition Program and share their community contributor badge.

Have something to show? Sign up for a community call demo. Fill in the form and we'll arrange a slot based on your availability.