- 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
Azure Form Recognizer Scope
Each Azure Form Recognizer activity calls a Form Recognizer API. To successfully call the API, the activities must include an authentication header in the request. To include an authentication header, the activities rely on the Azure Form Recognizer Scope activity to provide a subscription key value.
Using your subscription key (Subscription Key) and resource endpoint (Endpoint), the Azure Form Recognizer Scope activity facilitates the authenticated connection to your Form Recognizer Azure resource.
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.
The following steps and message sequence diagram is an example of how the activity works from design time (i.e., the activity dependencies and input/output properties) to run time.
- Complete the Setup steps.
- Add the Azure Form Recognizer Scope activity to your project.
-
Enter values for the Authentication and Input properties.
The values for the following properties are specified when adding this activity to your project in UiPath Studio.
DisplayName
The display name of the activity.
Attributes |
Details |
---|---|
Type |
|
Required |
Yes |
Default value |
Azure Form Recognizer Scope |
Allowed values |
Enter a
String or
String variable.
|
Notes |
N/A |
Subscription Key
SecureString
used to authenticate requests to the Form
Recognizer API.
Attributes |
Details |
---|---|
Type |
|
Required |
Yes |
Default value |
Empty |
Allowed values |
Enter a
SecureString
variable.
|
Notes |
The Subscription Key gets generated when you create a Form Recognizer Azure resource. For more information, see the Create a Form Recognizer Azure resource section of the Setup guide. |
Endpoint
The API endpoint of your Form Recognizer resource.
Attributes |
Details |
---|---|
Type |
|
Required |
Yes |
Default value |
Empty |
Allowed values |
Enter a
String or
String variable.
|
Notes |
The Endpoint gets generated when you create a Form Recognizer Azure resource. For more information, see the Create a Form Recognizer Azure resource section of the Setup guide. |
The following image shows an example of the activity dependency relationship and input/output property values.
For step-by-step instructions and examples, see the Quickstart guide.