Issue: Browser Automation Tool Blocked by Human Verification Challenges #138
-
📄 Description:I'm currently working with the Browser Automation Tool within the Azure AI Foundry Agent Service and encountering persistent access issues when attempting to retrieve publicly available web content. 🔍 Problem Summary:
🧭 Current State:
🛠️ What I’ve Tried:
🔁 To Reproduce:
✅ Expected Behaviour:
❗ Request for Help:Has anyone encountered similar issues with automated browser workflows being blocked by human verification or reCAPTCHA challenges? Are there recommended strategies or configurations within Azure AI Foundry to:
Any guidance, workaround, or shared experience would be greatly appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Thanks for the feedback @saadbhaldar1212 and discussion so far. Here's a summary to help clarify how and when to use browser automation effectively: ✅ Recommended Use Cases
Scenario Fit: For broader or more complex tasks, consider alternatives like Grounding with Bing, which may offer better flexibility and compliance. 📌 Given this conversation we will add more detail to our docs and FAQ on this topic - thank you for sharing |
Beta Was this translation helpful? Give feedback.
Thanks for the feedback @saadbhaldar1212 and discussion so far. Here's a summary to help clarify how and when to use browser automation effectively:
✅ Recommended Use Cases
Browser automation (CUA) works best for simple, structured interactions—like filling out and submitting forms—where the model can reliably navigate the UI.
Website Restrictions: If a site blocks crawling or scraping, browser automation tools will not work. This is a limitation of the site’s terms and technical controls, not the automation tool itself.
Scenario Fit: For broader or more complex tasks, consider alternatives like Grounding with Bing, which may offer better flexibility and compliance.
📌 Given…