Deleting Developer Environment on Power Platform - Guide

Power Platform's Developer Environment Update

Recently reported by the credible EY Kalman (better known as "The CRM Ninja"), Microsoft revealed a significant update to its Power Platform development environment strategy. EY Kalman emphasizes the importance of these changes for all users, regardless of whether they are professional or casual developers.

Microsoft's Power Platform connects developers to a full-capability professional gallery, often called a 'sandpit' where users can freely explore and experiment. The platform used to be available as a simple 'Community' plan, which was renamed to the 'Developer' plan that sports increased accessibility.

Microsoft had astonishingly boosted the number of these 'sandbox' environments users could create from only one to three. The expansion of these workspaces was immensely celebrated by the development community and the announcement video by Phil Topness garnered a lot of positive feedback.

Each of these rapidly growing environments reportedly utilized up to 2GB of storage space, which considering the expanding user base, adds up to a substantial amount of data storage. Tackling the issue, Microsoft has incorporated a new policy. If the environments have been created but are not in use, they are slated for deletion.

This might seem disadvantageous to some users who operate their environment occasionally or frequently go off the grid for a span of few months. However, the system is programmed to consider an environment as inactive only if unused for 90 days. Then it is tagged disabled, and appropriate users are alerted for action.

What qualifies as 'Active'? Microsoft defines it along the following lines:

• User activity: Includes operations like launching an app, executing a flow, or interacting with a Power Virtual Agents bot
• Maker activity: Creating, reading, updating, or deleting an app, flow, or custom connector
• Admin activity: Encompasses environment operations such as copy, delete, back up, recover, and reset

Also noteworthy is the classification of automation as active behavior. So, a scheduled flow run would also be indicative of an active developer environment.

This rule applies only to Developer environments and, till now, environments like Production, Sandbox, etc. have no auto-deletion policies enforced. As a failsafe for infrequent users, the trick is to set up automation to keep the environment active and avoid deletion.

While still in the early stage, users anticipate added controls and customizability on the deletion policy to prevent risks and empower user experience. The capacity to set scheduled cleaning routines or audit log retention schedules could be a handy feature not yet available.

To get a more detailed walkthrough and understanding of these changes, you can find it here.

Further thoughts

These electrifying changes from Microsoft help redefine the workspace for developers around the globe. The company's commitment to improving user experience and maximizing productive engagement is evident. Microsoft’s Power Platform is a launchpad for developers, providing them with a free, flexible, and resourceful environment to innovate.

Although the threat of losing their environment due to inactivity may sound alarming to some, it encourages a more conscious usage and contributes to efficient storage management. This approach also illuminates Microsoft's data conservation strategies, leading to optimal resource allocation.

The expectation for a personalized deletion policy does roll out in the minds of many. Developers are hoping for a more customizable platform where they are in control of their environment’s statuses, which Microsoft might soon provide, based on the requests.

Above all, these continual enhancements are solid proof of Microsoft’s direct responsiveness to the needs and wants of its wide user base, constantly iterating to make Power Platform better, more secure, and user-friendly.

Read the full article Power Platform : Developer Environment Deletion!

Learn about Power Platform : Developer Environment Deletion!

Microsoft's Power Platform has been a game changer for many developers, providing an environment to develop, test, and deploy applications. However, what happens when these developer environments go unused for a lengthy period?

The power platform opens up possibilities for developers to have a playground. By signing up for a developer plan, they get a full capability environment for free. This plan, previously known as 'Community' plan, serves as an excellent resource for everyone no matter if they’re a professional or citizen developer.

A few months earlier, Microsoft made waves by allowing users to create not just one, but THREE of these developer ecosystems. This made it even more convenient for experiments and trials. However, a question on storage size is inevitable. With each environment taking up to 1 to 2 GB of space, the total storage for each user can upsurge to 6GB.

Recently, Microsoft made a riveting announcement regarding these ecosystems. If a developer environment is created but not operational, it is bound to be erased! While this may be beneficial from a storage viewpoint, it might also raise concerns particularly for those who space out their activities or take breaks in between.

According to Microsoft, an environment that hasn’t been used for 90 days is considered inactive. Once it becomes inactive, it is disabled and a notification is sent to the administrator or owner. If no action is taken in the next 30 days, the environment is permanently removed.

The definition of 'Activity' by Microsoft includes user, maker, and admin activities. User activities include launching an app, executing a flow, or chatting with a Power Virtual Agents bot. Maker activities consist of creating, reading, updating, or deleting an app, flow, Power Virtual Agents bot, or custom connector. Lastly, Admin activities incorporate operations on the environment such as copy, delete, backup, recover, etc.

Notably, this doesn't end with user interactions. Automated behaviors like scheduled flow runs are also considered 'Activity'. However, this mechanism is only applicable to Developer environments at the moment. No such policies are called out for other environments (Production, Sandbox, etc).

The solution to maintain a semi-active developer ecosystem could lie in automation. Creating an activity, even a simple one, in the environment can keep it active. However, the option to customize deletion policies like audit log retention would bring an added layer of flexibility and control.

To summarize, being vigilant of usage patterns and making the most out of the available resources, could spare the developer from facing the deletion of their precious testing environments. Remember the adage, "use it or lose it"

For more insights and support in your journey with the Developer Tools, consider taking up courses on Microsoft Power Platform fundamentals or advanced classes on Power Apps, Power Automate, or Power Virtual Agents, according to your professional needs and interests.

More links on about Power Platform : Developer Environment Deletion!

Delete an environment in Power Platform admin center

Feb 14, 2022 — Learn how to delete or remove an environment to recover storage space.

Automatic deletion of inactive developer environments

May 24, 2023 — Inactive Power Platform developer environments are automatically deleted to free up resources.

Automatic environment cleanup - Power Platform

Jun 2, 2023 — After 30 days, if no action is taken, the disabled environment is deleted. You have seven days to recover deleted environments. Only developer ...

Keywords

Power Platform Developer, Environment Deletion, PowerApps Development, Microsoft Power Platform, Dynamics 365 Development, Power Platform Environment, Power Automate, Power BI, PowerApps Environment Delete, Dynamics 365 Environment Deletion.