Azure Blob ETL to SharePoint
Budget: £3,000 – £5,000 GBP
The task centres on moving content that currently lives in Azure Blob Storage into two destinations—SharePoint Online and a third-party cloud repository that we will finalise together. The source consists of mixed-format files: Word documents, images, CSVs and a few other common types.
I need a lightweight yet robust ETL solution that can:
• automatically detect new or updated blobs,
• perform any required transformations (basic metadata enrichment, naming conventions, optional compression where helpful), and
• deliver the output to the target platforms with solid error handling and retry logic.
An Azure-native approach—Azure Data Factory, Logic Apps, Functions, or a combination—will fit best, but I’m open to other suggestions so long as the pipeline runs securely inside my Azure subscription and can be scheduled or triggered on demand. Clear logging is essential; I should be able to see job status, successes and failures at a glance.
Deliverables
1. Source-controlled code / ARM or Bicep templates to deploy the pipeline.
2. A concise read-me that explains configuration steps and environment variables.
3. A short screen-share hand-off (recorded) showing the pipeline running end-to-end on my tenant.
Acceptance criteria
• All blobs placed in the test container appear in the correct SharePoint document library and the chosen third-party cloud folder with matching metadata.
• Failed transfers are logged and automatically retried up to three times.
• The solution can be re-deployed via template without manual UI steps (aside from authentication secrets).
If this scope aligns with your expertise, let’s discuss the implementation details and timelines.
I need a lightweight yet robust ETL solution that can:
• automatically detect new or updated blobs,
• perform any required transformations (basic metadata enrichment, naming conventions, optional compression where helpful), and
• deliver the output to the target platforms with solid error handling and retry logic.
An Azure-native approach—Azure Data Factory, Logic Apps, Functions, or a combination—will fit best, but I’m open to other suggestions so long as the pipeline runs securely inside my Azure subscription and can be scheduled or triggered on demand. Clear logging is essential; I should be able to see job status, successes and failures at a glance.
Deliverables
1. Source-controlled code / ARM or Bicep templates to deploy the pipeline.
2. A concise read-me that explains configuration steps and environment variables.
3. A short screen-share hand-off (recorded) showing the pipeline running end-to-end on my tenant.
Acceptance criteria
• All blobs placed in the test container appear in the correct SharePoint document library and the chosen third-party cloud folder with matching metadata.
• Failed transfers are logged and automatically retried up to three times.
• The solution can be re-deployed via template without manual UI steps (aside from authentication secrets).
If this scope aligns with your expertise, let’s discuss the implementation details and timelines.
Related categories:
Cloud Computing
C# Programming
Sharepoint
Azure
Microsoft SQL Server
Data Integration
ETL
Automation