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
Microsoft Copilot Studio – Build enhanced connectors with the Power Platform Connector SDK and PowerFx
We are announcing the ability to create enhanced connectors for makers in Power Apps and Copilot Studio. This feature will reach general avail...
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...
MVPMDEVANEY For $100 Off Power Platform Conference 2025
Use my Power Platform Conference 2025 Discount Code: MVPDEVANEY for $100 off registration. Follow this ... The post MVPMDEVANEY For $100 Off P...
Microsoft 365 & Power Platform Call (Microsoft Speakers) – September 2nd, 2025 – Screenshot Summary
Call Highlights  SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...
Power Platform Backup & Recovery
Power Platform backup & recovery Power Platform often contains critical business applications required for the daily work of the organizat...
Power Platform | Masking rules (Preview)
Let’s say you are storing sensitive information such as credit card numbers, SSNs, or users’ email addresses, and you want to protect this inf...
Power Platform – Mask sensitive data fields with column-level security
We are announcing the ability to mask sensitive data fields with column-level security in Power Platform. This feature will reach general avai...
Power Platform – Take advantage of expanded Virtual Network support
We are announcing the ability to take advantage of expanded Virtual Network support in Power Platform. This feature will reach general availab...