I have invested more than 4 months developing my first PowerApp and in the stage where my users (company staff) are testing it. I got a message from one of the users of an issue in the app, which I fixed and republished. Now, I have to extend my trial !!!. I'm using a single Azure SQL DB Connector. How could I not see this comming? Why I haven't been warned with a notification while developing my PowerApp that the connector that I'm using will not be free any more after Oct 1st 2019? I don't have time to read blogs and white papers, but have I missed something that I shouldn't have?
This seems to have been exclusively announced at their conference in September, and took effect just a couple weeks later at the start of October. I discovered it almost entirely on accident as well via someone mentioning it in a totally unrelated thread about another PowerApp issue I was having. They definitely fell flat on this changeover in a lot of ways, but they also seem to be okay with it decimating the population that can feasibly use PowerApps that aren't also utilizing Dynamics365.
I tested the apps again this morning and I was able to get into them in both Play and Edit modes.
Can anyone confirm your app is no longer asking for the trial license?
My apps have all seemed to be granfathered in still... I have made changes and can still access them. I contacted Support today to make sure that the grandfathering is based on Created date and not Modified date and they confirmed. It must have been a glitch if you were unable to access them. Below is the email I received:
Thank you for contacting Microsoft Support.
My name is Aditya Choudhary and I am the Microsoft Support Engineer who will be working with you on support request.
To answer your questions grandfathering is based on the creations date of the app.
App should be created before the October 1st.
Hope this helps. Please let us know if you have further queries.
Aditya Choudhary (MINDTREE LIMITED)
PowerApps and MS Flow Support
Backup Email: email@example.com
Working hours: 9 AM - 6 PM PST
If you have any feedback about my work, please let either me or my manager Sudip Dasgupta know at firstname.lastname@example.org
I don't think this has been completely ironed out yet.
While I can confirm it is working as expected using the URI:
The following is NOT working using the format (this is the way we embed PowerApps into Microsoft Teams / website App without the global toolbar):
In case anyone want to hide the Nav bar using the new URI - please see this https://powerusers.microsoft.com/t5/Building-PowerApps-Formerly/Hide-PowerApps-Navigation-Bar-Perman...
I just don't understand how businesses can make decisions when the licensing is constantly changing. We decided to go with PowerApps and Azure SQL as our platform due to having Office 365 licensees for 5500+ employees. The monthly costs would now be extraordinary. How does this help at all with PowerApps adoption? Luckily a lot of the workflows were built in Logic Apps. We will now have to port all the UI to a web app on Azure. Am I correct in understanding that we can continue making apps with Azure SQL until Oct 2020 and our existing app will work until Oct 2024. If I make a change to the app (of course required) will it still work until 2024 or does that constitute a new app? If the app will only work for 1 year then I don't think further investment is worthwhile. Does Microsoft understand how bad this makes their partners look for evangelizing PowerApps?
This will be a conference that you do not want to miss!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Apps features and capabilities at the free Microsoft Business Applications Launch Event.
Featuring samples like Return to the Workplace and Emergency Response Applications
Features releasing from October 2020 through March 2021