# Power Apps Samples is a curated shelf of community built Power Apps examples > The Power Apps Samples repository collects community contributed Power Apps solutions that demonstrate different usage patterns, and it is being retired in favour of a single Power Platform Samples repository. It suits makers and developers who want a worked example to copy rather than a blank canvas. **pnp/powerapps-samples** — Contains curated community Microsoft Power App samples - Repository: https://github.com/pnp/powerapps-samples - Website: https://aka.ms/powerplatform-samples - Stars: 538 · Forks: 345 - Language: Unknown - License: MIT - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/pnp-powerapps-samples ## A shelf of worked examples, not a product The repository description is that it contains curated community Microsoft Power App samples, and the documentation expands on that: community samples that demonstrate different usage patterns for Power Apps. That phrase is the key to reading the whole thing. These are not libraries, not a framework and not a component you install. Each sample sits in its own solution, which is the native Power Platform packaging unit, and the value of a sample is that you can import the solution, look at how the screens, formulas and data sources are wired, and then copy that approach into your own app. The repository is part of the Microsoft Power Platform community project, run under the Microsoft Open Source Code of Conduct, and the authors section explains the governance plainly. The contributors are all community members who volunteered their time to share code samples, and the work is done as an open source community project with each sample contained in its own solution. Some samples come straight from the feature teams or from the PnP team, and others are shared by the community. The repository is MIT licensed and is not archived, with the last push recorded on 2026-09-28. There are no GitHub releases, which makes sense for a collection of solutions rather than a distributed artefact, since there is nothing to version as a single download. The topic list of hacktoberfest, powerapps and powerplatform tells you that contributions arrive through the usual seasonal route as well as the regular one. ## This repository is on its way out, and that changes how you use it The most important line in the documentation is the important callout at the top. The maintainers are in the process of moving all the samples from product specific repositories like this one into a single repository for all Power Platform Samples, and they ask that pull requests be created in that repository instead. The contribution guidance confirms it: new samples belong in the Power Platform Samples repository, and issues, suggestions and fixes to the existing samples here are still welcome. That is a migration, not an abandonment, and the distinction matters for what you do next. If you want to submit a new sample, this is the wrong place, and the documentation points you to the contribution guidance in the consolidated repository so your pull request gets processed quickly. If you want to fix a sample that already lives here, that work is still accepted. If you want to use a sample, the ones here are still importable, and the migration is a background process rather than a removal. For anyone planning a long lived project on top of a sample, the practical advice is to treat the solution file as a reference implementation rather than a dependency. Copy the pattern into your own solution, own your own connection references and your own data model, and you are unaffected by where the sample itself is hosted. ## What is actually in the samples directory The directory listing is the best evidence of what the collection covers, and it reads as a catalogue of small, specific problems rather than a set of large applications. There is InvoiceProcessing, Timesheet, Tagbox, SearchMovies and Keyword-Tagging for the business data side. There is a group of reusable interface pieces: a clock time picker component, a cascading dropdown component, a calendar component, a people picker built on the Microsoft Graph Toolkit, and a Tagbox for chip style selection. There are sample apps with a more playful bent, including TicTacToe, ChuckNorrisIO and PowerHappening, plus a container examples directory and a README template that new sample authors are expected to follow. Several entries point at the platform's own extension mechanisms rather than at business apps. The SVG examples, the US map built with SVG images and the bodypart gallery are about the custom image and gallery capabilities. The accessibility color contrast checker is about building an accessible app. The COVID vaccine survey is a survey app. The app-login and company-pulse-creator-kit entries are closer to templates and kits than to individual samples, and the PDF Reader Creator Kit is a component kit with its own package. So the collection spans three things, and it is worth being clear about which one you are reaching for. Some entries are full sample apps showing an end to end pattern. Some are components you can reuse. And some are reference examples of a specific platform feature, such as custom images or accessibility, which are arguably the most valuable of the three for a maker who already knows how to build and wants to check a specific technique. ## Importing a sample, and what the documentation does not cover The documentation does not give you the import steps inline. It points to a wiki article titled how to use Power Apps samples, hosted in this repository's wiki, and tells you to refer to that to get started. That is where the actual procedure lives, and it is the first thing to open if you are new to importing Power Platform solutions. The mechanism the samples are built for is the standard Power Platform one. A solution file is imported into your environment, which brings in the app's screens and its data sources, and the import process needs the connection references for those sources to be resolvable in your own environment. That last point is the practical stumbling block for anyone importing a sample, because a sample built on a connector like SharePoint or SQL Server carries a reference that has to point at something that exists in your tenant rather than in the author's. The sample documentation will tell you which connectors a given sample expects, and that list is the thing to check before you import. It is worth saying plainly what the project documentation does not cover. There is no description of how the samples are tested, no list of the Power Platform environments or connector versions each sample targets, and no compatibility matrix. The repository has a .metadata directory, a .vs directory and a .github directory, and a samples/README-template.md that new samples are expected to follow, but the template is the mechanism by which the gaps get filled, and the fact that there is a template rather than a checker means consistency depends on each author filling it in. ## The governance files are the real difference Beyond the samples themselves, the repository carries the files that a Microsoft-run community project is expected to have, and their presence tells you more about how the project is run than the sample list does. There is a CODE_OF_CONDUCT.md adopting the Microsoft Open Source Code of Conduct, with the FAQ link and a contact address for questions. There is a CONTRIBUTING.md pointing at the guidance in the consolidated repository. There is a LICENSE file with the MIT terms. There is a SECURITY.md and a SUPPORT.md, both of which exist because Microsoft requires a disclosure path and a support route for its repositories, and their separate presence tells you where to report a problem in a sample that involves a connector or a data source. There is also the question routing logic in the documentation, which asks you to use a particular approach for submitting questions and issues so they get noticed and addressed. That instruction is aimed at contributors, and it is the same reason this repository asks for new samples to go elsewhere: a distributed sample collection with hundreds of solutions needs a single intake point, or the review queue becomes the bottleneck. The community infrastructure around the samples is broader than the code. The documentation points at the Power Platform Community, and at weekly community calls covering the latest Copilot, Microsoft 365 and Power Platform topics, with a schedule and recurring invites available. The repository also embeds a visitor statistics badge, which is a small detail but a telling one: it tells you this repository is visited constantly, which is exactly why the maintainers are consolidating rather than leaving it fragmented. ## Where a sample collection is the wrong answer The first limitation is that a sample is not a starting point you can build on without work. When you import a solution, the code comes with the author's naming, the author's data model and the author's connector references, and you inherit decisions that were made for a demonstration rather than for your organisation. Samples demonstrate a usage pattern, and the pattern is the transferable part. The rest is scaffolding you will replace. Teams that expect a sample to be a foundation usually find it is a reference, and that gap is where the hours go. The second is that samples go stale. Power Apps is a platform that Microsoft updates on its own schedule, and a sample written against a connector behaviour or a formula pattern from two years ago can stop working or stop being the recommended way. There is no compatibility statement in this repository to tell you which samples are current, and the absence of releases means there is no version history to diff. When you pick a sample, check when it was contributed, and treat it as a technique to learn rather than code to ship. The third is the platform itself. Power Apps sits inside a Microsoft 365 and Power Platform tenant with licensing, environment and governance attached, so it is a serious answer when the whole organisation is on Microsoft and a poor one otherwise. The realistic alternative for a maker who wants the same patterns without the platform commitment is to build the equivalent in whatever low code or full stack stack you already run. The difference in approach is that a sample gives you a working artefact you can import and inspect in minutes, while a from scratch build gives you something that fits your environment, at the cost of writing it yourself. If you are on Power Platform, the sample is faster. If you are not, the sample is a document with extra steps. ## Conclusion Adopt the Power Platform Samples repository rather than this one if you are looking for a Power Apps example today, because the maintainers state that new samples go to the consolidated repository and that this one is being migrated. Do not treat this repository as a library or a framework, since each entry is a self contained solution illustrating a pattern rather than a component you install. Before you pick an example, read the how to use the samples wiki article for the import steps, check the sample's own documentation for the connection it needs, and expect to adjust the connection references when you import into your own environment. ## FAQ ### What is the Power Apps Samples repository? It is a curated collection of community contributed Power Apps samples that demonstrate different usage patterns for Power Apps, with each sample contained in its own solution. Contributions come from the feature teams, the PnP team and the wider community. ### Where should I submit a new Power Apps sample? The maintainers are moving all samples from product specific repositories into a single Power Platform Samples repository, and they ask that pull requests for new samples be created there. Fixes and improvements to the existing samples in this repository are still welcome here. ### How do I import a sample from Power Apps Samples? The project documentation directs you to a wiki article on how to use Power Apps samples for the steps. Each sample lives in its own solution, so you import the solution into your environment and then point its connection references at connectors that exist in your own tenant. ### What kinds of samples are in the collection? The samples directory holds end to end apps such as InvoiceProcessing, Timesheet and SearchMovies, reusable interface components such as the clock time picker, the cascading dropdown, the calendar component and the Microsoft Graph Toolkit people picker, and reference material for specific features such as the SVG examples and the accessibility color contrast checker. ### Is Power Apps Samples maintained and under what licence? The repository is not archived and the last push was on 2026-09-28, though there are no GitHub releases. It is MIT licensed, adopts the Microsoft Open Source Code of Conduct, and carries SECURITY.md and SUPPORT.md for disclosure and support routing. ## Sources - [Issues](https://github.com/pnp/powerapps-samples/issues) - [License: MIT](https://github.com/pnp/powerapps-samples/blob/main/LICENSE) - [pnp/powerapps-samples on GitHub](https://github.com/pnp/powerapps-samples) - [Project website](https://aka.ms/powerplatform-samples) - [README](https://github.com/pnp/powerapps-samples/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pnp-powerapps-samples