For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
      • Snowflake
      • Redshift
      • BigQuery
      • Google Cloud Storage
      • AWS S3 Storage
      • Azure Blob Storage
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • Getting started
  • Requirements
  • Step 1: Create an Azure Storage Account
  • Step 2: Create a container
  • Step 3: Share the relevant information with Solvimon
IntegrationsData Exports

Azure Blob Storage

Was this page helpful?
Previous

Payment Service Providers

Next
Built with

To enable usage of Solvimon’s data seamlessly in your Azure Blob Storage location. This page describes the steps necessary to connect your Azure Blob Storage to Solvimon for data exporting.

Getting started

Requirements

The following access is required for us to set-up a connection from Solvimon to Azure Blob Storage.

  • A Microsoft Azure Cloud Account with privileges to create an Azure Storage Account.
  • A Project in Microsoft Azure portal.

Step 1: Create an Azure Storage Account

This step is optional if you already have a storage account. If that is not the case, you can follow this guide and it will give you the detailed steps on how to create the storage account. The result of this will generate the Azure Blob Storage account name and key, which later will be required.

Step 2: Create a container

The container is the element where the Solvimon data will be uploaded. If you already have a container, there is no need to create a new one, but if that is not the case, you can follow these steps and create the container for the storage account created in the previous step.

Step 3: Share the relevant information with Solvimon

FieldDescription
Account KeyAzure Blob Storage account key.
Account NameAccount’s name of Azure Blob Storage.
Bucket NameAzure Blob Storage container name.
Output Buffer SizeAzure Blob Storage output buffer size, in megabytes. Example: 5
Spill SizeAzure Blob Storage spill size, in megabytes. Example: 500.

Side note: The Output Buffer Size and the Spill Size are already filled in by default, and if you have not made any specific changes, there is no need to provide any information regarding them (it is optional).

As soon as we receive this information we will reach out and work with you directly to set-up the relevant data exports.