Hello everyone,
My latest video showcase the latest Power Apps Preview, Project Oakdale, and Microsoft Teams capabitilites in one video. We will build an App and create Tables with Project Oakdale and publish to Teams.
#msignite #ProjectOakdale
--------------------------------------------------------------------------------
Thanks,
Reza Dorrani, MVP
YouTube
Twitter
watch?v=6vdx7JDuCq4
Great video! Do you know if there is a Power Bi connector to access the data in Oakdale?
I saw other users asking the same question and I have been unable to find a good answer...
Do you know what we need to do in order to disable the ability for users to create Power Apps in Teams via Project Oakdale? We are concerned because each time this is done, a new environment is created in Power Platform Admin for the individual app. This could lead to sprawl rather quickly. Just today we had two users who spun up "test apps". If I'm not mistaken, tenants are limited to 500 environments.
The Power BI connector will require TDS endpoint to be enabled for the Oakdale environment.
Currently TDS is disabled for Teams environments and hence Power BI cannot connect to it.
Hopefully, we will have this soon.
--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
Thanks,
Reza Dorrani, MVP
YouTube
Twitter
Hi @beargal34
Great point. There is a 500 Teams limit as well - number of teams that can create Oakdale environments.
You can disable it using Teams policies.
--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
Thanks,
Reza Dorrani, MVP
YouTube
Twitter
Thanks Reza. We looked at that option. But according to my manager, it seems as if this option disables ALL Power Apps from MS Teams and we can't disable all of them as we have a few MS Teams that have added a Power App to their Team.
I have the exact same problem - curious users clicking buttons, but we have a number of existing PowerApps users access via MS Teams. For now, it looks like we are just forced to block access to the apps from teams. Inconvenient for the end-users, but a better option for us than trying to manage the environment sprawl if an option to disable on-the-fly environment creation isn't available - we have just two IT admins managing around 1000 users, and don't have time to play whack-a-mole with the various different things users keep enabling.
I can understand if there's no GUI option to turn this off (although at some point, this new habit MS has of releasing preview features to all our users without giving us an easy button-click way to disable it will become a problem!) but surely there must at least be a PowerShell command to control this?
Reza,
Just getting started with the PowerApps build experience in Teams. I am very, very concerned that while in the designer, if you navigate away from the designer in Teams, your changes are simply gone, no warning no nothing. I have noticed this as well using Canvas apps pinned to a channel tab. This could waste a significant amount of time, is there any though of fixing this?
Thanks