Skip to content

Add Azure Blob Storage cloud provider guide - #1275

Open
justincrowe-hub wants to merge 1 commit into
mainfrom
justin/azure-blob-storage-guide
Open

justincrowe-hub wants to merge 1 commit into
mainfrom
justin/azure-blob-storage-guide

Conversation

@justincrowe-hub

Copy link
Copy Markdown

Description

  • New page: providers/cloud/azure.mdx documents Azure Blob Storage as a recording storage destination, following the S3 and GCP guides. It lists the dashboard fields (Region, Connection String, Container Name, Path, Fallback Index).
  • Behavior notes: saving the credential uploads a test file to confirm the connection, and the container is created if it does not exist.
  • Navigation: added the page to the Cloud Providers section in docs.yml, and linked it from customization/provider-keys.mdx and security-and-privacy/data-flow.mdx. The data flow page already listed Azure as supported but had no guide to link to.

Field names and behavior checked against VapiAI/vapi @ 931b02a (AzureBlobStorageCard.tsx, azureFunctions.ts).

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work
  • Confirm Azure Blob Storage appears under Providers > Cloud Providers

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@lightsage-app

lightsage-app Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Lightsage docs evals

Lightsage could not queue docs evals for this PR.

Docs URL: https://vapi-preview-01a0f859-fb29-74f4-8561-80d61cb5623f.docs.buildwithfern.com
Commit: c966e64
Reason: No custom evals are selected for GitHub PR evals. Open Lightsage > Custom Evals and enable the GitHub checkbox for at least one custom eval.

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant