'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Power Apps Error: The Specified User Could Not Be Found
Question details
The user is encountering a 'Leave Request failed: The specified user could not be found' error in Power Apps, which prevents the related process from running.
- Product
- Power Apps
- Device & OS
- not provided
- Scenario
- Submitting a leave request or triggering an approval flow that references a specific user account in the system.
- Observed behavior
- The system throws an error stating 'The specified user could not be found', indicating that the referenced user cannot be resolved.
Ensure you have the necessary administrative privileges to view active directories, user fields, and Power Automate flow configurations in your Microsoft 365 environment.
Verify User Fields and Connector Configurations
Check the form's user fields and the related Power Automate flow to ensure the referenced account is valid and correctly configured.
This error typically occurs when the app or flow tries to look up an email address or user profile that does not exist, is misspelled, or is disconnected in Azure Active Directory.
Open your app in Power Apps Studio and select the form triggering the error. Verify that any 'Person' or 'User' fields are mapped to a valid, active email address.
Navigate to the Power Automate flow connected to your leave request. Ensure the 'Assigned to' field contains a valid user account within your organization's directory.
Go to the 'Data' pane in Power Apps, locate the 'Office 365 Users' connector, and refresh it to ensure there are no authentication issues or broken connections.
Consult the Power Apps Community
If verifying the user fields does not resolve the issue, seeking specialized help from the official community is the best next step.
Discover WPS Office: A Free and Lightweight Office Alternative
While troubleshooting complex Microsoft Power Apps errors, you might be looking for a simpler, cost-effective solution for your everyday document, spreadsheet, and presentation needs. WPS Office offers a highly compatible and lightweight alternative to Microsoft Office.
- 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded installer file and follow the on-screen instructions to complete the setup in minutes.
- 3. Open your Microsoft Office files: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files without any formatting loss.
Frequently Asked Questions
Why does the Leave Request approval flow fail with a user not found error?
This usually happens if the email address assigned to the approver field in Power Automate is misspelled, inactive, or belongs to a user who has been removed from your organization's Azure Active Directory.
How can I test if the Office 365 Users connector is the root cause?
Navigate to the 'Data' tab in your Power Apps Studio, find the 'Office 365 Users' connection, and re-authenticate. If it prompts for credentials or shows a warning icon, the connector needs to be repaired or recreated.
Can external guest users cause this Power Apps error?
Yes, if your app or flow attempts to look up an external guest user who has not been properly provisioned or invited to your organization's tenant, the system will not be able to resolve their account, resulting in this error.
