Copilot suggested B and I asked why not D?. This was the response
"Sharing the app with a security group in Teams is indeed a valid approach for managing access. However, the key step to ensure users can view and use the app in Teams is to publish the app. Publishing makes the app available and visible to users
within Teams1.
Sharing the app with a security group can be done after publishing to manage who has access, but it won’t make the app visible if it hasn’t been published first"
d for me.
1) do they mean 'personal Power App' in microsoft teams or 'Power App' not very clear.
2) (still not clear to me) could you make a 'personal Power App' for MS Teams Dataverse in the maker portal? Maybe this is the point they want to test (since 3 invalid options suggest Maker portal).
If question is about "personal Power App" [referring to an app that is designed for individual use within Microsoft Teams, utilizing Dataverse for Teams, the process is integrated into the Teams environment]: maker not suitable. Remaining C or D. Sharing more appropriate as there is no requirement ‘ALL users’, just users access it.
Correct answer is D
After you click share, you get a pop up with: "Enter or select a security group"
https://learn.microsoft.com/en-us/power-apps/teams/set-perms-and-share
Correct D also for ChatGpt: To ensure that users can access the Power Apps app in Teams, you should share the app with a security group in Teams.
Here are the steps to do so:
1. Assign the correct permissions for the tables in your app for the Colleagues with access role.
2. Select a security group you would like to assign to the Colleagues with access role1.
3. Choose which apps the Colleagues with access role should have access to.
4. Once you’re done sharing your apps, they’ll appear in the Built for your colleagues section within the Teams app store.
So, the correct answer is D. Share the app with a security group in Teams.
Option C suggests requesting a tenant administrator to pin the app to the app bar in Teams. This action would make the app easily accessible for all users in the organization.
Option D suggests sharing the app with a security group in Teams. While this action can provide access to the app for the specified security group, it may not address the issue of app visibility for all users.
The word 'all' is missing in the question. it is users plural but it does not necessarily mean that all users have to get access. So the point you mention has directed me away from C towards D.
I hope they will make better questions where we would not have to wonder and figure out how things are meant. 'some users' or 'all users' should have been part of the question so that we are able to respond correctly.
D. Share the app with a security group in Teams.
This is the correct approach because once an app is created in Microsoft Dataverse for Teams, you can share it with specific people or security groups directly in Teams. Remember that Microsoft Dataverse for Teams apps are automatically published when they're saved, so there's no need to separately publish them like you would in the Power Apps Maker portal.
It is not B because when you create a Power Apps app specifically for Teams using Microsoft Dataverse for Teams, you don't use the Maker portal to publish it. Instead, you publish the app directly within Teams. The previous provided link helps: https://learn.microsoft.com/en-us/power-apps/teams/dataverse-for-teams-table-permissions
tried all the scenarios.
A. Share the app with a security group by using the Maker portal.
Not possible with Teams. you choose what apps to add to Teams not share.
B. Publish the app by using the Maker portal.
no. apps are published in Teams portal
C. Request that a tenant administrator pin the app to the app bar in Teams.
yes. you can pin an app to Team Channel.
D. Share the app with a security group in Teams.
no. apps are not shared but added to Teams by admin. security groups not in teams but onedrive and sharepoint in ms 365.
E. Share the app with individual users by using the Maker portal.
no. app are added not shared to teams
Answer from chatGPT
B. Publish the app by using the Maker portal.
If the app has been created using Microsoft Dataverse for Teams, it must be published in order for users to be able to access it in Teams. Sharing the app with a security group or individual users is not sufficient to make the app visible in Teams. Requesting that a tenant administrator pin the app to the app bar in Teams may improve visibility, but the app still needs to be published in the Maker portal.
answer: D
Colleagues with access: With Power Apps for Teams, you can share an app with Azure AD security group whose members need not be part of the Teams team where the app was built. This enables you to add users to the application without having to add them to the specific team, and opens up “Broad Distribution” scenarios. For example, you may want to build an app that is enabled for every accountant in the organization, or even every employee in that organization.
https://learn.microsoft.com/en-us/power-apps/teams/dataverse-for-teams-table-permissions
It has to be D
Again one of those questions that are absolutely unclear about the goal. Do users require access to the app, do users want to add the app from the store? Who are the users...
Anyway, C does not give access to the app. Teams Admins, Teams App Admin or tenant admin could Pin an app to the bar or via a policy for groups, users, or all users. Before that, they would have to upload the app in the developer portal, publish it for approval and finally approve the app, which would add it to the store. But this only allows to install the app. It does not give access to the app automatically. Owners have still to share the app with users or groups. If the app has not been shared, users will get the usual access denied screen. I have been there.
Also we are talking about a Dataverse for teams environment. You can share a Power Apps build in a team only with a single M365 or security group, not with individuals.
The question doesn't make it clear if it's for a user, a group, or everyone. Even so, I think you would need to ask a tenant admin to pin the app to the app bar in Teams.
I explain:
To make a Power Apps app for Microsoft Teams created with Microsoft Dataverse for Teams accessible to users, it must be added to the app bar in Teams, which can only be done by a tenant administrator. Therefore, you should request that the administrator pin the app to the app bar. Although sharing the app with a security group using the Maker portal (A) or Teams (B) would allow members of that group to access the app, they would still need to locate and open it.
no where does it state that it shouldn't be made available to anyone either
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
33a7f9e
2 months ago5f14337
4 months, 1 week agohoo898
5 months, 1 week agojkaur
8 months agoMrEz
10 months, 4 weeks agoJoey444
1 year, 1 month agodony85
1 year agouberlord
1 year, 4 months agokty
1 year, 4 months agoMrEz
10 months, 4 weeks agoinscho
1 year, 4 months agoLuay
1 year, 7 months agocharles879987
1 year, 7 months agoopai677147
1 year, 8 months agoMicrosoftTheFuture
1 year, 8 months agoJons123son
1 year, 8 months agoJons123son
1 year, 8 months agofariasalan86
1 year, 9 months agoRichXP
1 year, 10 months agouberlord
1 year, 4 months ago