# microsoft/PowerBI-Developer-Samples: Power BI Embedded Examples Across Multiple Stacks > This repository offers Power BI Embedded and REST API examples across .NET, Python, Java, Node.js, React TypeScript, and PowerShell. It is a reference collection rather than a unified application, so adoption depends on finding a sample that matches your hosting model and implementation stack. **microsoft/PowerBI-Developer-Samples** — A collection of Power BI samples for developer use. - Repository: https://github.com/microsoft/PowerBI-Developer-Samples - Stars: 1,966 · Forks: 1,550 - Language: JavaScript - License: MIT - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/microsoft-powerbi-developer-samples ## PowerBI-Developer-Samples Targets Two Embedded Ownership Models The repository addresses developers who need examples for embedding Power BI content in applications built with different frameworks. Its main distinction is between two ownership models. "Embed for your customers," also called App Owns Data, appears for .NET Framework, .NET Core, Python, Java, and Node.js. "Embed for your organization," also called User Owns Data, appears for .NET Framework, .NET Core, and React TypeScript. This split matters because the repository is not merely a collection of visual demonstrations. The listed frameworks reflect distinct deployment decisions, such as whether an application uses one application-owned Power BI context or individual user access. The README identifies the supported framework combinations, but it does not document the authorization sequence or configuration for each sample at repository level. The intended users are therefore developers looking for a reference implementation tied to a particular Power BI embedding approach. It may help someone select a familiar stack, compare examples across languages, or locate a folder with a related integration concern. It does not replace the linked Power BI Developer documentation, which remains the appropriate place to verify the current service requirements and authorization model. ## Repository Structure Spans Seven Application Areas Based on the top-level repository layout, the samples are separated into `.NET Core/`, `.NET Framework/`, `Java/`, `NodeJS/`, `PowerShell Scripts/`, `Python/`, and `React-TS/` directories. This organization lets developers inspect an example in the same area as a framework they already use. It also means the repository should not be treated as a single library with one package entry point. The README states that embedding solutions cover five frameworks, while its ownership-model list names seven framework and language combinations in total. The repository metadata also lists C#, JavaScript, Python, Java, TypeScript, and PowerShell, with React and Flask appearing in the sample metadata. The root README does not identify a single runtime that executes every example. There is also a separate PowerShell area for calling Power BI REST APIs. That makes it more than an Embedded sample set, although the root documentation gives no REST operation examples or setup sequence. Developers should therefore locate the framework directory and then read its sample-specific README rather than assuming that files at the repository root form one coordinated application. ## Credential Encryption and Data Source Update Samples Address Operational Tasks Beyond content embedding, the repository includes solutions for two operational needs: encrypting credentials and updating data sources. The README lists .NET Core, Python, and Node.js for those concerns. Their inclusion indicates that the samples address more than rendering an embedded report, although the root document does not explain the encryption scheme, key handling, supported update operations, or expected permissions. These examples are most relevant when an application needs to manage sensitive connection information or trigger source changes as part of its integration workflow. Developers should not assume that a credential sample establishes a complete secrets-management design. The repository summary does not say where encryption keys are stored, whether secrets enter through environment variables, Azure Key Vault, or another service, or what happens when a key is unavailable. The limitation is concrete: framework coverage is listed, but the root README does not let a reader compare the implementations or assess their security properties. Anyone using those directories should inspect the sample-specific README and implementation files, then check the current Power BI developer documentation for supported credential and data-source operations. ## First Use Starts With a Sample Folder, Not a Root Install The root README does not provide installation commands, a package installation step, a single configuration file, or a startup command for the repository. It directs readers to README.md files in the respective folders. A first useful step is therefore to select the directory matching both the application stack and the intended ownership model. For App Owns Data, the available directories named by the README are `.NET Framework/`, `.NET Core/`, `Java/`, `NodeJS/`, and `Python/`. For User Owns Data, they are `.NET Framework/`, `.NET Core/`, and `React-TS/`. If the need involves REST API calls, start with `PowerShell Scripts/`; if it involves credential encryption or updating data sources, inspect the corresponding implementation under one of `.NET Core/`, `Python/`, or `NodeJS/`. No code block is included here because the repository-level documentation gives no verified command to run. The expected first result is a sample-specific README containing the applicable setup details. If that file does not provide a complete setup path, the README does not identify another installer or bootstrap script. On Windows, the root README adds a specific operational check: before running a sample, ensure that the full path to it does not exceed 260 characters. The README links this restriction to the Windows maximum file path limitation, so long workspace or checkout paths can prevent a sample from working even when its framework requirements are satisfied. ## PowerShell REST Samples Are Separate from Embedded Applications The `PowerShell Scripts/` area extends the repository beyond interactive Embedded applications. According to the root README, these scripts call the Power BI REST APIs. This makes the directory potentially relevant to command-line automation, API exploration, or administrative tasks that do not involve an application UI. The distinction is useful when choosing where to begin. A developer building an embedded React application has different files and configuration concerns from someone working with REST requests in PowerShell. The repository does not claim that these scripts are the API layer used by every embedded sample, and the root README does not describe how they connect to the other projects. The root documentation does not specify a service principal, tenant, credential, endpoint, or request payload. There are also no GitHub releases that could serve as versioned bundles for consumers. Readers should consult the scripts and their local documentation for exact inputs rather than infer API access from the repository's subject. ## MIT Licensing and Recent Repository Activity Leave Versioning Questions Open The repository identifies the MIT license. That permits use and modification under the license's terms, but this review does not provide legal advice. Developers still need to preserve the required license notice and inspect the repository's `LICENSE` file when distributing code or copying substantial portions into another product. The last push was on 2026-10-04, which is recent enough to avoid labeling the repository inactive or abandoned. However, the repository has no GitHub releases. There is therefore no release-tag history documented here to establish a stable versioning scheme, upgrade path, or compatibility promise between sample revisions. The default branch is `master`, and the README's build badge references a branch named `master`. The support section directs bug reports and technical assistance to the Fabric Developer Community Forum, feature requests to the Fabric Ideas Portal, and account-specific support to the Fabric Support Team or an account manager. Those routes help with questions, but they do not replace sample release notes. Based on the repository layout, maintenance work also spans several frameworks, so an update to one sample cannot be assumed to update or validate all others. ## Conclusion Developers evaluating Power BI Embedded should adopt this repository as a source of implementation examples when their required hosting model and language have a corresponding folder. It is a poor fit for teams seeking one installable package, uniform lifecycle management, or documented release cadence. Verify the selected sample's README, credentials requirements, tenant configuration, and Windows path constraints before copying its structure into an application. ## FAQ ### Which Power BI Embedded ownership models does microsoft/PowerBI-Developer-Samples cover? The README lists App Owns Data for .NET Framework, .NET Core, Python, Java, and Node.js. It lists User Owns Data for .NET Framework, .NET Core, and React TypeScript. ### How do I install microsoft/PowerBI-Developer-Samples? The root README does not provide a repository-wide installation command. It directs developers to the README.md files inside the relevant sample folders. ### Does microsoft/PowerBI-Developer-Samples include PowerShell REST API examples? Yes. The repository includes a `PowerShell Scripts/` directory, and the README states that it contains samples for calling the Power BI REST APIs. ## Sources - [Issues](https://github.com/microsoft/PowerBI-Developer-Samples/issues) - [License: MIT](https://github.com/microsoft/PowerBI-Developer-Samples/blob/master/LICENSE) - [microsoft/PowerBI-Developer-Samples on GitHub](https://github.com/microsoft/PowerBI-Developer-Samples) - [README](https://github.com/microsoft/PowerBI-Developer-Samples/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/microsoft-powerbi-developer-samples