---
title: "Use Codex with Azure Storage — connector setup — AgentSky"
description: "Use Codex with the Azure Storage connector on AgentSky. Connect the correct account, run a bounded first task, and verify permissions, cost and results."
url: https://agentsky.dev/agents/codex/connectors/azure_storage
---

# Codex + Azure Storage

Codex runs the task; the Azure Storage connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Codex, asks for Azure Storage access before sending, and keeps both choices in one task draft.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fagents%2Fcodex%2Fconnectors%2Fazure_storage%3Fresume%3D1)

Connect Azure Storage using the Connectors control before sending. Authorization opens separately and your draft stays here.

How the combination works

## Codex plans and executes. Azure Storage supplies authorized app access.

Codex owns the coding-agent loop: it explores the repository, changes files, runs commands, and returns evidence from the cloud workspace.

Massively scalable and secure object storage for cloud-native workloads, archives, data lakes, HPC, and machine learning.

- Codex Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
- Azure Storage connector Supplies the currently exposed operations for the authorized Azure Storage account. It does not promise every feature in the Azure Storage product.
- Permission boundary The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Codex can do.

Setup and first task

## Connect one Azure Storage account and verify one known resource.

The Composer preselects Codex with GPT-6.1 Sol. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.

01

### Open the Codex Composer

The Composer above carries Codex, GPT-6.1 Sol, and Azure Storage. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.

02

### Authorize the intended Azure Storage account

Review the Azure Storage account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

### Run and verify a bounded task

Name one Azure Storage resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in Azure Storage and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

Access, cost and limits

## What to verify before scaling Codex + Azure Storage

Software engineering tasks that benefit from Codex's repository navigation, command execution, and iterative implementation loop.

Establish with the first run

- Codex and GPT-6.1 Sol remain selected after sign-in.
- Azure Storage shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.

Still depends on your setup

- A catalog listing does not guarantee every Azure Storage website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.

Verification and recovery

## Check Azure Storage itself before trusting the result.

Open the same resource in Azure Storage and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

- Connection troubleshooting If Azure Storage access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
- Writes need explicit scope Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
- Re-check current state For decisions or follow-up writes, open the resource in Azure Storage and check its current state. A successful earlier read may already be stale.

## Codex + Azure Storage questions

## Related resources

[CodexReview Codex's supported models, capabilities and browser Composer.](https://agentsky.dev/agents/codex) [Azure Storage connectorReview the application-specific authorization and first-task guide.](https://agentsky.dev/connectors/azure_storage) [Codex + GPT-6.1 SolReview the current default agent and model combination.](https://agentsky.dev/agents/codex/with/gpt-6.1-sol) [PricingReview model, active-computer, tool and connector charges.](https://agentsky.dev/pricing)

## Run a bounded Azure Storage task with Codex.

[Open the Composer](https://agentsky.dev/agents/codex/connectors/azure_storage#composer)

## Frequently asked questions

### Can Codex use Azure Storage on AgentSky?

Yes. Azure Storage is in AgentSky's current managed connector catalog, and Codex can request its exposed operations after you authorize an account. The exact actions still depend on current connector operations and permissions.

### What does Codex do in this combination?

Codex runs the work loop with GPT-6.1 Sol selected by default: it interprets the task, chooses permitted operations, works in its cloud computer, and returns evidence. Azure Storage remains the source application and permission boundary.

### Do I need to paste a Azure Storage API key into the task?

No. This directory covers AgentSky's managed connector flow. Use the Connectors control and complete the provider authorization screen; never paste a password or secret into the Composer. Any provider plan or administrator approval remains separate.

### What can Codex do in Azure Storage?

The agent can use the operations that the current connector exposes for the authorized account. Availability depends on the operation, required inputs, provider scopes, resource sharing and organization policy; the catalog does not promise every Azure Storage feature.

### What happens if I am signed out or my balance is empty?

The shared Composer preserves the task, Codex, GPT-6.1 Sol, and Azure Storage through sign-in and connector authorization. Before dispatch, AgentSky checks the account and balance; if funding is required, it shows the billing path instead of silently changing the selections.

### How much does Codex + Azure Storage cost?

There is no fixed connector-task price. AgentSky records model token usage and active cloud-computer time, plus any paid tools or connector operations. Azure Storage's own subscription, API quota or provider charge is separate; review both products' current limits before a large workflow.

---

Markdown copy of https://agentsky.dev/agents/codex/connectors/azure_storage. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
