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.

[jed76]

Exactly the same as my end. I have two apps, both in the same environment, both use premium connectors and one gives the message and one doesn't!? Hopefully it will sort itself out!

[HEATFreight]

Which is giving the error message, the app with premium connectors?

[jed76]

They both use premium. This why it's so odd. 

[HEATFreight]

Hey Microsoft, are you guys daft? You have countless users suddenly suffering an issue that appears to be not our fault.

Perhaps you have a bug?

Perhaps you should take this seriously and escalate it to the top?

Perhaps you should stop making your developers look like amateurs by publicly accusing them in front of their users (via this stupid error message) of improper configurations. If you are wrong, you make your devs look bad, which is off-putting and unlikely to increase developer retention! If you are right about that "dev plan in production environment" crap, you still make your devs look bad, but why couldn't it have been an email to the developer instead of making them look incompetent in front of all their users?

Perhaps it is you, Microsoft, who is incompetent.

Get your 💩 together.

[DilKry]

I have started to see this in my company's tenant as well. The Dataverse for Teams database was created in MS Teams which is included in our E3/E5 licensing. The environment that the Dataverse database exists is in its own environment that was created when the Dataverse database was created in MS Teams. There should be no issue with the licensing for this project.

I think there is a lot of confusion in Microsoft when it comes to Dataverse for Teams. It appears their tools look at Dataverse for Teams the same as standard Dataverse. I had a Microsoft rep look at auditing reports and saying that I am not properly licensed for Dataverse in our organization but I keep advising her that we are using Dataverse for Teams which is included in our E3/E5 licensing so we do not need additional licensing for this.

[chico]

@DilKry 

curious, are all your users in that same Team and are they all getting the message or only a few?

Our setup sounds much like yours, but we do not see the message consistently with all staff on the same team.

[HEATFreight]

Oh weird, I just tested this for all users, and so far I'm only seeing it for me. I guess I assumed it was visible to everyone, but nope, just me so far. I am the only maker. Still, it seems like a misleading or erroneous warning.

[chico]

@HEATFreight 

I'm the only owner of the app in question but we have a total of about 40 users.
I see the error message and about 10 others also see it.
but the majority -Do not see it... 

[DilKry]

So far, I have just seen it but I see it every time I access the app. No other users have reported this but the banner is so slight that most users will probably not notice it. My concern is that this does not disable my app on 11/30 as this is a business crucial app.

[iantesting]

Yes, Microsoft's silence has been deafening...

While doing some digging, noticed that our critical App that is in danger apparently contains a Premium connector... Which is odd as I made sure that it didn't. So I published an blank app in another Team with just a Dataverse connection, License designation "Standard". As an aside I also saw the dev plan warning straight away. Added a SharePoint connection to the App and now it is designated "Premium"?