Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
[This article is prerelease documentation and is subject to change.]
This article describes current limitations of the computer use tool and provides solutions for common issues you might encounter during setup or execution.
Important
This article contains Microsoft Copilot Studio preview documentation and is subject to change.
Preview features aren't meant for production use and may have restricted functionality. These features are available before an official release so that you can get early access and provide feedback.
If you're building a production-ready agent, see Microsoft Copilot Studio Overview.
Limitations
The following limitations affect computer use:
- Hosted machine groups aren't supported.
- Multi-screen desktops aren't supported.
- In the agent's Activity tab, the agent session status might show as "In progress", although the session might be completed. Select a specific agent session and switch to transcript mode to validate that the computer use session is completed.
Hosted browser limitations
The service might throttle hosted browser usage based on demand. Therefore, it's not recommended for production use.
Note
You might see the error message "No machine able to run the automation has been found." when starting a computer use session on hosted browser. This error can occur if you already have an active session on hosted browser, if a demand-based throttling limit is reached, or due to an internal error. We're working to improve this experience.
The following scenarios might cause throttling:
| Category | Details | Impact |
|---|---|---|
| User based throttling | A user can have one active hosted browser session at any given time. Any subsequent computer use session on a hosted browser fails. | Session fail |
| Demand based throttling | Depending on overall demand, throttling might be applied and computer use session on a hosted browser fails. | Session fail |
Troubleshooting
If you encounter issues while using computer use, review these common problems and their solutions:
| Issue | Solution |
|---|---|
| Computer use execution fails with error: "Multi-factor auth (MFA) was detected as required for this account." When using Microsoft Entra ID credentials on a device with Network Level Authentication (NLA) enabled, or when Microsoft Entra authentication is required for Remote Desktop, you must either grant an MFA exception for the account or use certificate-based authentication. | - Disable NLA. Learn more in Desktop flows run failed with MSEntraLogonFailure - Provide admin consent for unattended runs using sign-in credentials with NLA. Learn more in Run unattended desktop flows. |
| A disconnected session exists for the user used in the connection on the target machine. Make sure the user signs out from any existing session. | - Connect to the machine using Remote Desktop. Open the Windows Start menu, select your user profile icon, and then select Sign out. |
| An automation is already running on the machine. Retry later. | - If you just tested or ran computer use, wait 2–3 minutes before trying again. |
| Inputs are ignored when running computer use tool | A breaking change alters the expected input schema (from context: to inputType:) for tools configured before August 2025.Fix: Edit the tool's inputs, add any temporary input, save (this refreshes the schema), delete the temporary input, save again, retest, and publish your agent. |
| When you use hosted browser, you might encounter the following error: "Request to XRM API failed with error: 'Message: user with id does not have ReadAccess right(s) for record with id of entity Flow Machine Group. Consider assigning a role with the level BusinessUnitLevel to the user or team" | Your environment might not have the latest Power Automate extensions solution. To force an update of the solution, as an environment admin:
|
| The test function on computer use tool doesn't work properly. For example, the test ends abruptly with an error: "The computer use tool is not a part of the planned execution sequence." | Test using the agent’s test chat instead, and review the descriptions (instructions) provided to the agent to ensure it has sufficient context to trigger computer use. |