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.
All right, I did receive randomly that error message too, but sometimes went away, and finally my Dataverse for Teams app has an error that says something like I don't have a Power Apps plan.
Solution:
Problem solved, now the app works again.
Cheers,
Fernando
How odd. The only app which I was seeing the error message is still functioning fine and the error message has gone. I did contact Microsoft yesterday and was told that some people would have been receiving an incorrect warning.
They weren't bluffing...
Earlier this morning (GMT+1), our apps stopped working and requesting a premium license for all users that used to have a free developer license. The free developer license is also not visible anymore in the 'Plans' section on make.powerapps.com.
Just tried my problematic app at 00:00 on 01/12/2023 and the error message has gone away and the app still works!!!
Just tried out of interest exporting the solution and importing it in to the PRODUCTION environment. After minding all missing objects the export / import worked. However, now I am seeing the infamous 'you can't run an app created with a developer plan in a production environment and the app will stop working on 11/30/2023'. How therefore can one ever migrate an created and tested in a DEVELOPER environment??
Many thanks!!
I don't understand how I have this warning only for one of my apps. All of them, apart from specific ones I have in my Developer environment are within the company's Production (default) environment. However, for one of them inside this environment, I am seeing this issue? If I import it to the Developer environment, the warning goes away but how can I 'remove' the developer plan from it? How can this have happened if it's never been created inside my Developer environment? Many thanks
I can't understand why I am only seeing this warning for one of my apps when all of them are all within our standard company production environment?
I've just noticed this on one of my apps! The warning went away but it's come back. Do we think they may not work from tomorrow then. I am currently the only user of the app so I presume if this happens, I can still use it in PREVIEW mode as I don't see the warning then?
welp,.
we have made it to the 30th and tomorrow we get to see all the excitement that may or may not come from this.
I want to take a moment to thank everyone in this community, I have learned a ton over the few years that I have been here.
Microsoft Licensing has never been clear or easy to understand, at the very least on the corporate level.
in 2020 I was brought in to this world specifically as management wanted me to understand "what licensing we needed to continue using these solutions. I'll never forget my first call with Microsoft corp reps where they basically told us that they did not know and that instead we should use the Teams Environments to create all our solutions...
in 2020, you could not add or even view "premium" connectors wihtout having "premium licensing"
and no one had any clue on what we needed to buy.
at somepoint in 2021 or maybe 2022, staff suddenly had access to premium connctors and the HTTP requests became a hot connector to use,
by 2023 - Microsoft still could not provide us an answer on what we needed and suddenly the E3 and E5 licensing was the same in the real of o365 with E5 becoming only needed for those corps that need/want the extra identity feautres.
This is not a small biz, I'm talking about a large USA based holding company with over 160k users in our tenant.
and still no one could give us a clear answer on what licensing we needed to buy...
Ironically enough, earlier this year some of our management got courted by BMC,
everything was very clearly presented, they knew what to buy, they bought it and now we are going strong with BMC and their whole suite of products.
I'm eager to see how things play out tomorrow with some of our apps/flows and sadly it wont matter as all solutions created in o365 power platform are already being migrated to BMC solutions.
Yes, I agree! I don't really need it and my newer smaller apps all run from SP lists as I have now figured out how to prevent access to the lists directly from the Sharepoint site. I think I may move this latest one back over to SP lists as well! Many thanks.
WarrenBelz
211
Most Valuable Professional
MS.Ragavendar
108
stampcoin
80