'%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 Automate Forms Connector Error CAA20003
Question details
The user encounters an error code CAA20003 in Power Automate, indicating their account does not exist in the Microsoft Services tenant and cannot access the application, despite being able to use Microsoft Forms normally.
- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Trying to connect Microsoft Forms with Power Automate using the Forms connector.
- Observed behavior
- Power Automate displays a tenant account error (CAA20003) stating the user account does not exist, blocking the connection to the application.
Ensure that you are logging into both Microsoft Forms and Power Automate using the exact same organizational account credentials, and that your account has not been recently migrated.
Seek Assistance in the Microsoft Power Platform Community
Since error CAA20003 is often related to backend tenant configurations or connector glitches, reaching out to Power Automate specialists is the most effective approach.
This error generally occurs when there is a synchronization issue between your account and the Azure Active Directory (Entra ID) tenant that governs Power Automate. Community experts can investigate the tenant and account configuration behind this specific error.
Go to the Microsoft Power Platform Community website and navigate to the dedicated Power Automate forum.
Click on 'Ask a Question' or 'Start a Topic' to draft a new support request.
Describe your issue clearly. Mention the error code CAA20003 and emphasize that your account can still sign in to Microsoft Forms and manage forms independently.
Wait for a Power Automate expert or Microsoft support agent to reply with specific steps to investigate your tenant and connector configuration.
Re-authenticate the Forms Connector
Sometimes, cached credentials or expired authentication tokens cause the tenant account error. Recreating the connection might resolve the issue temporarily.
Try WPS Office for Your Daily Document Needs
While Power Automate and Microsoft Forms are specific to the Microsoft ecosystem, if you are experiencing frequent account or tenant issues with Microsoft Services, consider WPS Office as a free, lightweight, and highly compatible alternative for your document, spreadsheet, and presentation tasks.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package.
- 2. Install the Software: Run the downloaded installer and follow the simple on-screen instructions to complete the setup.
- 3. Start Creating: Open WPS Office and manage all your documents, spreadsheets, and presentations from one unified, user-friendly interface.
Frequently Asked Questions
What does error CAA20003 mean in Power Automate?
Error CAA20003 typically indicates an authentication failure where the token could not be acquired because the selected user account does not exist or is not recognized in the specified Microsoft Services tenant.
Why does my account work in Microsoft Forms but fail in Power Automate?
Microsoft Forms and Power Automate route through different authentication endpoints and may require different administrative permissions or licensing assignments within your organization's Azure Active Directory (Entra ID), leading to mismatched access rights.
Can I fix the CAA20003 tenant error on my own?
Usually, this error requires intervention from your organization's IT administrator or Microsoft Support, as it involves backend Azure Active Directory tenant configurations that standard users cannot modify.
