Recently, while working on a Power Automate flow to create three different sites, I encountered a strange error that prevented me from saving the flow. The error message said:
user with id e076c594-a317-ef11-ef11-6045bdda79a2 does not have ReadAccess right(s) for record with id 208c9ffc-a317-ef11-ac20-6045bdd58a22 of entity Connection Reference. Consider assigning a role with the level BusinessUnitLevel to the user or team. For further troubleshooting, please work with a system administrator to use the Access Checker tool on this record: https://weteamworkdefault.crm.dynamics.com/main.aspx?forceUCI=1&pagetype=entityrecord&etn=connectionreference&id=a317c-e67c-ef11-a317-6045bdda317. More details: {"CallerPrincipal":{"PrincipalId":"a317-9145-ef11-a317-6045bda317","Type":8,"IsUserPrincipal":true},"OwnerPrincipal":{"PrincipalId":"de76c594-9145-ef11-a317-6045bdda79a2","Type":8,"IsUserPrincipal":true},"ObjectId":"a317-e67c-a317-ac20-6045bdd58a22","ObjectTypeCode":a317,"EntityName":"connectionreference","ObjectBusinessUnitId":"a76e00a9-a317-ef11-a317-6045bddc1ce3","RightsToCheck":"ReadAccess","RoleAccessRights":"None","PoaAccessRights":"None","HsmAccessRights":"None","GrantedAccessRights":"None","MinimumDepth":1,"Messages":["UserLevelMinimumPrivilegeDepthRequired = None","EntityUserGroupRights = None","BusinessUnitLevelMinimumPrivilegeDepthRequiredRights = ReadAccess","SecLib::AccessCheckEx2 failed. Owner Data: User principal de76c594-a317-ef11-a317-6045bdda79a2 is not loaded in UserDataCache yet; Principal Data: roleCount=2, privilegeCount=a317, accessMode='0 Read-Write', AADObjectId='45be5403-a317-4822-b7fe-09434736a0dd', MetadataCachePrivilegesCount=a317, businessUnitId=a317-e544-ef11-a317-6045ba317"],"EntityOwnershipTypeMask":1,"CallerInfo":{"IsSystemUser":false,"IsSupportUser":false,"IsAdministrator":false,"IsCustomizer":false,"IsDisabled":false,"IsIntegrationUser":false,"Teams":null,"Roles":null},"ReadOnlyState":"UserAndOrgFullAccess","IsHsmEnabled":false,"HsmInfo":null,"AccessOrigin":null}

This typically occurs when the user lacks the necessary permissions to access a Connection Reference in the environment. However, in my case, I already had access to the environment required, and everything appeared to be fine.
If you’re encountering this issue, don’t worry, you’re not alone. In this post, I will explain what caused the error and the quick solution that finally worked for me.
[Solution] User Does Not Have ReadAccess for Connection Reference
After checking permissions, roles, and connection references, I realized the issue wasn’t with access at all, it was the flow itself.
I created a copy of the same flow using Save As, and the duplicated flow saved successfully without showing the error.

This confirms the issue was caused by a corrupted or partially broken reference inside the original flow. Duplicating it regenerates the internal connection reference bindings, which resolves the ReadAccess issue instantly.
Also, you may like the following tutorials:
- Invalid Connection. Please Choose a Connection Power Automate
- [Solved] You do not have permission to view the membership of the group in SharePoint
- The execution of template action ‘Switch’ failed – Error in Power Automate
- Attempted to perform an unauthorized operation in Power Automate
- Restrict User Access to Specific Document Libraries in SharePoint

Hey! I’m Bijay Kumar, founder of SPGuides.com and a Microsoft Business Applications MVP (Power Automate, Power Apps). I launched this site in 2020 because I truly enjoy working with SharePoint, Power Platform, and SharePoint Framework (SPFx), and wanted to share that passion through step-by-step tutorials, guides, and training videos. My mission is to help you learn these technologies so you can utilize SharePoint, enhance productivity, and potentially build business solutions along the way.