Resolving User Not Licensed Errors When Saving A Row (Microsoft Dataverse)

When working with the Microsoft Dataverse platform, you sometimes get presented with error messages in the strangest circumstances. Take, for example, a recent scenario where we were getting the following error message whenever we attempted to save a Case row within Dynamics 365 Customer Service:
The user with SystemUserId=1e18d5cd-72a6-462a-98ab-eb76b1f17b79 in OrganizationContext=e1c03efe-c3a0-4a35-9ed7-05f49ab97918 is not licensed, and its SystemUserAccessMode=0 is not either of (NonInteractive=4, SetupUser=1)
The error would fire against any operation we targeted against the table - such as saving a row or executing a plug-in that performed some action against the table. A close reading of this error would suggest that something is going on as part of the transaction invoking the context of a user that is no longer active within the environment. The joys of inheriting a system from another project. 😉 We checked a few things in the first instance on any plug-ins registered on the Case table:
- The value of the Run in User’s Context setting on all appropriate plug-in steps to ensure that the original developer hadn’t put it to the disabled user.
 - Verified that the code wasn’t impersonating the user in question.
 
Finally, as a punt, we noticed that the table had several real-time workflows executing against it. We decided to deactivate all of these workflows and then re-activate them, working on the assumption that something had been cached relating to the disabled user. This was despite the fact that another active service account owned the workflows. Doing this resolved the issue, and much to our surprise, the error no longer appeared.
I must say, this is the strangest Dataverse platform error I have faced for a while, and I’m still not 100% sure why the steps we followed resolved the issue. Answers on a postcard below if you can share any insights, but I hope this proves helpful if you encounter the same problem yourself in the future.
Published on:
Learn moreRelated posts
Power Platform admin center – Manage agent security with enhanced admin controls
We are announcing the ability to govern Copilot agent development in your environments and enforce governance policies for Copilot agents. Thi...
Microsoft Power Platform governance and administration – Use the new connector management rule
We are announcing the ability to use the new connector management rule in Microsoft Power Platform governance and administration. This feature...
Demystifying Clusters in Power Platform: What Architects and Developers Must Know
When working with Microsoft Power Platform—especially Dataverse—you’ve probably seen terms like Cluster Geo Name or Cluster URI Suffix in your...
🔄Power Platform Environment Restore: Options & Best Practices
Hi Folks, Restoring environments in Power Platform has evolved significantly. In the past, Dynamics CRM On-Premise users relied on SQL databas...
Power Platform – Planned maintenance
We have scheduled your Power Platform environment for planned service maintenance. This maintenance is intended to provide increased stability...
Power Platform admin center – Power Platform inventory is now available in Public Preview
The Power Platform admin center now offers tenant admins a comprehensive, unified view of all key resources across their organization via Powe...
Microsoft 365 & Power Platform Community Call (SPFx) – October 30th, 2025 – Screenshot Summary
Call Highlights  SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...
Power Platform admin center – Updates for security roles in child business units
We have scheduled an update for the Power Platform admin center that changes how Dataverse security role fields are populated in child busines...