What does this mean? You are using a dev plan on an app that is not in a developer environment. This is not supported, and the app will stop working on 11/30/2023

[Vieen]

Hi,

I've been using power apps for a couple of months now and this is the first time that I have encountered this message.

"You are using a dev plan on an app that is not in a developer environment. This is not supported, and the app will stop working on 11/30/2023"

Do anyone have any idea what this means? I am using Power Apps Canvas App with Microsoft Dataverse as the Database and I publish the apps on teams.

Thanks in advance.

[AndrewR1]

Hi all, 

Hope this helps :

In Power Platform, you have different types of environments:

1. Default Environment: This is where you usually start creating your apps and solutions. It's typically a development and testing environment.

2. Other Environments: You can also create other environments for specific purposes, such as production, staging, or specialized development. Each environment can have its own set of resources like apps, flows, and data.

The message you're seeing indicates that you are using a "developer plan" within an environment that is not designated as a developer environment. A developer plan allows you to use premium features of Power Apps, but it's supposed to be used within environments specifically meant for development and testing.

Here's what the message means in detail:

1. "You are using a dev plan on an app that is not in a developer environment."

   • You are using a Power Apps plan meant for development purposes (developer plan).
   • The app you are working on is not in an environment that's designated as a developer environment.

2. "This is not supported, and the app will stop working on 11/30/2023."

   • Using a developer plan in a non-developer environment is against the intended usage.
   • Microsoft has identified this and is providing you with a notice that the app will stop working on a specific date (11/30/2023) if you don't adjust your setup.

What should you do?

1. Review Your Environment Setup: Check the environment where you've built and deployed your app. Is it meant for development purposes? If not, you might need to consider moving your app to an environment designed for development and testing.

2. Licensing: Ensure that you are using the appropriate licensing for the environments you're working in. Developer plans are best suited for developer environments.

3. Migration or Adjustment: Depending on your situation, you might need to migrate your app to an appropriate developer environment. This could involve exporting your app, creating a new environment, and importing the app into that environment.

4. Contact Microsoft Support: If you're unsure about the steps to take, or if you believe there might be a misunderstanding, it's a good idea to reach out to Microsoft Power Platform support for guidance.

[Roelof]

I got the same message today. And it is a "Powerapps for teams" app using "dataverse for teams" in the "Teams" environment that is created for that team.

[AndrewR1]

Hi if you have access to the admin centre for power apps you can see the type of environment that you have chosen this could be one of the following:

Production	This is intended to be used for permanent work in an organization. It can be created and owned by an administrator or anyone with a Power Apps license, provided there is 1 GB available database capacity. These environments are also created for each existing Dataverse database when it is upgraded to version 9.0 or later. Production environments are what you should use for any environments on which you depend.	Full control.
Default	These are a special type of production environment. Each tenant has a default environment that's created automatically. Its characteristics are discussed in the following section, The default environment	Limited control. All licensed users1 have the environment maker role.
Sandbox	These are non-production environments, which offer features like copy and reset. Sandbox environments are used for development and testing, separate from production. Provisioning sandbox environments can be restricted to admins (because production environment creation can be blocked), but converting from a production to a sandbox environment can't be blocked.	Full control. If used for testing, only user access is needed. Developers require environment maker access to create resources.
Trial	Trial environments are intended to support short-term testing needs and are automatically cleaned up after a short period of time. They expire after 30 days and are limited to one per user. Provisioning trial environments can be restricted to admins.	Full control.
Developer	Developer environments are created by users who have the Developer Plan license. They're special environments intended only for use by the owner. Provisioning developer environments can be restricted to admins. More information: Control environment creation. The developer environment will be available as long as you actively use the Power Apps Developer Plan. More information: Power Apps Developer Plan	Limited control. Security groups can't be assigned to developer environments.
Microsoft Dataverse for Teams	Dataverse for Teams environments are automatically created for the selected team when you create an app in Teams using the app for the first time or install an app from the app catalog. More information: About the Dataverse for Teams environment.	Limited control. Admins have limited settings available for Teams environments. No customizations of security role or assignments are available. Teams members are automatically mapped to their Teams membership type - owners, members, and guests - with a corresponding security role assigned by the system.

If the environment that your application resides in is not a development environment then using the developer plan will not work. You will either need to upgrade your licence or export and import the application across to a developer environment . 

If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.

If you like my response, please give it a Thumbs Up.

Many Thanks
Andrew

[Vieen]

Hi, thank you for this. very understandable. However, I did migrate the app to a production environment and published the app but the pop up is still there. Here is what I did.

Export Solution from the developer environment > Create a Production Environment > Import Solution >Publish all customization > Test the App

Let me know if I did something wrong or do you have any idea what's the problem with this.

Thanks

[lolbeat]

I just started getting the same message today on both of my Dataverse for Teams apps that are running only in Teams. Did anyone find out if MS are making some changes on the licensing? Actually, I have PowerApps licensing (but not 'full dataverse'). I always thought we can use powerApps with 'Dataverse for Teams' and that seems to be the general opinion among the 'experts' (YouTube MVP's etc), but now I'm very concerned our in-house apps will stop working.

[Roelof]

Hi Andrew, the case is about powerapps for teams in which dataverse for teams is used. This should be ok with an e3 or e5 license, but still we get this warning.

[iantesting]

Have also just received this warning this morning. While I do have a Developer environment, this warning only shows up on Powerapps for Teams apps that have been built and deployed in Teams...

[StevenN3i]

Same issue for me. We have an asset booking solution deployed within Microsoft Teams and I am now seeing the message. The app uses Dataverse within Teams so shouldn't require any additional licensing unless those requirements have changed?

[chico]

This is a great situation to encounter after coming back from vacation and another chapter in the confusion of licensing.

I'm not even sure how we got here but my initial thoughts seem to lead to Dataverse.

We have an app that was first created in Default Env, later exported to a production Env, and has been in solid use for over a year now. None of the users or creators/owners of the app have dev plans, but I know for sure that at least one (me) did have a Dev plan in the past... could that have been enough to seed the issue..?

I work for a large USA corp, we have had many calls since 2020 with Microsoft licensing reps, we never get a clear answer as to what we need to buy. Back in 2020 there seems to have been a strong push towards creating solutions in Teams. Somewhere in the middle getting some E5 licenses became the solution, then suddenly E3 and E5 became the same thing with only E5 pre bundling PowerBi Pro.

Premium connectors never seemed to work unless you were inside a Teams environment, then suddenly one day, they just started working in all Environments, again the License reps had no answers.

Against the wishes of our CIO we continued pushing PowerApps and PowerPlatform to the point where we now have a fairly vital app that we use daily and have become dependent on it.. sadly that app is now the one giving us this amazing experience.

So what is the realistic next step, are we going to need Power Apps Premium licensing?

going to be a tough sell to management as $10-$20 per month in a tenant with 170k+ users is not exactly in the budgets.

Maybe the bright side is that we have an Exciting Project now to move all data out of Dataverse and in to multiple sharepoint lists....

[astrontelstar]

Same error message here.  FRUSTRATING.  I am paying the per user license and have my app in the Default environment.  We are a small company and this is working great, but what the heck Microsoft?