Skip to content

Commit 80f689d

Browse files
committed
Merge remote-tracking branch 'origin/main' into JasonHQX-patch-3
2 parents e984674 + d683b9d commit 80f689d

File tree

10 files changed

+66
-1
lines changed

10 files changed

+66
-1
lines changed

powerapps-docs/maker/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2577,6 +2577,8 @@
25772577
href: ./canvas-apps/studio-versions.md
25782578
- name: Troubleshoot startup issues for Power Apps
25792579
href: /troubleshoot/power-platform/power-apps/troubleshooting-startup-issues
2580+
- name: Check model-driven app access for a user
2581+
href: ./model-driven-apps/app-access-checker.md
25802582
- name: Troubleshoot Power Query
25812583
href: /troubleshoot/power-platform/power-apps/troubleshoot-power-query-issues
25822584
- name: Support

powerapps-docs/maker/data-platform/azure-synapse-link-pipelines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Use the Azure Synapse Link to connect your Microsoft Dataverse data to Azure Syn
2828
2929
## Prerequisites
3030

31-
1. Azure Synapse Link for Dataverse. This guide assumes that you've already met the prerequisites to create an Azure Synapse Link with a Synapse workspace. More information: [Prerequisites for an Azure Synapse Link for Dataverse with your Azure Synapse Workspace](azure-synapse-link-synapse.md#prerequisites)
31+
1. Azure Synapse Link for Dataverse. This guide assumes that you've already met the prerequisites to create an Azure Synapse Link with Azure Data Lake. More information: [Prerequisites for an Azure Synapse Link for Dataverse with your Azure Data Lake](azure-synapse-link-data-lake.md#prerequisites)
3232
2. Create an Azure Synapse Workspace or Azure Data Factory under the same Azure Active Directory (Azure AD) tenant as your Power Apps tenant.
3333
3. Create an Azure Synapse Link for Dataverse with the **incremental folder update enabled** to set the time interval. More information: [Query and analyze the incremental updates](azure-synapse-incremental-updates.md)
3434
4. Microsoft.EventGrid provider needs to be registered for trigger. More information: [Azure portal](/azure/azure-resource-manager/management/resource-providers-and-types#azure-portal). Note: If you are using this feature in Azure Synapse Analytics, ensure that your subscription is also registered with Data Factory resource provider, otherwise you'll get an error stating that the creation of an "Event Subscription" failed.
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: App access checker for model-driven apps | Microsoft Learn
3+
description: Describes how to use the app access checker for model-driven apps.
4+
author: jbujula
5+
ms.author: jbujula
6+
ms.reviewer: matp
7+
ms.service: powerapps
8+
ms.subservice: mda-maker
9+
ms.topic: how-to
10+
ms.date: 06/23/2023
11+
ms.custom: template-how-to
12+
---
13+
# App access checker for model-driven apps
14+
15+
Use the app access checker tool to identify common issues found for a specific user that can occur when running a model-driven app.
16+
17+
Issues found by the app access checker include:
18+
19+
- If an app is visible to the user or not.
20+
- The reason why an app is visible or not visible to the user.
21+
- If the user has the required license.
22+
23+
## How to use the app access checker
24+
25+
Power Platform admins and makers can use the app access checker to search apps based on user principal name (UPN) or email address.
26+
27+
Open the diagnostics page in your browser by typing https://*environmentURL*/WebResources/msdyn_AppAccessChecker.html, such as *https://contoso.crm.dynamics.com/WebResources/msdyn_AppAccessChecker.html*. Then enter the UPN or email address in the box and then select **Search**.
28+
29+
## How to interpret the results
30+
31+
- **Visible**.
32+
- If the user doesn't have read privilege on the app module table, none of the apps are visible to the user, and **No** is displayed.
33+
- If the user has read and/or write privilege on the app module table, then all the apps are visible and **Yes** is displayed.
34+
- **License**.
35+
- If the user has appropriate licensing to play the app, **Yes** is displayed.
36+
- **Security**.
37+
- If the user has create or write privilege on the app module table, **Yes** is displayed. If the user isn't associated to one or more security roles assigned to the app, check if the user is member of a team and whether the team is associated with that security role.
38+
39+
### Example results
40+
41+
User has access to all visible apps in the environment.
42+
:::image type="content" source="media/app-access-checker/user-can-view-apps.png" alt-text="User has access to all visible apps in the environment" lightbox="media/app-access-checker/user-can-view-apps.png":::
43+
44+
User doesn't have visibility or access to any apps in the environment because of missing security role membership associated with each app.
45+
:::image type="content" source="media/app-access-checker/user-no-access.png" alt-text="Assign security roles to app" lightbox="media/app-access-checker/user-no-access.png":::
46+
47+
Two examples where the user has visibility to some apps but not others because of missing security role membership associated with the app.
48+
:::image type="content" source="media/app-access-checker/user-access-role.png" alt-text="User has access to some apps visible but not others" lightbox="media/app-access-checker/user-access-role.png":::
49+
50+
:::image type="content" source="media/app-access-checker/user-access-role-2.png" alt-text="Assign missing security roles to user" lightbox="media/app-access-checker/user-access-role-2.png":::
51+
52+
In this example, the user has the required security privilege for the app but doesn't have the required license to access some of the apps.
53+
:::image type="content" source="media/app-access-checker/user-no-license-access.png" alt-text="User doesn't have required license." lightbox="media/app-access-checker/user-no-license-access.png":::
54+
55+
In this example, the user doesn't have the required security privilege, so the app access checker isn't able to show licensing details.
56+
:::image type="content" source="media/app-access-checker/user-no-security-access.png" alt-text="Missing privileges to run the app" lightbox="media/app-access-checker/user-no-security-access.png":::
57+
58+
If **Security** is **Yes** and **License** is **No** or **Unknown** contact Help + support. More information: [Get Help + support](/power-platform/admin/get-help-support)
59+
:::image type="content" source="media/app-access-checker/user-yes-security-no-license.png" alt-text="Licensing issue is detected." lightbox="media/app-access-checker/user-yes-security-no-license.png":::
60+
61+
## Limitation
62+
63+
- App access checker doesn't show details for the Outlook App. This is because that information is only visible to Power Platform administrators.
66.4 KB
Loading
74 KB
Loading
45.8 KB
Loading
72.9 KB
Loading
143 KB
Loading
94.5 KB
Loading
117 KB
Loading

0 commit comments

Comments
 (0)