You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cli/azd/extensions/azure.ai.agents/AGENTS.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,6 +124,10 @@ Define new codes in `internal/exterrors/codes.go`.
124
124
125
125
A new extension release ships in two PRs:
126
126
127
+
### Provider handoff release
128
+
129
+
The release that removes `microsoft.foundry` from this extension must be coordinated with the provider-bearing `azure.ai.projects` release. Publish both artifacts before updating either registry entry, then update both entries and the `microsoft.foundry` meta-package together.
130
+
127
131
### PR 1 — Version bump
128
132
129
133
Bumps the extension to the new version. Touches only:
Copy file name to clipboardExpand all lines: cli/azd/extensions/azure.ai.agents/README.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,11 +80,7 @@ Details:
80
80
81
81
## Private networking for `host: azure.ai.project`
82
82
83
-
Foundry project services can be provisioned as network-secured, VNet-bound
84
-
accounts by adding a `network:` block to the `host: azure.ai.project` service in
85
-
`azure.yaml`. See [Private networking for `host: azure.ai.project`](docs/private-networking.md)
86
-
for the schema reference, BYO-image requirements, and VNet deployment
87
-
cheatsheet.
83
+
Foundry project services can be provisioned as network-secured, VNet-bound accounts by adding a `network:` block to the `host: azure.ai.project` service in `azure.yaml`. The `azure.ai.projects` extension owns that service and the `microsoft.foundry` provider; this extension still authors the block during agent init. See [Private networking for `host: azure.ai.project`](docs/private-networking.md) for the schema reference, BYO-image requirements, and VNet deployment cheatsheet.
Copy file name to clipboardExpand all lines: cli/azd/extensions/azure.ai.agents/docs/private-networking.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@ A Foundry project service can be provisioned as a **network-secured (VNet-bound)
4
4
5
5
Do **not** place `network:` on `host: azure.ai.agent`. Agent services describe deployable agents and depend on the project through `uses:`; the project service owns account-level provisioning inputs such as `endpoint:`, `deployments:`, and `network:`.
6
6
7
+
The `azure.ai.projects` extension owns the project service and the `microsoft.foundry` provider. `azd ai agent init` continues to author the block and eject its IaC during the staged ownership migration.
8
+
7
9
When `network:` is present, azd always provisions an **account private endpoint** and disables public data-plane access. Dependent stores (Cosmos DB, AI Search, Storage) stay platform-managed.
0 commit comments