Apps your teams build,
ready to rely on
We build and look after apps, flows and sites on Microsoft Power Platform, with environments for each stage, data policies and a tested path to production, so the apps your teams rely on keep running.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When a useful app belongs to one person
In many companies, people across the business build their own apps and flows on Microsoft Power Platform, and some become part of how a team works. An app is a screen for one task, such as booking equipment, and a flow runs a set of steps on its own, such as sending each new request to the right person. Microsoft calls the people who build them makers.
Many were built in the default environment, the one every licensed person in the company can build in, which Microsoft intends for personal work rather than for what a business depends on. An environment holds its own apps, flows, data and settings, and a flow signs in to each service it uses with a connection, often its maker’s own.
So when a maker changes roles or leaves, a flow can stop, and it can be hard to say which apps reach which data, or who looks after them. And some apps live in Microsoft Dataverse for Teams or in free developer environments, which Microsoft is retiring.
What we build
Apps, flows and sites on Microsoft Power Platform, each in the environment its work needs, with code where low-code stops, moved to production in tested solutions, so what your business relies on is owned by a team.
Apps for the work your teams do
Canvas apps in Microsoft Power Apps, each screen laid out for its task, and model-driven apps, which Power Apps builds from your data in Microsoft Dataverse, the platform’s own data store. A canvas app can also work on data you already keep elsewhere.
Flows that keep work moving
Cloud flows in Microsoft Power Automate that run their steps when something happens, on a schedule or at the press of a button, and desktop flows, which work a system’s screens as a person would, only where it offers no other way in.
Code where low-code stops
Power Fx, the platform’s formula language, where it fits. Where it doesn’t: custom connectors to your own APIs, code components for screens a standard control can’t draw, and plug-ins, .NET code that Dataverse runs as records change, each tested before it reaches production.
Environments for each stage
The default environment kept for personal work, a developer environment for each maker, and test and production environments for what the business relies on. Managed Environments, Microsoft’s governance features, add sharing limits and usage insights, and environment routing can start each new maker in their own developer environment.
Data policies that keep data where it belongs
A data policy for each environment, setting which connectors, the links to each service, its apps and flows may use, and which may be used together: strict where anyone can build, wider where a team’s work needs more.
A path to production
Apps and flows packaged in solutions, which carry work from one environment to the next, with connection references and environment variables, so each environment supplies its own connections and settings. Pipelines move them to test and production, as Microsoft’s guidance on application lifecycle management sets out, owned by a team or a service principal, an identity for software rather than a person.
Sites for customers and partners
Sites in Microsoft Power Pages where customers or partners sign in to send a request, follow it or update their details, with table permissions on every form and list, and each site’s Web API limited to the columns it needs, as Microsoft now requires.
Moves out of retiring environments
Each Dataverse for Teams environment listed, then upgraded to Dataverse or moved into one you already run, and the work in unmanaged developer environments moved into managed ones, in planned steps, before Microsoft’s dates.
Agents where they help
Agents in Microsoft Copilot Studio that answer from your knowledge and act through your connectors, with access scoped to the task and a person approving what matters. Microsoft’s MCP server for Dataverse, generally available, lets other AI assistants work with your data within the security roles of the person using them.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Sales, service and finance apps:CRM and ERP development, for Microsoft Dynamics 365 apps
- Intranets and files on the same tenant:Intranet development, for Microsoft SharePoint sites
- Developers in your own team:Hire developers for Power Platform apps
Rules for where data can go
Every app and flow reaches data through connectors, one for each service it uses, and signs in to each with a connection. A data policy sorts those connectors into three groups: Business, Non-business and Blocked.
An app or a flow can use business connectors or non-business ones, never both, and can’t use a blocked one at all. Some connectors, such as Dataverse’s, can’t be blocked, only sorted, and a new one lands in Non-business unless an admin chooses otherwise.
A policy applies to one environment, to several or to all of them, so each can have the rules its work needs: strict where anyone can build, wider where a team’s work needs more. Where several apply to one environment, the strictest result applies, so we keep them few.
Microsoft is rolling out advanced connector policies, which list the connectors an environment allows instead of sorting them, and can run alongside data policies like these. We plan both around the environments you have.
One flow
- New orderUses Team files, in {{ plTfTag }}
- Save to customer recordsUses Customer records, in {{ plCrTag }}
- Send to an outside serviceUses Outside service, in {{ plOsTag }}
{{ plVerdict }}
Data policy
Customer records
Team files
Outside service
A flow can use business connectors or non-business ones, never both.
{{ plStatus }}
Two kinds of environment are retiring
Microsoft is retiring Dataverse for Teams environments, the ones created from inside Microsoft Teams. No new ones can be created from November 15, 2026. Those not upgraded to Dataverse are suspended on September 15, 2027 and decommissioned on October 30, 2027. Apps, flows and agents built on Dataverse can still be used in Teams.
Microsoft says Dataverse for Teams offers a subset of Dataverse, without direct API access, custom connectors, desktop flows or AI Builder. An upgrade keeps an environment’s apps, flows, agents and data, and needs enough Dataverse capacity in your tenant, your company’s own space in Microsoft’s cloud, and licenses for the people who use it.
It’s retiring unmanaged developer environments too, including those the free Power Apps Developer Plan creates. No new ones can be created from November 15, 2026; existing ones are suspended from December 15, 2026 and deleted from January 15, 2027. Developer environments that are Managed Environments carry on, and each person can now create one.
Microsoft announces changes like these on its Learn site, and new Dataverse capabilities on its AI at Work roadmap, so we plan from its dates. Each environment is listed first. Then its apps, flows and data are upgraded, moved into a managed environment, or retired on purpose, before its date.
Start with a review of your tenant
The review covers your environments: which type each is, which are Managed Environments, and how environment routing is set; the apps and flows in your default environment, who made them and which the business relies on; whose connections each flow runs on, and which makers have moved on; your data policies, and the connectors each environment allows; your solutions, and how changes reach production; your Power Pages sites, their table permissions and Web API settings; which features need which licenses, as Microsoft’s licensing guide sets them out; and your Dataverse for Teams and developer environments, with Microsoft’s dates for each.
The first step is one app or flow the business relies on, moved into a solution, owned by a team and released through a pipeline, as Microsoft’s guidance sets out, so the path is proven before anything else takes it.
You get a written review and a proposal for the first step.
Questions worth asking
Our teams already build their own apps. Do we have to stop them?
Usually not. Microsoft’s governance guidance is to give makers the right places to build rather than to stop them: the default environment for personal work, a developer environment for each maker, and a data policy for each environment. The apps and flows the business comes to rely on then move to test and production in solutions, owned by a team. What fits depends on your company, and the review shows where to start.
What happens to a flow when the person who built it leaves?
A flow that runs on its maker’s own connections can stop when their account is turned off, and until someone takes it over, it has no owner who can change it. For flows the business depends on, Microsoft recommends ownership by a service principal, an identity for software rather than a person, with connection references, so each environment supplies the connections. A team can own the rest.
We have apps in Dataverse for Teams. What should we do?
List them first, then decide for each. Microsoft stops new Dataverse for Teams environments from November 15, 2026, suspends those not upgraded on September 15, 2027, and decommissions them on October 30, 2027. An admin can upgrade an environment to Dataverse, which keeps its apps, flows, agents and data, if your tenant has the capacity and its users have the licenses Microsoft sets out. Or an app can be moved into an environment you already run, or retired on purpose. Apps on Dataverse can still be used in Teams.
Our developers use the free Developer Plan. Does that change?
Yes. Microsoft is retiring unmanaged developer environments, including those the Power Apps Developer Plan creates: no new ones from November 15, 2026, existing ones suspended from December 15, 2026 and deleted from January 15, 2027. Developer environments that are Managed Environments carry on, one for each person, and running apps and flows in one needs a premium license, as Microsoft sets out. So each developer’s work moves into one of those, or into a sandbox, before its date.
When is low-code the right choice, and when is custom software?
It depends on the work. Low-code is often the right answer where the platform’s apps, flows and connectors cover what the work needs and your people already work in Microsoft’s tools, and we’ll tell you when it is. Custom software makes sense where the work needs a product of its own, such as an app your customers pay for, or more than the platform was built to do. Many companies run both, linked to each other.
Custom SoftwareCan our apps use the data and systems we already have?
Yes, in most cases. Connectors reach many services as they are, custom connectors reach your own APIs, and virtual tables show data from another system in Dataverse without copying it, as Microsoft’s documentation describes. Each connection is tried in a test environment before it reaches production.
Systems & API IntegrationCan agents work with our apps and data?
Yes, within each person’s access. Agents built in Microsoft Copilot Studio can answer from your knowledge and act through your connectors, by default with the signed-in person’s own credentials, so an agent reaches only what that person can, and a person approves what matters. Other AI assistants can reach Dataverse through Microsoft’s MCP server, which respects each person’s security roles. An admin allows each one, and some uses can be charged, depending on your licenses.
Do we need more Microsoft licenses for this?
Sometimes. An app or a flow that uses a premium connector, a custom connector or Dataverse needs premium licensing for the people who use it, and Managed Environments come with Microsoft’s standalone licenses, as its licensing guide sets out. We check what yours already cover, and say what any part of the plan would need before anything is bought.
Can you build a site for our customers or partners?
Yes, in Microsoft Power Pages, where customers or partners sign in to send a request, follow its progress or update their details. We set table permissions on every form and list, which Microsoft now enforces on new sites, and each site’s Web API names only the columns it allows. Where the site is the product, or needs a design of its own, we build it as a web app instead, reviewed, tested and documented like every release.
Web & App DevelopmentCan you look after apps and flows someone else built?
Yes. The review shows what each app and flow does, whose connections it runs on and which environment it’s in. Then ownership moves from one person to a team or a service principal, and each connection to accounts you choose, with your makers’ help where they’re still with you.
How do you keep our data secure?
Each environment gets a data policy for the connectors its work needs, and the ones your business relies on are Managed Environments, with limits on how widely an app can be shared. Flows that matter are owned by a team or a service principal rather than one person, sign-in stays with Microsoft Entra ID, the one your organization already uses, and each Power Pages site has table permissions on every form and list. Code we add is reviewed before release, so problems are found early.
Application SecurityWhat does it cost?
It depends on the work: the apps, flows and sites involved, the environments they need, and whether they’re new, moved or taken over. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.
PricingCan we hire Power Platform developers for our own team?
Yes. Describe the apps, flows or sites the work involves, and within 48 hours we’ll introduce Power Platform developers matched to it, working in your time zone. You meet each one and choose who joins your team.
Hire developers for Power Platform apps
Microsoft, Dataverse, Dynamics 365, Microsoft Entra, Power Apps, Power Automate, Power Pages and Power Platform are trademarks of the Microsoft group of companies, and the other Microsoft product names on this page, such as AI Builder, Copilot Studio, Power Fx and Teams, may be too. Webair is independent of Microsoft, and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us which apps and flows your teams rely on, and where each one runs today. A short call is enough to see where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}