1.28.1 (2026-07-22)

Bugs Fixed

• [#9143] Fix azd down --no-prompt hanging in CI/CD for Terraform-based projects by auto-approving the destroy when running non-interactively, and fix azd down --force failing with a backend initialization error on a fresh agent.
• [#9161] Fix azd extension install intermittently failing on Windows with an "Access is denied" error when replacing an extension executable held by a transient file lock.

Other Changes

• [#9261] Stop showing the automatic azd tool first-run install prompt and periodic update notifications. Explicit azd tool commands are unchanged.
• [#9245] Update the bundled GitHub CLI to v2.96.0.
• [#9091] Emit the infra.provider telemetry attribute on provision, up, and down so provisioning runs can be segmented by infrastructure provider.
• [#9167] Recognize azd invocations from Microsoft Foundry Skill in the execution.environment telemetry field.

1.0.0-beta.4 (2026-07-23)

Features Added

• [#9229] azd ai toolbox now supports the WorkIQ (work_iq_preview), FabricIQ (fabric_iq_preview), and toolbox-search (toolbox_search_preview) preview tools, and azd ai toolbox connection list now surfaces any tool that exposes a project connection.

Bugs Fixed

• [#9220] Fix azd ai toolbox create --project-endpoint --from-file failing when run outside an azd project; the best-effort environment sync now skips silently when no azure.yaml is present instead of failing the command.

1.0.0-beta.3 (2026-07-23)

Features Added

• [#9133] The azure.ai.projects extension now owns Foundry project provisioning through the microsoft.foundry provider, including updating deployments and connections on existing projects (set AZURE_AI_PROJECT_ID to the project ARM resource ID), using the customer VNet region for private endpoints, and blocking automatic Azure Container Registry creation for private-network projects. Release it together with azure.ai.agents, since mixing versions can cause both extensions to register the same provider.

Bugs Fixed

• [#9149] Fix Foundry project synthesis and provisioning not consistently resolving configuration declared inline in azure.yaml, via the deprecated config: block, or through local $ref files.

1.0.0-beta.7 (2026-07-23)

Features Added

• [#9009] azd ai agent init now offers invocations_ws as a selectable agent protocol (including for bring-your-own-image --image init), while responses remains the default.
• [#9204] Add eastus, italynorth, uaenorth, southcentralus, switzerlandwest, ukwest, westeurope, westcentralus, and japanwest to the list of supported hosted agent regions.

Bugs Fixed

• [#9149] Fix azd ai agent run and azd deploy not consistently resolving agent definitions declared inline in azure.yaml, via the deprecated config: block, or through local $ref files.
• [#9171] Fix modern Python agent projects (using pyproject.toml) being incorrectly routed to container deployment and prompted for an unnecessary Azure Container Registry during code deploy.
• [#9205] Fix azd deploy failing with HTTP 403 when the signed-in user's role (for example a subscription-inherited Owner or Azure AI Developer) lacked Cognitive Services data-plane access; the deploy-time RBAC check now recognizes only roles that grant it and auto-assigns the Foundry User role when needed.
• [#9225] Fix azd ai agent init accepting stale Azure Container Registry connections from an existing Foundry project; init now validates discovered registries against ARM and clears missing ones instead of deferring the failure until publish.
• [#9254] Fix azd ai agent doctor failing valid projects whose agent definition is declared inline in azure.yaml; the definition check now uses the same resolver as run and deploy.
• [#9264] Fix azd ai agent doctor reporting a false pass for an inline or $ref agent definition with an unsupported kind; resolved non-hosted definitions are now validated, while valid workflow definitions still pass.

Other Changes

• [#9133] Foundry project provisioning has moved to the azure.ai.projects extension. Update azure.ai.agents and azure.ai.projects together, since mixing versions can cause both extensions to register the same microsoft.foundry provider.

[Missing change log entry]

1.0.0-beta.3 (2026-07-16)

Features Added

• [#9024] azd deploy for host: azure.ai.toolbox services now supports an endpoint: field in azure.yaml to reference an existing toolbox by its MCP endpoint URL, skipping version creation. This enables reusing a toolbox managed outside the current project.

Bugs Fixed

• [#9013] Fix azd ai toolbox skill add/remove and connection add/remove branching from the toolbox's default version instead of its latest, causing sequential mutations to silently drop earlier changes. Add a --from-version flag to override the branch source.

Other Changes

• [#9103] Pin internal azd module dependency to released version.

1.0.0-beta.3 (2026-07-16)

Other Changes

• [#9103] Pin internal azd module dependency to released version.

1.0.0-beta.3 (2026-07-16)

Breaking Changes

• [#9046] azd deploy for host: azure.ai.connection services is now a no-op; connections are created at provision time by the microsoft.foundry provider via azd provision. This removes the redundant ARM write on every azd deploy.

Other Changes

• [#9103] Pin internal azd module dependency to released version.

1.0.0-beta.6 (2026-07-16)

Features Added

• [#9046] azd provision now creates Foundry connections declared as host: azure.ai.connection services in azure.yaml at provision time via the microsoft.foundry synthesizer, for both greenfield and brownfield projects. Connection category, target, authentication type, credentials, and metadata are all supported. azd deploy for host: azure.ai.connection services is now a no-op; provision is the single source of truth.
• [#9107] Add centralus region to the list of supported hosted agent regions.
• [#8942] azd deploy can now carry over the current hosted-agent session across deploys. When AZD_AGENT_RESUME_SESSION_ON_DEPLOY is set to a truthy value, the session is stopped before deploy and re-pointed at the newly deployed version so the next invocation resumes with its /home/session volume intact instead of minting a fresh session.

Bugs Fixed

• [#9114] Fix azd ai agent invoke failing with "agent name is required" on brownfield projects where the hosted agent name is written inline in the azure.ai.agent service config rather than emitted as a deployed environment output. The agent name is now seeded from the inline/config definition, with the deployed environment variable retaining precedence.
• [#9007] Add a preflight validation check that detects an immutable resource-group region conflict before provisioning. When the target resource group already exists in a different region than AZURE_LOCATION, the check surfaces the mismatch during azd's validation phase with clear remediation guidance instead of a slow deploy-time ARM InvalidResourceGroupLocation error.

Other Changes

• [#9112] Terraform infrastructure eject now synthesizes azure.ai.connection services into Foundry project connection resources, preserving their category, target, authentication type, credentials, and metadata.
• [#9049] Switch the invocations_ws agent endpoint from the preview dispatcher form to the GA path-based route. azd deploy now registers AGENT_{KEY}_INVOCATIONS_WS_ENDPOINT (and azd ai agent show displays Endpoint (invocations_ws)) as wss://<account>.services.ai.azure.com/api/projects/<project>/agents/<agent>/endpoint/protocols/invocations_ws?api-version=v1, carrying the project and agent as path segments to mirror the HTTP invocations route. The previous form embedded them as project_name/agent_name query parameters on a single literal /api/projects/agents/... path.
• [#9103] Pin internal azd module dependency to released version.

0.7.2 (2026-07-16)

• Simple test release of extension, with no changes.