docs(destination-azure-blob-storage): update Azure Blob Storage setup docs

[devin-ai-integration]

Documentation Confidence Assessment

Overall Confidence: 2/5 capped: too much code inference

Dimension	Score	Rationale
Code Comprehension	1/5	The connector is Java/Kotlin and depends on Bulk CDK object-storage behavior, so the skill requires a low score despite source review.
API Documentation Quality	5/5	Microsoft Learn provides official Azure Blob Storage docs for auth, SAS, RBAC, permissions, limits, and status.
Change Scope & Risk	3/5	The PR makes moderate setup/auth/reference updates plus a changelog correction, with 48 additions and 35 deletions.
Existing Doc Maturity	3/5	The existing 181-line doc had core sections but setup prerequisites and programmatic config were incomplete.
Connector Sensitivity	3/5	This is a certified GA connector with ql: 300 and sl: 200, so documentation changes warrant human review.
Triggering Context	5/5	Triggered by merged PR #78243, a scoped CDK bump for this connector.

What I Verified vs. What I Inferred

• Verified from code: Connector config field names and required fields; supported destination sync modes; auth fields are mutually exclusive; overwrite cleanup uses object metadata and only deletes old objects after successful stream close; INCOMPLETE stream statuses now cause a non-zero destination result instead of successful cleanup.
• Verified from API docs: Azure Blob Storage supports SAS, account key, and Entra ID authorization; Microsoft recommends Entra ID where possible; SAS tokens grant scoped permissions; Storage Blob Data Contributor grants blob read/write/delete capabilities.
• Inferred: The concise SAS permission list maps to all blob operations Airbyte performs during check and sync; the 2026-05-20 changelog date is based on the merge commit date for PR chore: bump to latest cdk. #78243.

Areas of Concern

• Please review the Azure permission wording, especially the SAS permission summary, because the connector code relies on SDK operations rather than explicit REST endpoint documentation.
• Confidence is capped because this is a Java/Kotlin connector under the playbook rubric.

---

What

Updates the Azure Blob Storage destination docs after reviewing the connector source, Azure documentation, and merged PR #78243.

How

• Corrects setup guidance to say users should create the target container before configuring the destination.
• Clarifies Azure endpoint, auth exclusivity, blob size, and check-connection behavior.
• Adds SAS and Entra ID permission guidance for write/list/read metadata/delete operations.
• Adds a programmatic configuration reference for PyAirbyte, Terraform, and API users.
• Corrects the 1.1.7 changelog date and subject to reflect the merged CDK behavior change.

Review guide

1. docs/integrations/destinations/azure-blob-storage.md lines 28-39: configuration table updates.
2. docs/integrations/destinations/azure-blob-storage.md lines 116-153: setup and reference additions.
3. docs/integrations/destinations/azure-blob-storage.md line 166: changelog correction.

User Impact

Users get clearer setup instructions, more accurate credential permission guidance, a programmatic field reference, and a changelog entry that describes the actual 1.1.7 behavior change.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

---

Note: I am an AI assistant (Devin) and have proposed these documentation updates based on a review of the connector source code and third-party API documentation. Reviewers may merge, modify, or close this PR as they see fit.

Devin session

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.

[github-actions]

Deploy preview for airbyte-docs ready!

Project:	airbyte-docs
Status:	✅  Deploy successful!
Preview URL:	https://airbyte-docs-f6kss7h8y-airbyte-growth.vercel.app
Latest Commit:	3bd5d86

Deployed with vercel-action