Skip to main content

Notifications

Announcements

No record found.

Dynamics 365 Community / Blogs / D365 Pro Desk / Troubleshooting D365 /Power...

Troubleshooting D365 /PowerApps Login

Login issue | Login Error | PowerApps Login | CDS

Users experiencing access issue when logging into a Common Data Service environment or when accessing model-driven apps can see more context on the issue, including the cause of the issue, the environment’s name, error code, and a link to troubleshooting documentation. When they share this context with admins, it can help admins troubleshoot and address the access issue.

Multiple factors affect user access to Common Data Service environments. Administrators can use the Run diagnostics command to assess user access to a Common Data Service environment, and get details and mitigation suggestions as to why a user can or can’t access the environment.

To access a Common Data Service environment, a user must meet the following criteria:

  1. Be enabled for sign-in in Azure Active Directory (Azure AD).
  2. Have a valid license that has a Dynamics 365 or Microsoft Power Platform recognized service plan, or the environment must have active per-app plans.
  3. Be a member of the environment’s Azure AD group (if one has been associated with the environment).
  4. Have at least one Common Data Service security role assigned directly to them or to a group team they’re a member of.

A user’s level of access within the environment and to the resources (apps and data) in the environment is determined by the privileges defined in the security roles assigned to that user. Their access mode being Administrative or Read-Write also determines their level of access within an environment.

Use the following steps to run user access diagnostics on a user in a Common Data Service environment.

  1. In the Power Platform admin center, select an environment.
  2. Select Settings > Users + permissions > Users.
  3. Select a user.
  4. Select Run diagnostics.

Note
The action of running or rerunning diagnostics will force the user information in Azure AD to synchronize to the environment’s Common Data Service database to provide up-to-date status on the user’s properties. If the diagnostic run doesn’t eliminate the root cause of a user access issue, please provide the results of the diagnostic run in the support ticket you create; this will greatly help Microsoft Support engineers to resolve your issue faster.


This was originally posted here.

Comments

*This post is locked for comments