Pro User
explore our new search
Understanding Default Power Platform Environment & SharePoint Integration
Image Source: /new_publishers(a693199c-4179-ec11-8d21-6045bd8e0e82)
Power Apps
Oct 20, 2022 8:52 AM

Understanding Default Power Platform Environment & SharePoint Integration

by HubSite 365 about Alex Shlega [MVP]

Microsoft Power Platform Consultant/Solution Architect, Business Applications MVP

Citizen DeveloperSharePoint OnlinePower Apps

Become a pro in managing the Default Power Platform environment & SharePoint form apps with Microsoft expert insights.

A Look into Power Platform's Default Environment and SharePoint

The expansive diversity of the Power Platform is undeniably incredible. However, from a perspective of focusing heavily on Dataverse-backed apps and flows, the default environment may seem inadequate. Its lacks are, however, not entirely negative. This environment allows every citizen developer to create apps without the need for a dedicated project environment, a trial, or an individual dev subscription, making it the only platform that offers such capability.

The Default Environment was designed as a free-for-all sandbox. Considering the size of some organizations, several hands would be found in this sandbox, thus its potential to become chaotic is almost certain. Microsoft, aware of the pitfalls, suggested to consider the Default environment as a personal productivity environment. However, the boundaries of what this suggests remain somewhat unclear.

A decision-making process table is provided, courtesy of Microsoft, to aid in the understanding of whether to keep an app in the default environment or not. This decision mainly falls on administration rather than the citizen developer.

SharePoint form apps are a type of production application that may end up in the Default environment without intention. By default, this environment is used for that. If you are more acquainted with the Dataverse side, you might be wondering what SharePoint form apps are, here is an explanation along with an example. The default SharePoint form for a SharePoint list, could be exchanged for a Default environment Power Apps.

To see how this has been set up in your tenant, the "Get-AdminPowerAppSharepointFormEnvironment" cmdlet can be used. In this example, all SharePoint form apps are sent to the "default". If you want to check which form applications are stored, the "Get-AdminPowerApp" cmdlet can be used.

The "Default" environment used to be the only destination for these apps but this isn't the case anymore. The "Set-AdminPowerAppSharepointFormEnvironment" cmdlet can be used to specify which environment should be used for SharePoint form ps. Sadly, existing SharePoint form apps won’t move to the new environment, they remain in the original (likely in the Default) environment. Instead, new forms will be created in the dedicated environment moving forward.

But there are a few great points to consider. We can specify the environment that will be used for SharePoint form applications, and the sooner we do it the better. There is the risk, however, that if a SharePoint form application is in the Default environment already, it will remain there, and we cannot do the same for the Flows created from SharePoint – they stay in the Default environment no matter what.

Interestingly, you may end up having Power Apps created in different environments for the same SharePoint setting. This administrative disparity of integration components may increase administrative efforts. It seems like there is a balance to be struck between a dedicated environment for SharePoint “integration” to enhance Default environment administration versus the potential for increased administrative effort. The choice will mostly depend on the specific needs and workflow of your organization's development.

Further General Insights

Power Apps platform is a cutting-edge business solution for businesses seeking to enhance their efficiency and productivity. It provides a default environment that allows for the easy creation and management of applications. Whether it's SharePoint or Dataverse-backed apps, Power Apps has distinguished itself as a leading tool for innovative business operations.

Read the full article Default Power Platform environment and Sharepoint

Power Apps - Understanding Default Power Platform Environment & SharePoint Integration

Learn about Default Power Platform environment and Sharepoint

Understanding the intricate functionalities and uses of Microsoft's Power Platform and SharePoint can be daunting. These two Microsoft software, along with SharePoint forms (or applications), are integral in offering seamless web-based collaboration platforms that provide secured real-time data access and interactive user interfaces. But before diving deeper, it's worth noting the significance of the default environment in the Power Platform, the restrictions and advantages attached to it, and how it works with SharePoint.

The default environment acts as a personal sandbox for 'an average developer' to create applications and flows without having to request a specific project environment or create a trial. It’s a playground for everyone and can become somewhat chaotic, depending on the organization's size. Although it's considered mostly unbeneficial from a Dataverse-centered view, Microsoft points out that it’s ideal for personal productivity. However, you can think of it as a personal productivity environment.

As Microsoft suggests, one has to contemplate whether an application should stay in the default environment or not. And naturally, not every average developer might be conscious of such considerations. Most of the decision-making responsibility would then land on the administrators. In some cases, the criteria might also vary according to the organization itself.

An example of a production application ending up in the default environment is SharePoint form applications. They find their place here automatically, without any intentional effort. For instance, you can create a new form as a Power Apps application on your SharePoint list, which then finds its place in the default environment.

You can verify the configuration in your tenant with the Get-AdminPowerApp SharePoint Form Environment cmdlet. You may also discover which form applications are stored there using the Get-AdminPower App cmdlet. However, it is crucial to remember that any existing SharePoint form applications will not migrate to a new environment. They will remain in their original environment, usually the default, even though new forms will get created in the dedicated environment henceforth.

Moving on, it is possible to store Power Apps form applications in different environments for the same SharePoint environment. Some of them might be in the default environment while the others in a new dedicated one. With this at our disposal, it's possible to specify the environment for SharePoint form applications and the sooner we do it, the better. However, if a SharePoint form application already exists in the default environment, it will remain there. And unfortunately, there is no provision to do the same for the Flows created from SharePoint.

Last but not least, having a dedicated environment for SharePoint integration can result in comfortable default environment administration. However, if we can only implement this practice for specific components, it might increase administrative efforts instead

In conclusion, it may seem tricky to comprehend the nitty-gritty of Microsoft's SharePoint and Power Platform, but with practical learning and a hands-on approach, one can master these tools to streamline organization tasks and increase productivity. Therefore, it is essential to expand your knowledge and understanding of these platforms. You can take advantage of the various training courses available online, like those on the Microsoft Learn platform, for a step-by-step learning process to cater to your organization's particular needs.

Tips for better understanding:

  • Always try to get hands-on experience
  • Understand by creating an app or flow in the default environment
  • Experiment by moving components between environments
  • Look into Microsoft’s recommendations and guidelines for managing the default environment

By the end of these tips and a structured learning process, expect to possess a deeper understanding of SharePoint, Power Platform, and how the default environment fits into the big picture.

More links on about Default Power Platform environment and Sharepoint

Manage the default environment - Power Platform
Jul 12, 2023 — Like every other environment type (sandbox, production, developer), the default environment is archived automatically. However, you can request ...
Environments overview - Power Platform
Jan 30, 2023 — A single default environment is automatically created by Power Apps for each tenant and shared by all users in that tenant. Whenever a new user ...
Secure the default environment - Power Platform
Apr 17, 2023 — The default environment is created with the name TenantName (default). You can change the environment name to something more descriptive, like ...


Default Power Platform, Power Platform environment, Sharepoint, Sharepoint Integration, Microsoft Power Platform, Default Environment Settings, Power Platform Default, Sharepoint and Power Platform, Power Platform Configuration, Sharepoint Environment Settings.