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.

[JF2022]

Majority of users are getting the above error in the Production environment. 

[Sai47]

Hi,

Have you upgraded to new license,is the issue resolved. Please let me know.Thanks.

[JF2022]

Hello @Sai47 would this solely be based on user requirement? Meaning each user needs a new license, would that be either PowerApps Premium or PowerApps PAYG for the App?

[Sai47]

Hi,

I dont think each user needs it but the developer needs this license.Really not sure about the issue.Thanks

[Meenu_A]

I removed the premium connectors then application falls under standard so that pop message is not reflecting now, in case you are using premium connectors then premium license is required.

[kky1]

I had posted a while back on this not understanding. As I worked through in detail with migrating apps, which are part of solutions from DEV to PROD I think I can offer a little more of an understanding. Our premium license holder was a service account for continuity of app ownership, etc. with employee turnover. I think I was getting this message because some of the flows and the app ownership was mine as the employee/developer and not the service account, so even though the app itself wasn't using a premium connector, the fact that the app was owned by me instead of the service account and that it was inside a solution that had flows that were using a premium connector was (I think) causing the issue. In short, every app/flow connection reference and owner inside a solution needs to be tied to the premium account holder or this message appears.

I've since left the position and had to go through the onerous process of reviewing not just the connections but also the ownership of every app and flow within every solution to ensure it was the service account. Then re-migrate to PROD (which takes about a half dozen tries because it's very much back and forth troubleshooting reading errors when the migration fails and having to go back to the DEV environment to guess which connection reference needs deleted/adjusted etc. - and since a connection reference can be in multiple solutions, this can get really frustrating very quickly). What I'm describing is the love/hate relationship I had with apps/flows - so much about it is pretty slick and cool but dealing with the connections, connection references and ownership issues when migrating from DEV to PROD is just insanity. 

[jed76]

Thanks. This is most interesting. I've currently got quite a large app in my developer environment and am not looking forward to migrating it to our standard production environment for all staff to access as it's not something I have really done before. I have plenty of other apps which I have created in our standard company production environment and all staff I share those with work with no bother. I have just never tried exporting from developer to production. It also makes use of Dataverse tables. If you have any tips, I'd be most grateful!

[kky1]

Hi @jed76 - Yes, you'll need everything to be in a solution in order to migrate to PROD from DEV. This process is intimidating, especially at first. Going forward, I suggest that you and any future developer ALWAYS be logged in as the premium account holder and build your apps and flows from INSIDE the Solution. Start with the Solution FIRST! (Sorry for all the caps, but this is what I wish I would've known - it would have saved me much frustration later!)

If you build flows or apps outside of a Solution, then you have to add them to a Solution later. When you add an existing app/flow to a Solution, you will have to drop all the connections and re-establish them as connection references as you can't use connections in a Solution. In addition, you'll need to ensure the owner of every app/flow is the premium account owner. (There is a flow you can run to change an app owner.) Allow yourself time (it took me DAYS) to get all this in order, especially if the Solution has many components. The app governance part of this community will have much info to guide you on this. I really wish you luck on this! 

[jed76]

Many thanks. To be honest, I'm not even sure what a SOLUTION is? Currently I have lots of apps and flows which I have created in my account within our main company production environment - these all work fine. 

My latest which is being created in my DEV environment is one which I will need to share at some point. Do you know how to add a custom user profile when I share the app? I keep getting a warning that I cannot add things such as SERVICE WRITER etc. for the dataverse tables anymore and I think I need to create a custom security role based on the Basic User one. I have done this and provided the access roles to the dateverse list, but I am unsure what to do next?!

[kky1]

Hi @jed76  - unfortunately I don't have much guidance for the scenario you are describing. My org shied away from Dataverse due to cost. I would post your question to the community in a new thread as I'm sure there will be someone who can help.