To achieve a fully automated .bacpac
export via Azure Data Factory (ADF) without any manual steps, and ensure it works entirely over private endpoints, here's a recommended approach:
Since ADF doesn't have a built-in activity to export .bacpac
files, we can leverage either of the following:
Azure Function Activity
Create an Azure Function that calls the Azure SQL Export REST API to export the .bacpac
to Azure Blob Storage.
Integrate the Function App with your VNet to route via private endpoint.
Trigger this function using an Azure Function Activity in ADF.
Web Activity (Direct REST API Call)
Use ADF’s Web activity to call the Azure SQL Export REST API directly.
This requires configuring proper authentication (e.g., managed identity).
Ensure the ADF Integration Runtime is running inside a Managed VNet or a Self-hosted IR with access to your private endpoints.
Private Endpoint Compatibility
Both methods above can work via private endpoints if:
Your SQL Server, Blob Storage, and (if used) Function App are configured with private endpoints.
Your ADF Integration Runtime is within the same VNet or peered network.
No Manual Work
Once the setup is done:
- The ADF pipeline can be triggered manually, on schedule, or by event.
- The
.bacpac
will automatically be exported and saved to blob storage — no manual intervention needed.
For additional information, please refer the following thread:
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Thank you.