Forum Discussion
Anthropic Claude Purview Data Connector showing all users as Guests..
It appears this connector is not mapping fields properly causing internal users to be mapped as "guests", and since prompts/data isn't maintained for guest users the connector is effectively not gathering anything but noise. Unlike the other data connectors, one cannot create field mappings. Also the app being named using the guid of Microsoft's own "dataassessments" service principal I don't think is intended either. Has anybody else experienced this? See below for an example.
7 Replies
Ticket has so far gone nowhere, however today in DPSM this now appears over each log entry for Claude.
"Limited user context available
Anthropic interactions don't currently include user context in the data sent to Microsoft Purview and are treated as guest interactions."
Which of course contradicts the connector documentation and begs the question -- if it doesn't include user context what use is the connector besides logging useless noise and running up PAYG charges?Support has of course been useless, but today I now see this in activity explorer... Not sure if this is now by design or not, but it might as well be completely disabled as there is no useful info captured at all.
Limited user context available
Anthropic interactions don't currently include user context in the data sent to Microsoft Purview and are treated as guest interactions.
This, I see the guest and Guid naming issue. The agent ID is passed as the correct user name from Anthropic though. Ticket raised on the anthropic side, guess Microsoft is fixing it "live".
This, seeing the same issue with the guest internal mapping, though the agent ID reflects the correct user name so Anthropic is passing it to MS. Ditto on the guid naming for the app. I've jumped through a support ticket process with Anthropic which has gone quiet. Guess it's new and MS are testing live.
Sigh. Thanks for the confirmation that I’m not alone. At least now I won’t bother opening a ticket that will go nowhere.
The connector did at least briefly pass the agent name (Our user IDs) to Purview, but this has now stopped working too.
