How azure-samples/functions-e2e-blob-pdf-to-text works
This Azure Functions sample turns PDFs uploaded to Blob Storage into text files. An Event Grid-based blob trigger invokes the processor, which loads PDF pages, extracts and joins their text, then returns the result through a Blob Storage output binding. The README also documents the provisioned Flex Consumption app, managed-identity access, and optional VNet isolation. The runtime relationship is visible in the function source; infrastructure relationships below are documented in the README, not traced through sampled Bicep files.
Main entry points: processor.bicep Flex Consumption app · PDFProcessor.js PDF text extraction · storage-Access.bicep Storage network access · vnet.bicep Virtual network
Components 11
PDF processing
- Unprocessed PDFs
- Event Grid blob trigger
src/src/functions/PDFProcessor.js - PDF text extraction
src/src/functions/PDFProcessor.js - PDF.js
src/src/functions/PDFProcessor.js - Processed text
Azure hosting and security
- Flex Consumption app
infra/app/processor.bicep - Managed identity
infra/app/processor.bicep - Storage network access
infra/app/storage-Access.bicep - Virtual network
infra/app/vnet.bicep - Application monitoring
infra/core/monitor/monitoring.bicep
Other components
- PDF uploader
Connections 10
- PDF uploader → Unprocessed PDFs: uploads PDFs
README.md - Unprocessed PDFs → Event Grid blob trigger: triggers on upload
src/src/functions/PDFProcessor.js - Event Grid blob trigger → PDF text extraction: invokes handler
src/src/functions/PDFProcessor.js - PDF text extraction → PDF.js: extracts pages
src/src/functions/PDFProcessor.js - PDF text extraction → Processed text: writes extracted text
src/src/functions/PDFProcessor.js - Flex Consumption app → Event Grid blob trigger: hosts
- Flex Consumption app → Managed identity: uses identity
- Flex Consumption app → Storage network access: uses secure access
- Storage network access → Virtual network: uses integration
- Flex Consumption app → Application monitoring: emits telemetry