Power Automate Process Mining: Troubleshooting License Errors for Seamless Access

Table of Contents

Power Automate Process Mining is a powerful capability within the Power Automate platform that enables organizations to gain deep insights into their business processes. By analyzing event logs, process mining helps identify bottlenecks, inefficiencies, and deviations from expected workflows. This visibility is crucial for process optimization, cost reduction, and overall operational excellence. However, like any sophisticated tool, Process Mining in Power Automate relies on proper licensing to ensure seamless access and functionality for all users involved. When users encounter licensing issues, it can disrupt their ability to access and analyze processes, hindering their ability to derive valuable insights. One common licensing error that users might encounter is the “The user has not been assigned any license” error. This article addresses this specific error, providing clarity on its symptoms, underlying causes, and practical resolutions to ensure uninterrupted access to Power Automate Process Mining capabilities.

Symptoms¶

The primary symptom of this licensing issue is the appearance of a specific error message when a user attempts to access a process within the Power Automate Process Mining environment. This error typically manifests when a process has been shared with a user who either has a disabled account or, more commonly, lacks the necessary Power Automate license. When a user tries to open or interact with a process under these conditions, the system will block access and display the following error message:

Error loading users for this process: the user (id=<GUID>) has not been assigned any License. Please contact your system administrator to assign license to this user for the action to succeed.

This error message is designed to be informative, highlighting the licensing problem and guiding users towards seeking assistance from their system administrator. The GUID (Globally Unique Identifier) mentioned in the message is a unique identifier for the user experiencing the error, which can be helpful for administrators in pinpointing the affected user account. It’s important to note that this error specifically occurs within the context of accessing a shared process. If a user is attempting to access a process they created themselves and encounters this error, the underlying cause might be different and require further investigation into their overall Power Automate licensing status.

Cause¶

The root cause of the “The user has not been assigned any license” error in Power Automate Process Mining is, as the message clearly states, related to user licensing. Specifically, this error arises because the user with whom a process has been shared does not possess a valid Power Automate license that includes access to Process Mining features. This situation can occur due to several common scenarios within an organizational context:

• User Account Disabled: If a user has left the organization or their account has been intentionally disabled for security or administrative reasons, their associated licenses are typically revoked or become inactive. If a process was previously shared with this user before their account was disabled, attempting to access that process by another user might trigger this error if the system checks the license status of all users associated with the process.
• License Revocation or Change: Organizations periodically review and adjust user licenses based on roles, responsibilities, and cost optimization. It’s possible that a user previously had a license that included Process Mining capabilities, but their license was subsequently changed to a lower-tier license that does not include these features. If a process was shared with this user when they had the necessary license, and they later lost it, this error can occur.
• Incorrect Initial License Assignment: In some cases, users might be provisioned with Power Automate licenses that do not include Process Mining from the outset. This could be due to an oversight in the initial license assignment process, or it might be intentional based on the user’s role if Process Mining was not initially considered necessary for their tasks. However, if their responsibilities evolve and they require access to Process Mining, they will need to be assigned the appropriate license.
• License Expiration: Power Automate licenses, like many software licenses, can have expiration dates. If a user’s license has expired and has not been renewed, they will lose access to the licensed features, including Process Mining. This scenario is less common in organizations with robust license management practices, but it is still a potential cause.

Understanding these potential causes is crucial for administrators to effectively troubleshoot and resolve the “The user has not been assigned any license” error. By identifying the specific reason behind the license issue, administrators can implement the appropriate resolution, ensuring that authorized users regain seamless access to Power Automate Process Mining.

Resolution 1: Delete the user from Dataverse¶

One effective resolution for the “The user has not been assigned any license” error, particularly when the issue stems from a disabled user or a user who has left the organization, is to delete the user from Dataverse. Dataverse is the underlying data platform for Power Automate and many other Microsoft Power Platform applications. User information, including access permissions and licenses, is managed within Dataverse.

When a user account becomes inactive or is no longer needed, simply disabling the account may not fully resolve licensing conflicts within Dataverse, especially if the user was previously associated with shared resources like Process Mining processes. Deleting the user from Dataverse ensures that all references to the user are removed, effectively eliminating any potential licensing conflicts related to that user’s account.

Steps to Delete a User from Dataverse (General Guidance):

1. Access the Power Platform Admin Center: Administrators need to access the Power Platform Admin Center, which is the central portal for managing environments, users, and settings for Power Platform applications, including Power Automate and Dataverse.
2. Navigate to Environments: Within the Power Platform Admin Center, select the specific environment where the Power Automate Process Mining process is located and where the user’s data resides in Dataverse.
3. Go to Users: Within the selected environment, navigate to the “Users” section. This section lists all users who have access to the Dataverse environment.
4. Locate the User to Delete: Search for the user account that is causing the licensing error. You can typically search by username or email address.
5. Delete the User: Select the user account and choose the “Delete” option. The exact wording and location of the “Delete” button might vary slightly depending on the Power Platform Admin Center interface updates.
6. Confirm Deletion: The system will typically prompt for confirmation before permanently deleting a user. Review the confirmation message carefully and proceed with deletion only if you are certain that you want to remove the user and their associated data.

Important Considerations for Deleting Users from Dataverse:

• Data Loss: Deleting a user from Dataverse is a permanent action and can result in data loss if the user was the owner of any records or resources within Dataverse. Before deleting a user, ensure that any critical data or ownership is transferred to another active user.
• Impact on Shared Resources: Deleting a user might impact shared resources or processes that were associated with that user. Carefully assess the potential impact on shared processes and make necessary adjustments, such as re-sharing processes with active users, before deleting the user.
• Synchronization with Azure Active Directory: Dataverse user management is often synchronized with Azure Active Directory (Azure AD). Deleting a user from Dataverse might not automatically delete the user from Azure AD. If you need to completely remove the user from the organization’s directory, you may need to delete the user from Azure AD separately.
• Consult Official Documentation: Microsoft provides detailed official documentation on user management in Dataverse and the Power Platform Admin Center. Always refer to the latest official documentation for the most accurate and up-to-date steps and best practices for deleting users.

By carefully deleting the problematic user from Dataverse, administrators can resolve the “The user has not been assigned any license” error and ensure that access to Power Automate Process Mining processes is granted only to users with valid licenses and active accounts.

Resolution 2: Revoke sharing permissions from the user using a Power Automate flow¶

Another effective approach to resolve the “The user has not been assigned any license” error is to revoke the sharing permissions from the user who is causing the issue directly within Power Automate, using a Power Automate flow. This method is particularly useful when you want to address the error without deleting the user from Dataverse, perhaps because deleting the user is not feasible or desirable due to other organizational dependencies.

By creating a Power Automate flow, you can programmatically remove the specific user’s access to the problematic Process Mining process. This ensures that the process is no longer shared with the unlicensed or disabled user, thereby resolving the licensing error for other users attempting to access the process.

Steps to Revoke Sharing Permissions using a Power Automate Flow:

1. Create an Instant Cloud Flow:

   • Navigate to the Power Automate portal (make.powerautomate.com).
   • On the left navigation pane, select My flows.
   • Click + New flow and choose Instant cloud flow.
   • Give your flow a descriptive name (e.g., “Revoke Process Mining Access”).
   • Select the trigger Manually trigger a flow and click Create.

2. Add the “Perform an unbound action” Action:

   • In your flow editor, click + New step.
   • Search for and select the Dataverse connector.
   • Choose the action Perform an unbound action.

3. Configure the “Perform an unbound action” Action:

   • Action Name: Enter RevokeAccess. This specifies the Dataverse action you want to perform.
   • Target: This field requires the URI of the Process Mining process from which you want to revoke access. The format is /msdyn_pminferredtasks(<PROCESS-ID>).
     • Replace <PROCESS-ID> with the actual ID of the Process Mining process. You can find the Process ID in the URL when you access the process in Power Automate Process Mining.
   • Revoke: This field requires a JSON object specifying the user from whom you want to revoke access. Use the following JSON structure:

   {
     "systemuserid": "USER-ID",
     "@{string('@odata.type')}\": \"#Microsoft.Dynamics.CRM.systemuser\"
   }
   

   
   * Replace "USER-ID" with the actual ID of the user you want to revoke access from. You can find the User ID in the error message itself (e.g., “user (id=<GUID>)”) or by looking up the user in the Power Platform Admin Center or Dataverse user settings.

   Here’s an example of how your configured “Perform an unbound action” might look:

   

4. Save and Test the Flow:

   • Click Save to save your flow.
   • Click Test in the top right corner to test your flow. Choose Manually and click Test.
   • Run the flow. If successful, the sharing permissions for the specified user will be revoked from the Process Mining process.

Explanation of the Action Parameters:

• RevokeAccess Action: This is a pre-defined action within Dataverse specifically designed to revoke access permissions.
• /msdyn_pminferredtasks(<PROCESS-ID>) Target: msdyn_pminferredtasks is the entity set name in Dataverse for Process Mining processes. By specifying the process ID in the URI, you are targeting the specific process from which you want to revoke access.
• Revoke Parameter (JSON):
  • "systemuserid": "USER-ID": This specifies the ID of the user whose access you want to revoke.
  • "@{string('@odata.type')}\": \"#Microsoft.Dynamics.CRM.systemuser\": This is metadata that explicitly defines the type of entity being referenced as a “systemuser” in Dataverse.

Benefits of Using a Flow for Revoking Permissions:

• Automation: Flows can be automated and even scheduled to periodically check for and revoke access from users who no longer have the necessary licenses.
• Non-Destructive: Revoking permissions is less destructive than deleting a user from Dataverse. It only removes access to the specific process and does not impact the user’s overall Dataverse account or other data.
• Auditing and Logging: Flow executions are logged, providing an audit trail of when and from whom access permissions were revoked.

By utilizing a Power Automate flow to revoke sharing permissions, administrators gain a flexible and controlled method to address the “The user has not been assigned any license” error, ensuring that Process Mining processes are accessible only to authorized and licensed users.

---

By implementing either of these resolutions, you can effectively address the “The user has not been assigned any license” error in Power Automate Process Mining and restore seamless access for your users. Remember to choose the resolution that best fits your specific situation and organizational requirements.

Do you have any further questions or experience with this licensing error in Power Automate Process Mining? Feel free to share your thoughts and comments below!