Home | Connectors | Azure Blob Storage | Azure Blob Storage - OpenText Core Capture Services Integration and Automation
Data flow: Azure Blob Storage ? OpenText Core Capture Services
Organizations can store incoming PDFs, scans, and image files in Azure Blob Storage and automatically feed them into OpenText Core Capture Services for classification and data extraction. This is useful for large-scale document intake scenarios such as invoices, claims, HR forms, and customer correspondence.
Business value: Reduces manual upload effort, supports high-volume processing, and creates a scalable intake layer for shared business services.
Data flow: Azure Blob Storage ? OpenText Core Capture Services ? downstream workflow systems
Mailroom teams can deposit scanned mail into Azure Blob Storage from multiple locations, then OpenText Core Capture Services can classify the documents by type, extract key fields, and route them to the correct business process. This supports centralized processing for organizations with remote offices or outsourced scanning operations.
Business value: Speeds up mail distribution, improves routing accuracy, and reduces delays in handling time-sensitive correspondence.
Data flow: OpenText Core Capture Services ? Azure Blob Storage
After invoices are captured and key data is extracted, the original invoice images and processed output can be archived in Azure Blob Storage for long-term retention, audit support, and easy retrieval by finance teams. This creates a low-cost repository for invoice records while keeping the capture platform focused on processing.
Business value: Lowers storage costs, supports audit readiness, and simplifies access to invoice history for finance and compliance teams.
Data flow: Azure Blob Storage ? OpenText Core Capture Services ? CRM or onboarding workflow
Customer-submitted documents such as IDs, proof of address, tax forms, and signed agreements can be uploaded to Azure Blob Storage through portals or service channels. OpenText Core Capture Services can then classify and extract the required information to accelerate onboarding and reduce manual review.
Business value: Shortens onboarding cycle times, improves data accuracy, and helps customer service and compliance teams work from the same document set.
Data flow: OpenText Core Capture Services ? Azure Blob Storage
Documents that fail classification or require human review can be written back to Azure Blob Storage as an exception queue. Operations teams can review, correct, and resubmit these files for capture without losing the original document or creating duplicate intake channels.
Business value: Improves processing resilience, supports controlled exception management, and reduces the risk of lost or unprocessed documents.
Data flow: OpenText Core Capture Services ? Azure Blob Storage
Once documents are captured and indexed, the original files and extracted metadata can be stored in Azure Blob Storage for retention, legal hold, or downstream analytics. This is especially valuable for regulated industries that need to preserve source documents after operational processing is complete.
Business value: Supports compliance requirements, enables cost-effective archival, and preserves a complete record of processed content.
Data flow: Bi-directional
Azure Blob Storage can serve as the shared repository for documents collected from multiple channels, while OpenText Core Capture Services processes those documents and writes back classification results, extracted fields, or processing status. Finance, operations, customer service, and compliance teams can all access the same document source and status information.
Business value: Improves collaboration across departments, creates a single source of truth for document handling, and reduces duplicate storage or manual handoffs.