- Release Notes
- Overview
- Getting Started
- Marketplace Vendors
- Marketplace Customers
- Publishing Guidelines
- Publishing Guidelines for Ready-to-go Automations
- Publishing Guidelines for Solution Accelerators
- Publishing Guidelines for Integration Service Connectors
- Security & IP Protection
- Other UiPath Listings
- Node-RED
- Setup
- Teams
- Microsoft Teams Scope
- Create Team
- Create Team From Group
- Get Team
- Get Teams
- Channels
- Create Channel
- Delete Channel
- Get Channel
- Get Channels
- Update Channel
- Chats
- Get Chat
- Get Chats
- Get Chat Members
- Messages
- Get Message
- Get Messages
- Get Message Replies
- Reply To Message
- Send Message
- Events
- Create Event
- Delete Event
- Get Event
- Get Events
- Users
- Get User Presence
- How It Works
- Technical References
- Get Started
- About
- Setup
- Technical References
- Azure Form Recognizer Scope
- Activities
- Analyze Form
- Analyze Form Async
- Get Analyze Form Result
- Analyze Receipt
- Analyze Receipt Async
- Get Analyze Receipt Result
- Analyze Layout
- Analyze Layout Async
- Get Analyze Layout Result
- Train Model
- Get Models
- Get Model Keys
- Get Model Info
- Delete Model
- Connectors
- How to Create Activities
- Build Your Integration
How It Works
To enable the outbound automation between UiPath and Azure Form Recognizer, the activities establish an authenticated connection to the Form Recognizer API via the Azure Form Recognizer Scope activity.
After the connection is established, the other Azure Form Recognizer activities send requests to the applicable Form Recognizer API operation(s) using the parameters you enter in the activities' input properties. If the requests are successful, the activities return the response values to the output property variables.
This is where we need your help.
Before the scope activity can be used to establish a connection, you must complete the steps outlined in the Setup guide. After you complete the Setup steps, you can begin building your automation projects
The authentication method used by the Azure Form Recognizer Scope activity is different when compared to other Microsoft integrations (e.g., Teams and ).
Currently, the Azure Form Recognizer activities authenticate with a single-service subscription key only. Authentication using an InteractiveToken or IntegratedWindowsAuthentication is not supported.