Power Apps

    Power Apps for forms and business applications.

    The service technician opens today's jobs on a tablet, even in a basement with no signal, and the back office sees the new status. We pick app type and data store.

    For field and back-office teams who want to capture jobs, building data or reservations in an app of their own.

    • Canvas apps
    • Model-driven apps
    • Code apps
    • Dataverse
    • Copilot Studio
    • Microsoft Teams
    A farm shop in Gruyères looking up at the castle, cheese, bread and a laptop with a Power App on the table, the robot agent beside it holding a tablet
    01

    Canvas, model-driven or code app

    A canvas app fits freely designed interfaces such as capture on a tablet, offline as well. A model-driven app fits data with many relationships and roles on Dataverse; forms, views and the chat with Microsoft Copilot are derived there from the data model. Code apps bring an interface built with React or Vue under Power Platform governance, with connectors and data policies. For external users we build in Power Pages.

    02

    Screens, roles, status

    We define screens, required fields, roles and status changes, and choose SharePoint, Dataverse or an interface to the business system according to data relationships and access needs. Where an agent or an AI feature can take over a step, we plan it in from the start. The building blocks:

    • Capture on the moveCanvas apps for phone and tablet with photos, location and offline mode, embedded in Teams if you like.Result: data arrives complete and validated, even where there is no signal on site.
    • Case work in the officeModel-driven apps on Dataverse with views, business rules and process steps.Result: the back office works with the same records as the team outside.
    • Code appsThe interface is built in React or Vue, by your developers or by us with coding agents, and runs with Entra sign-in, connectors and the platform's data policies.Result: a tailored interface that your IT manages like any other app.
    • Agents and AI in the appPrompts check input or read receipts, an agent from Copilot Studio answers questions from the same tables.Result: routine cases are prepared when a person opens them.
    • Solutions and environmentsDevelopment, test and production kept apart, changes through a pipeline, owners and business responsibility named.Result: every change to the app has a fixed route into operation.
    03

    Licences, environment, activation

    Apps on SharePoint lists with standard connectors run with Microsoft 365. As soon as Dataverse, premium connectors or a code app are involved, every user needs Power Apps Premium or an equivalent licence; in managed environments this applies to every app. Your admins activate code apps per environment. Bring real examples and exceptions, and name the person who will own the app in the business.

    04

    One transaction, played through

    People work through typical transactions from submission to closure. We test invalid input, role changes, concurrent work, working without a connection and data-source errors. A documented deployment and a person responsible for the app are part of the rollout.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: October 2026

    • As of 23 September 2026

      Code apps run with the platform's sign-in and policies.

      Code apps have been generally available since February 2026. They are built in a development environment such as Visual Studio Code, sign in through Entra ID and follow sharing limits, Conditional Access and data policies. Admins activate them per environment; users need Power Apps Premium, an app pass or pay-as-you-go.

      Source: Microsoft Learn: Power Apps code apps
    • From February 2027

      In managed environments, an app opens only with a licence.

      Since June 2026, people without a suitable licence see a notice in the app; from February 2027 it no longer opens. This also applies to apps with standard connectors. Beforehand, we reconcile the licence report in the Power Platform admin centre with your users.

      Source: Microsoft Learn: Licensing requirements for managed environments
    • Since April 2026

      Model-driven apps show only the modern look.

      The classic look can no longer be switched on; logic, data and permissions are unchanged. For chat in the app, Microsoft Copilot takes over from the earlier Copilot chat, which has been phased out since January 2026 in environments without Dynamics 365 apps.

      Source: Microsoft Learn: Important changes coming in Power Platform

    Before the first app goes live.

    Does everyone need a Power Apps licence?

    For apps on SharePoint lists with standard connectors, the Microsoft 365 licence is enough. As soon as Dataverse, premium connectors or a code app are added, every user needs Power Apps Premium, an app pass or pay-as-you-go. In managed environments this applies to every app from February 2027. We record what your workflow needs before we build.

    Can people work without a connection?

    Yes, canvas apps on Dataverse work offline. The data sits on the device, and changes sync as soon as there is a connection again. We set which tables and records go onto the device in the offline profile, and we test the sync with conflicts.

    Can our developers work with their own code?

    Yes, with code apps in React, Vue or another framework, built in Visual Studio Code. Sign-in, connectors and data policies come from the platform. Some features are still missing, such as Power Platform Git integration, use as a SharePoint form and running in Power Apps for Windows; we check this before choosing the app type.

    What changes for AI features such as AI Builder?

    From 1 November 2026, new and renewed licences no longer include AI Builder credits; credits already purchased continue until the end of the contract term. AI features in apps then consume Copilot Credits. We check which of your apps read receipts or use prompts and plan consumption per environment.

    How does a change get from test to production?

    Through a solution that a pipeline moves from the development environment to test and then to production. The pipeline's target is a managed environment. This records who deployed what and when, and a change can first be checked with test users.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.