Dataflow Change with # InsightsAppsPlatform

(2) Share

Report

Posted on by krodgers

Recently a dataflow that was setup over a year ago has started to fail because it is saying # InsightsAppsPlatform doesn't have access locked security columns. This started to happen on August 3rd which caused over 1 millions records to be deleted. I have since recovered them. This looks to be a bug because if this Microsoft System account is now required for dataflow it should have full access to all columns regardless of Column Security setup. In order for the dataflow to work i needed to add this account to the Column security which I didn't have to before. Hope this helps others before they have this issue.

Thank you

Categories:

Microsoft Dataverse with Power Apps

I have the same question (2)

All responses (7)

Answers (0)

Sort by

Suggested answer

SwatiSTW 809 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Looks like a recent change made dataflows run as #InsightsAppsPlatform, which now honors Column Security. If that identity can’t read locked columns, rows look “missing” and get deleted.

Fix: add #InsightsAppsPlatform to the relevant Column Security Profiles (ensure Read on key/mapped columns).

Temporarily avoid destructive sync (“delete rows not in source”) and monitor deletes.

Report to Microsoft as a possible regression/behavior change.

1 people found this reply helpful.

Was this reply helpful? Yes No
CL-17091254-0 9 on at

Like (1)

Report
Copy link

Link copied!

Wish I had seen this post sooner, same problem here on 12/09/25. Caused tens of thousands of rows to be deleted. Support ticket raised to MS.

Was this reply helpful? Yes No
Suggested answer

blink182_joel 24 on at

Like (2)

Report
Copy link

Link copied!

Absolutely shocking from Microsoft. How these changes are made without any consideration to its customers, speaks volumes. Would like to add that, for me, I couldn't just add in the AppsInsightsPlatform user, I had to create a separate profile, which allows Read, Update and Create. The profile I had for a group of users, only had read. Adding that user to it, still didn't allow updates. So the reply from @SwatiSTW isn't quite right.

Was this reply helpful? Yes No
CL-17091254-0 9 on at

Like (0)

Report
Copy link

Link copied!

Same has happened again for me yesterday and today. Same account, no changes made.

Was this reply helpful? Yes No
MF-12051538-0 406 on at

Like (0)

Report
Copy link

Link copied!

This issue began happening to me at the end of April. I've had a Microsoft ticket open for quite some time but nobody seems able to help. Did anybody in this thread receive a fix or workaround to this issue?

Was this reply helpful? Yes No
Suggested answer

11manish 2,635 on at

Like (0)

Report
Copy link

Link copied!
Try below:

Add the # InsightsAppsPlatform application user to the appropriate Field Security Profile.

Grant access to the secured columns used by the Dataflow.

Re-run and validate the Dataflow.

If your Dataflow starts reporting errors related to secured columns, verify that # InsightsAppsPlatform has the required field-level security permissions.

This behavior may be related to a recent platform change in how Dataflows enforce Dataverse security.

Best Practice:
Regularly review Field Security Profiles and ensure all application users involved in Dataflows have the necessary permissions before running synchronization or

delete operations.

Was this reply helpful? Yes No
MF-12051538-0 406 on at

Like (0)

Report
Copy link

Link copied!

I tried that with no luck. The problem is that it's not populating whatever columns make up the alternate key used in the dataflow. Those columns have no security on them, and when I change what columns make up the key, it changes what columns don't populate data.

For example, I have columns Company_ID and Entry_No -- these are the columns used in PrimaryKey. When I use PrimaryKey as the dataflow Key, Company_ID and Entry_No are all blank. I created duplicate columns called Temp_Company ID and Temp_Entry_No and map the exact same columns to those as Company_ID and Entry_No. I created a new key called TempKey and use that as the dataflow key. Now the original two columns populate and the new 'Temp' ones do not.

It sounds like the TempKey is an adequate workaround but the problem is that since whatever columns compose the key are blank, the dataflow can't match any existing records and re-adds every single record every refresh.

Was this reply helpful? Yes No