This appears to be a user licensing or entitlement issue, rather than a problem with the SharePoint list permissions or the complexity of the form.
SharePoint, Office 365 Users, and Office 365 Outlook are standard connectors. Therefore, a SharePoint-integrated customized form using only these connectors normally does not require a separate Power Apps Premium license. However, each user still needs a Microsoft 365 license that includes the seeded Power Apps entitlement, and the Power Apps service must be enabled for that user.
The Power Apps Community Plan or Developer Plan is intended for individual development and testing. It does not provide production usage rights to other users and should not be relied upon for an organizational SharePoint form.
I recommend checking the following:
1. Review the affected users’ licenses
Confirm that the users have a Microsoft 365 license that includes Power Apps for Microsoft 365. In the Microsoft 365 admin center, expand the user’s assigned license and verify that the Power Apps service plan is enabled.
Having SharePoint access alone does not always mean the user has an active Power Apps entitlement. Some SharePoint-only, frontline, guest, or custom license configurations may not include it.
2. Confirm that the form contains only standard connections
Open the customized form in Power Apps Studio and review:
Data sources
Connections
Power Automate flows called from the form
Custom components
Any recently added connectors
The three connectors listed are standard, but a flow called by the form may contain a premium connector, custom connector, Dataverse action, HTTP action, SQL connection, or on-premises gateway. That could cause users to require an additional Power Apps or Power Automate license.
3. Check the environment and ownership
Verify that the form was created in the organization’s tenant and not under a personal Community or Developer Plan environment. A SharePoint customized form should normally be associated with the SharePoint list and the tenant’s default Power Platform environment.
Also confirm that the owner account and affected users belong to the same Microsoft 365 tenant.
4. Check the users’ connector access
Although SharePoint-integrated forms are accessed through the list, users may still need to authorize the Office 365 Users or Office 365 Outlook connections the first time they open the form.
Confirm that:
The connectors are permitted by the organization’s DLP policies.
The users are allowed to create the required connections.
Exchange Online is available if the form uses Office 365 Outlook.
Conditional Access policies are not blocking Power Apps.
5. Test with a controlled user
Select one affected user and temporarily assign a Microsoft 365 license known to include Power Apps. After the license is assigned, allow time for provisioning, sign the user out, clear the browser session, and test the form again.
If the form works after that change, the issue is most likely the user’s existing license or disabled Power Apps service plan.
The recommended production approach is to retain the existing SharePoint-integrated form, keep all connections and flows within standard licensing entitlements where possible, and ensure every internal user has a Microsoft 365 license that includes Power Apps. You should not need to rebuild the form or revert to the default SharePoint form unless the current form depends on premium capabilities.
