chore(azure.ai.*): point no azd project guidance at azd ai agent init#8374
Merged
trangevi merged 1 commit intoMay 26, 2026
Merged
Conversation
…nit` When `azd ai <extension> context` is run outside an azd project, the extensions print a yellow warning with a suggested next command. Previously they recommended bare `azd init`, which scaffolds a generic azd project but does not wire up the AI agent service target, model deployment selection, or Foundry project endpoint that every `azure.ai.*` extension assumes is in place. `azd ai agent init` is the correct entry point: it goes through the Foundry-aware init pre-flow, picks a sample, and writes an `azure.yaml` that the rest of the `azure.ai.*` family can act on. Update the guidance in four sibling extensions to match what the agents extension actually expects: * azure.ai.connections * azure.ai.projects * azure.ai.routines * azure.ai.skills One-line change per file; no runtime behavior change beyond the printed string. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the “no azd project found” guidance in the azure.ai.* extensions so users are directed to azd ai agent init (which scaffolds an AI-agent-compatible project) instead of azd init (which can create a generic project shape that the azure.ai.* extensions can’t effectively use).
Changes:
- Update the suggested remediation command from
azd init→azd ai agent initin the “no azd project” warning across four extensions. - Keep behavior unchanged aside from the printed suggestion string.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| cli/azd/extensions/azure.ai.skills/internal/cmd/context.go | Update “no azd project” suggestion to azd ai agent init. |
| cli/azd/extensions/azure.ai.routines/internal/cmd/context.go | Update “no azd project” suggestion to azd ai agent init. |
| cli/azd/extensions/azure.ai.projects/internal/cmd/context.go | Update “no azd project” suggestion to azd ai agent init. |
| cli/azd/extensions/azure.ai.connections/internal/cmd/context.go | Update “no azd project” suggestion to azd ai agent init. |
trangevi
approved these changes
May 26, 2026
Member
|
/check-enforcer override |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this fixes
When a developer runs
azd ai connection context,azd ai project context,azd ai routines context, orazd ai skills contextoutside an azd project, the extensions print a warning that suggestsazd init. Following that suggestion gets them a generic azd project that the rest of theazure.ai.*family can't actually operate on -- no agent service target, no Foundry endpoint wiring, no model deployment.This PR points all four extensions at
azd ai agent initinstead, which scaffolds a project the family is actually designed to work with.Why it matters
A first-time
azure.ai.*user is most likely to hit this message exactly when they're trying to set up a new project. The current suggestion sends them down a path that looks like it's working until much later, when they discover the project shape is wrong and they have to start over.Scope
One-line change per file (string only). No runtime behavior change beyond the printed suggestion.
Fixes #8379