Skip to content

docs: sync and convert from upstream #997

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
foundry-devx-agent merged 1 commit into from
Sep 19, 2026
Merged

docs: sync and convert from upstream #997

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions docs/agents/agent-applications.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ For applications, this endpoint is exposed at:

`https://{accountName}.services.ai.azure.com/api/projects/{projectName}/applications/{applicationName}/protocols/openai`

The OpenAI-compatible API exposed through applications has been modified to ensure users' conversations remain private. This restriction is temporary and will be removed once we support end-user isolation. As a result, the API is more limited than the OpenAI API served by the project endpoint. Specifically:
The OpenAI-compatible API that applications expose is modified to keep your conversations private. This restriction is temporary and is removed when end-user isolation is supported. As a result, the API is more limited than the OpenAI API served by the project endpoint. Specifically:

- Only the stateless Responses API (`POST /responses`) is supported.
- Other APIs including `/conversations`, `/files`, `/vector_stores`, and `/containers` are inaccessible.
Expand Down Expand Up @@ -169,13 +169,20 @@ Agent Applications are Azure resources. Use the latest API version available for
- `project_name`: The Foundry project name.
- `application_name` and `deployment_name`: Choose names for the Agent Application and deployment you want to create.

3. Choose an `api-version`.
3. Choose an `api-version`. To list the versions your subscription supports, run:

#### 1. Create agent application.
```azurecli
az provider show --namespace Microsoft.CognitiveServices --query "resourceTypes[?resourceType=='accounts/projects/applications'].apiVersions[]" -o tsv
```

#### 1. Create agent application

For a full property reference and an infrastructure-as-code (Bicep) example for Agent Applications, see the Azure Resource Manager template reference for [Microsoft.CognitiveServices/accounts/projects/applications](https://learn.microsoft.com/azure/templates/microsoft.cognitiveservices/accounts/projects/applications).

**Required field**: Set the `agentName` field to the name of the agent you want to publish.
**Required fields**:

- `agentName`: The name of the agent you want to publish.
- `displayName`: A friendly name for the application. Omitting it fails with an opaque `400 SystemError`.

The following example shows only the minimum required fields. By default `authorizationPolicy` is set to **Default (Azure RBAC)** and `trafficRoutingPolicy` routes all traffic to the first deployment.

Expand All @@ -186,6 +193,7 @@ Content-Type: application/json

{
"properties":{
"displayName": "Publishing Agent",
"agents": [{"agentName": "Publishing Agent"}]
}
}
Expand Down Expand Up @@ -403,14 +411,14 @@ from azure.identity import DefaultAzureCredential, get_bearer_token_provider
BASE_URL = "https://<foundry-resource-name>.services.ai.azure.com/api/projects/<project-name>/applications/<app-name>/protocols/openai"

# Create OpenAI client authenticated with Azure credentials
openai = OpenAI(
client = OpenAI(
api_key=get_bearer_token_provider(DefaultAzureCredential(), "https://ai.azure.com/.default"),
base_url=BASE_URL,
default_query={"api-version": "2025-11-15-preview"}
)

# Send a request to the published agent
response = openai.responses.create(
response = client.responses.create(
input="Write a haiku",
)
print(f"Response output: {response.output_text}")
Expand Down
43 changes: 19 additions & 24 deletions docs/agents/quickstart-hosted-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,18 +16,14 @@ Before you begin, you need:

* An Azure subscription. If you don't have one, [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
* If you have an existing Foundry project, you need `Foundry Project Manager` at project scope. If you need to create a new Foundry project, you need the `Owner` role at resource group scope. For the full role matrix, see [Hosted agent permissions reference](/agents/hosted-agent-permissions).

<ZonePivot group="azd__canvas__csharp__foundry-skills__python__vscode" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} defaultValue="azd" />

<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="azd" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* [Azure Developer CLI (azd) 1.27.1 or later](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd).
* The `azd microsoft.foundry` extension. Install and verify the extension after `azd` is installed:

```azurecli
azd ext install microsoft.foundry
```

* An authenticated `azd` session. Sign in after you install the extension:
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure Developer CLI (`azd >= 1.27.1`) and the Foundry extensions used in this quickstart.
* An authenticated `azd` session:

```azurecli
azd auth login
Expand All @@ -37,8 +33,9 @@ Before you begin, you need:
<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="python" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* [Python 3.13 or later](https://www.python.org/downloads/).

* [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli) installed and authenticated:
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure CLI (`az`).
* An authenticated Azure CLI session:

```bash
az login
Expand All @@ -60,7 +57,9 @@ Before you begin, you need:
<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="csharp" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* [.NET 10 SDK](https://dotnet.microsoft.com/download/dotnet/10.0).
* [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli) installed and authenticated:
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure CLI (`az`).
* An authenticated Azure CLI session:

```azurecli
az login
Expand Down Expand Up @@ -89,29 +88,25 @@ of `Azure.AI.Projects`. The stable 2.0.x package doesn't include these APIs.
<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="vscode" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* [Visual Studio Code](https://code.visualstudio.com/).
* [Microsoft Foundry Toolkit for Visual Studio Code](https://aka.ms/foundrytk).
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure Developer CLI (`azd`) and the Microsoft Foundry Toolkit for VS Code extension used in this quickstart.

</ZoneContent>
<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="canvas" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* [GitHub Copilot App](https://github.com/features/copilot).
* The Microsoft Foundry Canvas extension. To install it, in the GitHub Copilot App open **Settings** > **Plugins**, search for `microsoft-foundry`, and select **Install**. For more information, see [What is Microsoft Foundry Canvas?](../concepts/foundry-canvas#install-microsoft-foundry-canvas)
* [Azure Developer CLI (azd) 1.27.1 or later](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd). The canvas uses `azd` to test and deploy the agent.
* The `azd microsoft.foundry` extension. Install and verify the extension after `azd` is installed:

```azurecli
azd ext install microsoft.foundry
```
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure Developer CLI (`azd >= 1.27.1`) and the Microsoft Foundry Canvas for GitHub Copilot App used in this quickstart.

</ZoneContent>
<ZoneContent group="azd__canvas__csharp__foundry-skills__python__vscode" value="foundry-skills" options={[{"id": "azd", "title": "Azure Developer CLI"}, {"id": "python", "title": "Python"}, {"id": "csharp", "title": "C#"}, {"id": "vscode", "title": "VS Code"}, {"id": "canvas", "title": "Canvas"}, {"id": "foundry-skills", "title": "Foundry Skills"}]} values={["azd", "python", "csharp", "vscode", "canvas", "foundry-skills"]} defaultValue="azd">

* A coding agent host with the
[Microsoft Foundry Skill](/get-started/use-microsoft-foundry-skill)
installed.
* [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli) and
[Azure Developer CLI (azd)](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd)
installed and authenticated:
[Microsoft Foundry Skill](/get-started/use-microsoft-foundry-skill).
* [Foundry Dev Pack](/developer-tools-and-integrations/install-cli-sdk#install-foundry-devpack).
The Foundry Dev Pack installs Azure CLI (`az`), Azure Developer CLI (`azd`),
and the Foundry Skill used in this quickstart.
* Authenticated Azure CLI and `azd` sessions:

```bash
az login
Expand Down
4 changes: 2 additions & 2 deletions docs/models/model-retirement-schedule.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,8 @@ This section lists the retirement lifecycle for Foundry Models sold by Azure.
| gpt-realtime | 2025-08-28 | GA | 2027-03-02 | — |
| gpt-realtime-1.5 | 2026-02-23 | GA | 2027-08-24 | — |
| gpt-realtime-2 | 2026-05-06 | Preview | 2026-08-31 | — |
| gpt-realtime-2.1 | 2026-07-07 | Preview | 2027-06-25 | — |
| gpt-realtime-2.1-mini | 2026-07-07 | Preview | 2027-06-25 | — |
| gpt-realtime-2.1 | 2026-07-07 | GA | 2027-06-25 | — |
| gpt-realtime-2.1-mini | 2026-07-07 | GA | 2027-06-25 | — |
| gpt-realtime-mini | 2025-10-06 | GA | 2027-04-06 | — |
| gpt-realtime-mini | 2025-12-15 | GA | 2027-06-15 | — |
| gpt-realtime-mini | 2025-10-06 | GA | 2026-09-21 | — |
Expand Down
35 changes: 25 additions & 10 deletions docs/observability/concept-notification-center.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,28 +3,38 @@ title: "Microsoft Foundry Notification Center overview"
description: "The Microsoft Foundry Notification Center surfaces security, policy, and performance alerts in one place. Explore key features to keep your AI solutions reliable."
---

Microsoft Foundry Notification Center centralizes all important observability alerts and notifications for your AI agents, models, and projects. Previously, developers had to manually monitor multiple siloed systems and configure Azure Monitor alerts to catch agent issues - an error-prone and time-consuming process. Now, the Notification Center automatically aggregates critical signals into a single in-app feed, so you can see and address problems directly within the Foundry portal, without complex setup.
Microsoft Foundry Notification Center centralizes all important observability alerts and notifications for your AI agents, models, and projects. Previously, developers had to manually monitor multiple siloed systems and configure Azure Monitor alerts to catch agent issues. This approach was error-prone and time-consuming. Now, the Notification Center automatically aggregates critical signals into a single in-app feed, so you can see and address problems directly within the Foundry portal, without complex setup.

By delivering timely notifications in the same UI where you manage your agents, the Notification Center helps you stay on top of issues in real time and maintain your AI solutions' reliability and compliance.

## When to use the Notification Center

Use the Notification Center when you want a single in-portal feed for critical Foundry signals, without configuring and monitoring multiple Azure Monitor alert rules yourself. For example:

- Catch high-severity Microsoft Defender for Cloud security alerts on your agents or infrastructure.
- Track Azure Policy or guardrail compliance issues across your projects.
- Know when long-running evaluation or training jobs finish or fail.

## Prerequisites

- An active Microsoft Foundry project. To create one, see [Create a project](../how-to/create-projects).
- Access to the [Foundry portal](https://ai.azure.com).

## Delivery channels

Currently, the Foundry web portal (in-app) delivers notifications. A small badge on the bell icon indicates new unread items whenever they arrive.
Currently, the Foundry web portal (in-app) delivers notifications. A small badge on the bell icon indicates new unread items whenever they arrive.

## Key capabilities and alert coverage

The Foundry Notification Center provides a comprehensive alerting experience integrated into the Foundry web portal. Key capabilities include:

### Centralized notifications panel
A bell icon in the Foundry portal's header opens the Notification Center panel. This panel shows recent notifications (unread and read) with timestamps (for example, "3m ago") and short descriptions, giving you an immediate overview of new events. You can click any item to see details or navigate to the relevant resource for resolution. A **Dismiss All** action is available to mark all notifications as read (with a confirmation prompt) for quick cleanup.

### "View all" notifications page
For deeper review, a dedicated expanded view page lists all notifications in a table format, including older or previously-read items. Unlike the compact bell panel, this page is designed for detailed review, filtering, and auditing of notifications. You can sort or filter notifications by criteria like type, project, or severity (with more filtering options on the way). The **View All** page ensures you can explore your entire notification history across all categories of events, not just the latest alerts.
A bell icon in the Foundry portal's header opens the Notification Center panel. This panel shows recent notifications (unread and read) with timestamps (for example, "3m ago") and short descriptions, giving you an immediate overview of new events. You can select any item to see details or navigate to the relevant resource for resolution. A **Dismiss all** action is available to mark all notifications as read (with a confirmation prompt) for quick cleanup.

### View all notifications page

For deeper review, a dedicated expanded view page lists all notifications in a table format, including older or previously read items. Unlike the compact bell panel, this page is designed for detailed review, filtering, and auditing of notifications. You can sort or filter notifications by criteria like type, project, or severity (with more filtering options on the way). The **View all** page ensures you can explore your entire notification history across all categories of events, not just the latest alerts.

### Alert types covered
The Notification Center aggregates multiple categories of key events from across the Foundry environment. It supports four main types of notifications:
Expand All @@ -43,15 +53,20 @@ These steps require portal access. For RBAC role requirements, see [Role-based a

</Note>

**Accessing notifications**: In the Foundry portal, select the Notification Center (bell) icon to open the notifications panel. The panel displays a scrollable list of your most recent notifications, with each entry showing a concise description and an icon or color indicating its category or importance. New (unread) notifications are highlighted.
### Access notifications

In the Foundry portal, select the Notification Center (bell) icon to open the notifications panel. The panel displays a scrollable list of your most recent notifications, with each entry showing a concise description and an icon or color that indicates its category or importance. New (unread) notifications are highlighted.

### View notification details

**Viewing details**: To learn more about a notification, select it in the panel. Selecting a notification opens a detailed view or relevant page:
To learn more about a notification, select it in the panel. Selecting a notification opens a detailed view or relevant page:

For agent evaluation alerts or run completions, selecting an item might open the Foundry **Operate** page or evaluation results for the specific agent or run, where you can inspect metrics and logs around the time of the alert.
- For agent evaluation alerts or run completions, selecting an item might open the Foundry **Operate** page or evaluation results for the specific agent or run, where you can inspect metrics and logs around the time of the alert.
- For security or policy alerts, selecting a notification directs you to the appropriate details. For example, a deep link to the Azure portal security center or policy compliance page so you can investigate and fix the issue.

For security or policy alerts, selecting a notification directs you to the appropriate details. For example, a deep link to the Azure portal's security center or policy compliance page so you can investigate and remediate the issue.
### Mark notifications as read

**Marking notifications as read**: After you review an alert, the panel marks it as read automatically (the visual highlight disappears). In the notifications panel, you can use the **Dismiss All** button to mark all current notifications as read at once.
After you review an alert, the panel marks it as read automatically and the visual highlight disappears. In the notifications panel, select **Dismiss all** to mark all current notifications as read at once.

## Related content

Expand Down
Loading