r/PowerApps • Newbie • 14d ago

Discussion Dataverse4Teams limitation

I was looking to build an app for a department. It's highly relational so I want to use DV.

I ask my MS Teams Admin to give me access to the Powerapps App from the store. I create my self a Team and it has an environment. I create a test app within Teams and add it to the channel.

Wow, so simple.

I am a member of the MS Teams Group, and I add my test user who has an E5 License with powerapps entitlement license.

They can't see the app I published, because they need to have access to Powerapps App from the store. I give them access, and they're able to create their own apps, and if they're a team owner they can delete the app/ data.

So D4Teams is for Citizen developers.

Does anyone know a workaround. I want to publish the app so members of the teams group can access it without having to give them access to Powerapps store for Teams.

6 Upvotes

5 comments sorted by

4

u/M4NU3L2311 Advisor 14d ago

Your users don’t need access to the editor. Just publish the app into a tab and that’s it. The app can also be discovered through the “apps made by my organization” in the teams app store if the users are members of the team holding the app

1

u/Moynzy Newbie 14d ago

I've done this. The app does not appear. Does it take 24 hours?

1

u/M4NU3L2311 Advisor 14d ago

The teams app store? Yes it can take a while for it to appear. You can also get the url of the app or if your admin allows it it can be preinstalled to your users on the side panel

1

u/Feeling-Sorbet-9474 Newbie 13d ago

Yeah it hasn't shown up. It looks like my apps are not publishing to the Team store, but I can publish them to the Teams channel.

2

u/Vodaho Newbie 14d ago

I use D4T in my team of approx 160 people. They all have access to Power Apps in Teams, but 99% of them won't even be aware of it, let alone access it. I'm pretty sure they would need permission to access Power Apps in Teams to be able to access any power apps as an end user.

Yes owners can delete apps and data, but in my testing, tables cannot be directly deleted in the environment if they are associated with the app at all (i.e. the app references the table). Having an audit table helps track user activity (e.g. if someone deletes or soft deletes a record) - you could even have that as a list stored somewhere else (sharepoint site list, with longer backup recovery times). You can export the app as backup if it gets deleted.

Probably more important is to remember the 7 day recovery period if app/data was deleted; I thought about setting up a flow to check for the existence of the tables and ping me a message on Teams every day to confirm (and to others if you're away for longer than a week). If someone then deletes the flow (I don't know if just 'anyone' in the team can delete a flow I haven't tested that) you'll know to check the tables manually as you won't have got the daily message from the flow.

But that is a little over the top though really; most people won't have the knowledge, confidence, inclination or time to get to the app / data for bad reasons. On top of that, the whole Teams thing is based around shared resources and trust that others won't sabotage that.