Overview
Microsoft Azure is a cloud computing platform offering storage, compute, identity, and data services. Organizations use Azure Blob Storage to securely store, manage, and distribute unstructured data at scale.
The Alchemer integration with Microsoft Azure supports automated file creation per survey response. The Alchemer → Azure integration allows surveys to generate CSV, TSV, or JSON files and push them directly into an Azure Blob Storage container for downstream processing, workflows, and system automation.
Common uses for the Alchemer Microsoft Azure integration
- Capture survey responses as files for ingestion into Azure Blob Storage
- Trigger Azure Functions or Logic Apps via new file events
- Feed data into Data Lake / Synapse / Databricks pipelines
- Support audit logging and long‑term archiving strategies
- Enable distributed teams to consume results without platform access
- Automate delivery of raw response data to secure cloud storage
What can the Alchemer Microsoft Azure integration do?
You will need
- Microsoft Azure Storage Account and Container with appropriate access permissions
- Azure Shared Access Signature (SAS token). More details in the authentication how-to guide.
- An Alchemer plan that includes integrations and the Integration Manager permission enabled.
- Contact us if you are unsure if your plan includes integrations.
Setup Alchemer Microsoft Azure integration in surveys
Microsoft Azure | Push response to Azure Blob Storage
You will need:
- Azure Blob Storage authentication (SAS token or account key). More details in the authentication how-to guide.
- The Azure container name where files will be created
Configure the action
- Open your survey in Survey Builder.
- Select Add New: Action.
- In the Add Action modal, scroll to the Integrations section.
- Select Microsoft Azure.
- Select Azure | Push response to Azure Blob Storage.
- Azure | Authentication: Select an existing authentication or create a new authentication using your SAS URL.
- Azure | Select file type: Select your desired file type to be uploaded into your Azure Blob storage container.
- Azure | Custom file name: By default, the file name is generated using survey ID session ID, and epoch timestamp. You can optionally provide a custom file name from your survey. Keep this unique to identify your files.
- Azure | Get data back: Select the metadata fields you want returned to the survey.
- Save the action.
Status codes
- 200: Successfully pushed file to Azure Blob container
- 400: The external integration returned an error
Testing and Troubleshooting
Testing and Validation
How to test
- Submit a survey response that triggers the file creation action.
- Confirm the file appears in your Azure Blob Storage container.
- Validate that the file format (CSV/TSV/JSON) and included fields match expectations.
How to verify results
- Check the newly created file in Azure Blob Storage.
- Open the file to confirm content accuracy.
Monitoring Integration Activity
Where to find logs
- Go to Results → Individual Responses.
- Select the response you want to inspect.
- Open the Action Log tab.
What logs display
Success or failure status
- Timestamp
- Input and output values
- Returned status codes from Azure
Troubleshooting
Authentication issues
- Incorrect or expired SAS token
- Missing permissions on the container (e.g., write access)
Container issues
- Incorrect container name
- Container does not exist in the target storage account
Azure API errors
- SAS token scope limitations
- Storage account firewall restrictions
FAQs
What permissions do I need?
Integration Manager in Alchemer and write permissions for Azure Blob Storage (via SAS).
Integration Manager in Alchemer and write permissions for Azure Blob Storage (via SAS).
When does the integration run?
In real time when a survey response is submitted.
In real time when a survey response is submitted.
Can I use multiple Microsoft Azure actions in one survey?
Yes. Each response can write multiple files to Azure if configured.
Yes. Each response can write multiple files to Azure if configured.
Why isn’t my file being created?
Check the Action Log for authentication failures, container issues, or Azure API errors.
Check the Action Log for authentication failures, container issues, or Azure API errors.
What if I need additional functionality?
Contact Alchemer Support for enhancement requests.
Contact Alchemer Support for enhancement requests.
