DOCSEARCHbyAlgolia
Submit Docs

Power Platform Documentation

repository·main·Indexed 19 days ago

https://github.com/microsoftdocs/power-platform

Documentation for Power Platform, including the management of Power Fx formula references and detailed guidance on Microsoft Dataverse for Teams. Covers environment lifecycle operations, licensing, user roles, capacity enforcement, and the process for upgrading Dataverse for Teams environments to production.

Tokens
347.3K
Snippets
636
Records
1.6K
Agent score
67%

What's inside Power Platform

  1. Overview of Dataverse Git integration

    main

    Dataverse Git integration allows development teams to sync solutions and solution objects across one or more Microsoft Dataverse environments using an Azure DevOps Git repository. This native integration is designed for developer environments to enable version control, change tracking, and team collaboration.

    Important Usage Note: Git integration is intended for use in developer environments. For test or production environments, you should use builds to create solution artifacts and Power Platform pipelines for deployment rather than direct Git syncing.

  2. What is the Business value toolkit?

    main

    The Business value toolkit is a collection of sample apps and processes designed to help organizations measure, analyze, and communicate the benefits of Power Platform solutions. It provides a framework to transform raw insights into compelling success stories, ensuring return on investment (ROI) is tracked and visible.

    Key components include:

    • A structured storytelling framework: A five-stage process to capture the journey of an app.
    • Strategic alignment analysis: An analytical process that evaluates stories against organizational strategic objectives.
    • Value calculator: A tool to quantify impact using metrics like the average cost of things.
    • Value cards: Concise visual representations of collected data used for communication.
    • Proposal assessment: A proactive capability to evaluate new ideas before development.

  3. Overview of Power Platform pipelines

    main

    Power Platform pipelines provide automated Application Lifecycle Management (ALM) and CI/CD capabilities. They are designed to serve three distinct user roles:

    • Admins: Centrally manage and govern pipelines, set up safeguards for solution development, and scale ALM processes. Admins can use delegated deployments with approvals, view analytics via Power BI, and extend pipelines using Power Automate.
    • Makers: Use preconfigured, in-product deployment experiences within their development environments. Pipelines prevalidate solutions against target environments to detect missing dependencies and validate connections/environment variables before deployment begins.
    • Developers: Use the Power Platform CLI to orchestrate deployments and can extend the pipeline logic to integrate with other CI/CD tools.

    Pipelines reduce the manual effort of exporting/importing solutions, managing connection settings, and handling environment-specific configurations.

  4. Overview of Data Subject Rights (DSR) actions in Power Apps

    main

    When responding to Data Subject Rights (DSR) requests for Power Apps customer data, administrators can perform several key actions to ensure privacy compliance:

    • Discover: Use search and discovery tools to find customer data that may be the subject of a request.
    • Access: Retrieve personal data residing in the Microsoft cloud and make a copy available to the data subject.
    • Rectify: Edit, redact, or remove personal data where applicable.
    • Restrict: Limit the processing of personal data by removing licenses or turning off services, or by moving data from the Microsoft cloud to on-premises/other locations.
    • Delete: Permanently remove personal data from the Microsoft cloud.
    • Export: Provide an electronic copy of personal data in a machine-readable format to the data subject.

  5. Overview of Power Platform Tools for Visual Studio

    main

    Power Platform Tools for Visual Studio is a development extension used for the rapid creation, debugging, and deployment of plug-ins. It also supports developing custom workflow activities, web resources, and integration technologies such as Azure Service endpoints and webhooks.

    Note: This is a new product independent of the legacy Developer Toolkit for Microsoft Dynamics CRM 2013. It is not compatible with templates or projects from the Developer Toolkit.

  7. Overview of ALM Accelerator for Power Platform

    main

    The ALM Accelerator for Power Platform is a canvas app designed to simplify Application Lifecycle Management (ALM) for both low-code makers and advanced code-first developers. It provides a simplified interface to Azure Pipelines and Git source control, allowing makers to perform source control operations, enable version history, and deploy solutions across environments (Development, Validation, Test, and Production).

    Key Requirements:

    • All Power Platform components (apps, flows, customizations, etc.) must be contained within a solution.
    • Users must understand how to manage solutions in Power Platform.

    Core Workflow:

    1. Makers work in isolated development environments.
    2. Makers use the ALM Accelerator canvas app to import solutions from source control, export changes to source control, and create pull requests.
    3. Azure Pipelines YAML and PowerShell templates automate the staged deployment from development to production.

  8. Overview of the Power Platform Center of Excellence (CoE) Starter Kit

    main

    The Power Platform CoE Starter Kit is a reference implementation designed to help organizations build governance, monitoring, and adoption capabilities using native low-code tools. It provides a technical foundation for a Center of Excellence (CoE) by using Power Apps, Power Automate, Power BI, Dataverse, and Copilot Studio to showcase sophisticated administrative and governance patterns.

    Key Components:

    • Power Apps and Power BI: Analytics reports and interactive apps to view and manage tenant data.
    • Dataverse: A central data model and workflows used to collect resource information across tenant environments.
    • Automation and Tooling: Assets to build the monitoring and automation necessary for CoE operations.
    • Templates: Suggested patterns and practices for implementing CoE efforts.

    Note: The kit represents sample implementations. While the underlying components (Dataverse, admin APIs, connectors) are fully supported, you should customize the kit to meet your organization's specific administrative and governance goals.

  12. Overview of the SAP Procurement template for Power Platform

    main

    The SAP Procurement template is a framework designed to accelerate the integration of SAP ERP data with Microsoft Power Platform. It streamlines complex SAP procurement screens and attributes into simplified Power Apps interfaces and automates procure-to-pay processes using Power Automate flows.

    The template is organized into two layered solutions:

    • SAP Base: Contains foundational components used by the SAP Procurement solution and intended for future SAP solution templates.
    • SAP Procurement: Contains specific components designed to transform procure-to-pay business processes connected to SAP.

    This template is intended to be used as a starting point that can be customized, extended, and integrated with other systems or additional controls.