azurefunctions-agents-runtime 0.0.0a2__tar.gz

azurefunctions_agents_runtime-0.0.0a2/LICENSE.md

@@ -0,0 +1,21 @@
+    MIT License
+
+    Copyright (c) Microsoft Corporation.
+
+    Permission is hereby granted, free of charge, to any person obtaining a copy
+    of this software and associated documentation files (the "Software"), to deal
+    in the Software without restriction, including without limitation the rights
+    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+    copies of the Software, and to permit persons to whom the Software is
+    furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included in all
+    copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+    SOFTWARE

azurefunctions_agents_runtime-0.0.0a2/PKG-INFO

@@ -0,0 +1,510 @@
+Metadata-Version: 2.4
+Name: azurefunctions-agents-runtime
+Version: 0.0.0a2
+Summary: A markdown-first programming model for building AI agents on Azure Functions, powered by the Microsoft Agent Framework.
+License: MIT
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE.md
+Requires-Dist: azure-functions==2.1.*
+Requires-Dist: agent-framework-core==1.3.*
+Requires-Dist: agent-framework-openai==1.3.*
+Requires-Dist: agent-framework-foundry==1.3.*
+Requires-Dist: pydantic==2.13.*
+Requires-Dist: python-frontmatter==1.1.*
+Requires-Dist: azurefunctions-extensions-http-fastapi==1.0.*
+Requires-Dist: aiohttp==3.13.*
+Requires-Dist: azure-identity==1.25.*
+Requires-Dist: azure-storage-blob==12.28.*
+Requires-Dist: jsonschema==4.26.*
+Requires-Dist: mcp==1.27.*
+Provides-Extra: dev
+Requires-Dist: ruff==0.15.*; extra == "dev"
+Requires-Dist: mypy==2.1.*; extra == "dev"
+Requires-Dist: pydantic==2.13.*; extra == "dev"
+Requires-Dist: pytest==9.0.*; extra == "dev"
+Requires-Dist: types-jsonschema==4.26.*; extra == "dev"
+Requires-Dist: pytest-cov==7.1.*; extra == "dev"
+Dynamic: license-file
+
+# azurefunctions-agents-runtime (Preview)
+
+> **Public preview.** The features described here are available for preview use and may change before general availability.
+
+A markdown-first programming model for building AI agents on Azure Functions, powered by the [Microsoft Agent Framework (MAF)](https://github.com/microsoft/agent-framework).
+
+- **Build agents with markdown** — write instructions, configure triggers, and bind tools in `.agent.md` files
+- **Run on any Azure Functions trigger** — trigger agents on timer, queue, blob, HTTP, Event Hub, Service Bus, Cosmos DB, and more
+- **Connect to 1,400+ services** — use connector-backed MCP servers to let agents act through Office 365, Teams, SQL, Salesforce, SAP, and hundreds of other connectors
+- **Extend with MCP servers** — plug in remote HTTP MCP servers, including MCP servers backed by connectors
+- **Build custom tools in plain Python** — drop a `.py` file in `tools/`, decorate functions with `@tool`, and pull in any package you need
+- **Automatic HTTP and MCP endpoints** — optionally expose your agent as an HTTP chat API and MCP server with no extra code
+- **Serverless with built-in session management** — scales to zero, persists multi-turn conversations in Azure Blob Storage
+- **Pluggable model providers** — bring OpenAI, Azure OpenAI, or Microsoft Foundry credentials and the runtime auto-detects the right client
+
+## Installation
+
+The package is published on PyPI as **`azurefunctions-agents-runtime`**.
+
+```bash
+pip install azurefunctions-agents-runtime
+```
+
+Add it to your function app's `requirements.txt`:
+
+```
+azurefunctions-agents-runtime
+```
+
+## Model Provider Configuration
+
+The runtime uses Microsoft Agent Framework, which supports Microsoft Foundry, Azure OpenAI, and OpenAI as inference back-ends. The public preview quickstart and samples use **Microsoft Foundry** as the primary path, pinned with `AZURE_FUNCTIONS_AGENTS_PROVIDER=foundry`.
+
+| Provider | `AZURE_FUNCTIONS_AGENTS_PROVIDER` | Required env vars | Notes |
+| --- | --- | --- | --- |
+| Microsoft Foundry | `foundry` | `FOUNDRY_PROJECT_ENDPOINT`, `FOUNDRY_MODEL` | Recommended quickstart/sample path. Uses `DefaultAzureCredential`; run `az login` locally and set `AZURE_CLIENT_ID` in multi-identity Function Apps. |
+| Azure OpenAI | `azure_openai` | `AZURE_OPENAI_ENDPOINT`, `AZURE_OPENAI_DEPLOYMENT`, optional `AZURE_OPENAI_API_VERSION` | Alternative Azure-hosted provider. `AZURE_OPENAI_DEPLOYMENT` takes precedence over `AZURE_FUNCTIONS_AGENTS_MODEL`. If `AZURE_OPENAI_API_KEY` is omitted the SDK uses `DefaultAzureCredential` (AAD). |
+| OpenAI | `openai` | `OPENAI_API_KEY`, optional `AZURE_FUNCTIONS_AGENTS_MODEL` (default `gpt-4o-mini`) | Alternative non-Azure provider. `AZURE_FUNCTIONS_AGENTS_MODEL` applies directly for OpenAI. |
+
+If `AZURE_FUNCTIONS_AGENTS_PROVIDER` is unset, auto-detection picks the first provider whose env vars are set, in this order: `AZURE_OPENAI_ENDPOINT` → `FOUNDRY_PROJECT_ENDPOINT` → `OPENAI_API_KEY`. Set `AZURE_FUNCTIONS_AGENTS_PROVIDER` to make the provider choice intentional.
+
+Model resolution precedence is: explicit requested model > provider-specific env (`FOUNDRY_MODEL` for Foundry, `AZURE_OPENAI_DEPLOYMENT` for Azure OpenAI) > `AZURE_FUNCTIONS_AGENTS_MODEL` > provider default.
+
+## Quick Start
+
+### 1. Create the agent file
+
+Create `main.agent.md`:
+
+```markdown
+---
+name: My Agent
+description: A helpful assistant
+
+builtin_endpoints: true
+---
+
+You are a helpful assistant. Answer questions concisely.
+```
+
+### 2. Create the function app entry point
+
+Create `function_app.py`:
+
+```python
+from azure_functions_agents import create_function_app
+
+app = create_function_app()
+```
+
+> The app root is auto-detected from `AzureWebJobsScriptRoot` (set by `func start` and the Azure Functions host). You can override it with `create_function_app(app_root=Path(__file__).parent)` or the `AZURE_FUNCTIONS_AGENTS_APP_ROOT` env var.
+
+### 3. Create `agents.config.yaml`
+
+```yaml
+# Default runtime configuration
+model: $FOUNDRY_MODEL
+timeout: 900
+```
+
+### 4. Create `host.json`
+
+```json
+{
+  "version": "2.0",
+  "extensions": {
+    "http": {
+      "routePrefix": ""
+    }
+  },
+  "extensionBundle": {
+    "id": "Microsoft.Azure.Functions.ExtensionBundle",
+    "version": "[4.*, 5.0.0)"
+  }
+}
+```
+
+### 5. Create `requirements.txt`
+
+```
+azurefunctions-agents-runtime
+```
+
+Connector-backed tools are exposed through MCP servers in `mcp.json`, and connector-triggered apps use the Azure Functions Connector Extension through the Functions extension bundle. No package extra is required.
+
+### 6. Set the model provider
+
+For local development with Microsoft Foundry, sign in with `az login`, then create `local.settings.json`:
+
+```json
+{
+  "IsEncrypted": false,
+  "Values": {
+    "FUNCTIONS_WORKER_RUNTIME": "python",
+    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
+    "AZURE_FUNCTIONS_AGENTS_PROVIDER": "foundry",
+    "FOUNDRY_PROJECT_ENDPOINT": "https://<project-name>.<region>.services.ai.azure.com/api/projects/<project-name>",
+    "FOUNDRY_MODEL": "gpt-5.4"
+  }
+}
+```
+
+### 7. Start Azurite (local storage emulator)
+
+The MCP server endpoint and non-HTTP triggers (timer, queue, blob, etc.) require a storage account. Locally, use [Azurite](https://learn.microsoft.com/azure/storage/common/storage-use-azurite) via Docker:
+
+```bash
+docker run -d --name azurite -p 10000:10000 -p 10001:10001 -p 10002:10002 \
+  mcr.microsoft.com/azure-storage/azurite \
+  azurite --skipApiVersionCheck --blobHost 0.0.0.0 --queueHost 0.0.0.0 --tableHost 0.0.0.0
+```
+
+### 8. Run locally
+
+```bash
+func start
+```
+
+Your agent is now running at `http://localhost:7071/agents/main/` with a built-in chat UI, HTTP API (`/agents/main/chat`, `/agents/main/chatstream`), and MCP tool exposed through the Functions MCP endpoint (`/runtime/webhooks/mcp`).
+
+## Features
+
+**Architecture overview:** see [`docs/architecture.md`](docs/architecture.md) for the module map and data flow pipeline.
+
+### Built-in endpoints
+
+Any `.agent.md` file can opt into built-in endpoints with `builtin_endpoints`. The route slug comes from the `.agent.md` filename after sanitization, not from the display `name:` field.
+
+- **Debug chat UI** — built-in single-page web interface at `/agents/{slug}/`
+- **HTTP APIs** — `POST /agents/{slug}/chat` (JSON) and `POST /agents/{slug}/chatstream` (SSE)
+- **MCP tool** — optional tool exposed through `/runtime/webhooks/mcp` for VS Code, Claude Desktop, etc.
+- **Session persistence** — multi-turn conversations stored in Azure Blob Storage via the runtime's `BlobHistoryProvider`, reusing the function app's `AzureWebJobsStorage` account
+
+If any built-in endpoint is enabled, `trigger` is optional. This allows endpoint-only agents as well as triggered agents that also expose a chat UI or API. `builtin_endpoints.debug_chat_ui: true` automatically enables the backing chat APIs. `builtin_endpoints: true` is shorthand for enabling all built-in endpoints, including the MCP tool. See [`docs/front-matter-spec.md#builtin_endpoints`](docs/front-matter-spec.md#builtin_endpoints).
+
+### Event-driven agents (`<name>.agent.md`)
+
+Define event-triggered agents with `.agent.md` files. Each file corresponds to a single Azure Function. Supported trigger types:
+
+- **Event triggers** — timer, queue, blob, Event Hub, Service Bus, Cosmos DB, Teams, Office 365, etc.
+- **HTTP triggers** — expose agents as REST API endpoints; add `response_example` or `response_schema` for validated JSON responses
+
+### Shared capabilities
+- **Markdown-first** — agent instructions, trigger config, and tool bindings in `.agent.md` files
+- **Skills** — progressive-disclosure prompt modules under `skills/<name>/SKILL.md` (loaded on demand via MAF's `SkillsProvider`)
+- **Custom tools** — drop a `.py` file in `tools/`, decorate functions with `@tool`, and they become callable
+- **Connector-backed MCP tools** — call Office 365, Teams, SQL, Salesforce, SAP, and other connectors through HTTP MCP servers
+- **MCP servers** — connect to external remote HTTP MCP servers for additional tools
+- **Sandbox** — Python code execution via Azure Container Apps dynamic sessions; if no explicit sandbox session id is supplied, each invocation gets a fresh GUID-backed session
+
+## Agent File Format (`.agent.md`)
+
+Agent files use YAML frontmatter + markdown body:
+
+```yaml
+---
+name: Agent Name
+description: What this agent does
+
+# Optional: system tools (code execution)
+system_tools:
+  dynamic_sessions_code_interpreter:
+    endpoint: $ACA_SESSION_POOL_ENDPOINT
+
+# Optional when builtin_endpoints is enabled; required otherwise:
+trigger:
+  type: timer_trigger      # or queue_trigger, connector_trigger, etc.
+  args:
+    schedule: "0 0 9 * * *"  # trigger-specific params passed as kwargs
+
+logger: true               # optional, default true
+substitute_variables: true # optional, default true — env-var replacement in frontmatter + body
+
+# For HTTP-triggered agents: expected response format
+response_example: |        # optional — agent returns structured JSON matching this example
+  {
+    "summary": "A brief summary",
+    "keywords": ["keyword1", "keyword2"]
+  }
+---
+
+Agent instructions in markdown...
+```
+
+> **Note**: Earlier preview releases supported a `runtime: copilot|maf` frontmatter field. As of 1.0.0 only Microsoft Agent Framework is used and the field is ignored (with a one-time warning per agent file). Remove it from your `.agent.md` files.
+
+### Multiple functions from markdown
+
+- **`*.agent.md` with `trigger`** — creates an event-triggered Azure Function. Exactly one trigger per file.
+- **`*.agent.md` with `builtin_endpoints`** — also serves `/agents/{slug}/`, `/agents/{slug}/chat`, and `/agents/{slug}/chatstream` when chat endpoints are enabled, and can expose an MCP tool when `builtin_endpoints: true` or `builtin_endpoints.mcp: true`. The sanitized filename stem becomes the base Azure Function name and endpoint slug. If two agent files sanitize to the same name (for example, `daily-report.agent.md` and `daily_report.agent.md`), the runtime auto-suffixes both the Azure Function name and the built-in endpoint slug (`_2`, `_3`, ...), keeping them paired in practice (`daily_report_2` ↔ `/agents/daily_report_2/`). The frontmatter `name:` field is display-only. See [`docs/front-matter-spec.md#function-name-resolution`](docs/front-matter-spec.md#function-name-resolution) and [`docs/front-matter-spec.md#builtin_endpoints`](docs/front-matter-spec.md#builtin_endpoints).
+
+When a triggered function runs, the agent's markdown body is used as the system instructions. The prompt sent to the agent includes the trigger type and the serialized binding data:
+
+```
+Triggered by: service_bus_queue_trigger
+
+Trigger data:
+```json
+{"body": "...", "message_id": "...", ...}
+```​
+```
+
+This applies to all trigger types, including timers (whose data includes fields like `past_due`).
+
+For a complete reference of all supported triggers and their parameters, see [docs/triggers.md](docs/triggers.md).
+
+### Trigger type resolution
+
+| Format | Resolves to | Example |
+|---|---|---|
+| `http_trigger` | Runtime HTTP adapter over `app.route(...)` | `http_trigger` |
+| No dots | `app.<type>(...)` | `timer_trigger`, `queue_trigger` |
+| `connector_trigger` | `app.connector_trigger(...)` | `connector_trigger` |
+
+### HTTP-triggered agents
+
+HTTP-triggered agents expose REST API endpoints that accept JSON input and return structured JSON output. Use `response_example` in the frontmatter to define the expected response format:
+
+```yaml
+---
+name: Summarize
+trigger:
+  type: http_trigger
+  args:
+    route: summarize
+    methods: ["POST"]
+    auth_level: FUNCTION     # ANONYMOUS | FUNCTION | ADMIN (default: FUNCTION)
+response_example: |
+  {
+    "summary": "A brief summary of the content",
+    "keywords": ["keyword1", "keyword2"],
+    "sentiment": "positive"
+  }
+---
+
+Analyze the provided content and return a structured summary.
+```
+
+The agent receives the HTTP request body as input and is instructed to return JSON matching the example. If `response_example` is omitted, the raw agent text is returned as `text/plain`.
+
+`response_schema` (JSON Schema) is also supported as an alternative to `response_example` for advanced use cases.
+
+### Environment variable substitution
+
+`docs/front-matter-spec.md#environment-variable-substitution` is the authoritative reference. In short, the runtime resolves `$VAR` and `%VAR%` placeholders inline in every string value in `agents.config.yaml`, `mcp.json`, agent frontmatter values, and the markdown body (outside fenced code blocks). Missing variables are left as literal placeholders.
+
+#### Agent instructions (markdown body)
+
+Variable references are resolved inline at load time anywhere string values are supported. Both `$VAR_NAME` and `%VAR_NAME%` syntaxes are supported, where the identifier must match `[A-Za-z_][A-Za-z0-9_]*`:
+
+```markdown
+---
+name: Notifier
+description: Sends updates to $TEAM_NAME
+system_tools:
+  dynamic_sessions_code_interpreter:
+    endpoint: "https://$HOST/api"
+---
+
+Send a daily summary email to $TO_EMAIL.
+Post a message to the %TEAM_NAME% team's General channel.
+```
+
+If `HOST=contoso.internal`, `TO_EMAIL=alice@example.com`, and `TEAM_NAME=Engineering` are set in the environment, those values resolve inline:
+
+> `endpoint: "https://contoso.internal/api"`
+>
+> Send a daily summary email to alice@example.com.
+>
+> Post a message to the Engineering team's General channel.
+
+If a referenced variable is not set, the original `$VAR_NAME` or `%VAR_NAME%` text is left unchanged.
+
+The runtime does **not** substitute dictionary keys, `${FOO}` brace syntax, identifiers starting with a digit such as `$9PORT`, or text inside fenced code blocks (`` ``` ``), so documentation examples in your instructions are preserved.
+
+For the `$IDENT` syntax, identifiers that include characters outside `[A-Za-z0-9_]` (for example `$VAR-NAME`) are matched greedily up to the first invalid character — so `$VAR-NAME` resolves to `<value-of-VAR>-NAME` when `VAR` is set, and stays `$VAR-NAME` when `VAR` is unset. The `%IDENT%` syntax requires a closing `%` immediately after the identifier, so tokens like `%VAR-NAME%` remain fully literal. Quote or escape the surrounding text if you need a `$IDENT` token to remain literal.
+
+To disable substitution for an agent's frontmatter values and markdown body, set `substitute_variables: false` in the frontmatter:
+
+```yaml
+---
+name: My Agent
+substitute_variables: false
+---
+
+Instructions with literal $VAR references that should not be replaced.
+```
+
+> **Note**: `substitute_variables` itself is read before env-var substitution. It must be a literal boolean (`true` or `false`). Setting `substitute_variables: $MY_FLAG` will not be resolved and defaults to `true`.
+
+## Custom Python tools
+
+Drop a `.py` file in `tools/` and decorate functions with `@tool`. The runtime auto-discovers them at import time and adds them to every agent.
+
+```python
+# tools/my_tools.py
+from azure_functions_agents import tool
+
+@tool
+def reverse_string(text: str) -> str:
+    """Reverse the input string."""
+    return text[::-1]
+```
+
+`@tool` is re-exported from `agent_framework`. Functions can be sync or async; types in the signature feed MAF's automatic JSON-Schema generation. Tools that need richer schemas can be declared with `agent_framework.FunctionTool` directly.
+
+## Built-in Endpoint Routes
+
+Built-in endpoints are explicit per agent. The filename stem determines `{slug}`; for example, `main.agent.md` uses `main` and `daily_azure_report.agent.md` uses `daily_azure_report`.
+
+### Chat UI
+
+A built-in single-page chat interface served at `/agents/{slug}/` when `builtin_endpoints.debug_chat_ui: true` (or `builtin_endpoints: true`). No frontend code needed — just open `http://localhost:7071/agents/main/` locally for `main.agent.md`, or `https://<your-app>.azurewebsites.net/agents/{slug}/` when deployed. See [`docs/front-matter-spec.md#function-name-resolution`](docs/front-matter-spec.md#function-name-resolution).
+
+On first load, you'll be prompted for the base URL and a function key (for deployed apps). These are stored in browser local storage and can be changed via the gear icon.
+
+### HTTP Chat API
+
+POST endpoints for programmatic access:
+
+- **Any agent with `builtin_endpoints.chat_api: true`:** `POST /agents/{slug}/chat` and `POST /agents/{slug}/chatstream`
+
+The JSON endpoint returns `session_id`, `response`, and `tool_calls`. The streaming endpoint uses Server-Sent Events (SSE) with `session`, `delta`, `intermediate`, `tool_start`, `tool_end`, `done`, and `error` events.
+
+Pass `x-ms-session-id` header to continue a conversation across requests. If omitted, a new session is created automatically.
+
+### MCP Server
+
+When `builtin_endpoints: true` or `builtin_endpoints.mcp: true`, the agent is exposed as an MCP tool named after its slug through the shared MCP-compatible endpoint at `/runtime/webhooks/mcp`. Requires the MCP extension system key in the `x-functions-key` header when deployed.
+
+### Without built-in endpoints
+
+If no agent enables built-in endpoints, no chat UI, chat API, chatstream, or agent MCP tool is registered. The app still runs triggered functions. See [`docs/front-matter-spec.md#builtin_endpoints`](docs/front-matter-spec.md#builtin_endpoints).
+
+## MCP Server Configuration
+
+You can give your agent access to external MCP servers by creating an `mcp.json` file in the app root. Only remote HTTP MCP servers are supported. The `type` field is optional — when omitted, an entry with a `url` is treated as HTTP. When `type` is specified it must be `"http"` or `"streamable-http"`; any other transport (e.g. `stdio`, `sse`) is rejected with a warning.
+
+String values in `mcp.json` support inline environment-variable substitution with both `$VAR` and `%VAR%`. Eligible fields include `url`, `headers` values, `type`, `tools` entries, and Azure identity auth values such as `auth.scope` and `auth.client_id`. Dictionary keys such as server names, environment-variable names, and header names are not substituted.
+
+```json
+{
+  "servers": {
+    "microsoft-learn": {
+      "type": "http",
+      "url": "https://$MCP_HOST/api",
+      "headers": {
+        "Authorization": "Bearer $LEARN_MCP_TOKEN"
+      }
+    },
+    "custom-api": {
+      "type": "streamable-http",
+      "url": "https://example.com/mcp",
+      "headers": {
+        "Authorization": "Bearer $MCP_TOKEN"
+      }
+    },
+    "office365-outlook": {
+      "type": "http",
+      "url": "$O365_MCP_SERVER_URL",
+      "tools": ["office365_SendEmailV2"],
+      "auth": {
+        "scope": "https://apihub.azure.com/.default",
+        "client_id": "$O365_MCP_CLIENT_ID"
+      }
+    }
+  }
+}
+```
+
+Tools from configured MCP servers are automatically available to the agent at runtime. Each server entry supports:
+
+- **`type`** — optional. When set, must be `"http"` or `"streamable-http"`. When omitted, an entry with a `url` is treated as HTTP.
+- **`url`** — the MCP server endpoint URL (required)
+- **`headers`** — optional HTTP headers (e.g. for authentication)
+- **`tools`** — optional array of tool name patterns to allow (default: `["*"]`)
+- **`auth`** — optional Azure Identity authentication configuration. Set `auth.scope` to the token scope required by the MCP server. The runtime uses `DefaultAzureCredential` to acquire the token.
+
+The runtime loads MCP tools and skips MCP prompts. This avoids startup/runtime failures from connector-backed MCP servers that support tools but reject `prompts/list`.
+
+By default, MCP auth follows the app-wide identity selection: `AZURE_CLIENT_ID` when set, otherwise the system-assigned identity/default Azure credential chain. To choose a user-assigned managed identity for a single MCP server without changing the app-wide identity, set `auth.client_id` in that server's `mcp.json` entry. If the configured client ID is empty or an unresolved placeholder, the runtime falls back to the app-wide identity selection.
+
+> **Note**: Entries without a `url`, with unresolved placeholders in `url`, or with a `type` other than `"http"` / `"streamable-http"`, are ignored with a warning. Use the remote HTTP transport instead.
+
+## Session storage
+
+Multi-turn conversations are persisted as JSON Lines, one record per message:
+
+- **Deployed apps (recommended).** When `AzureWebJobsStorage` is configured —
+  as either a connection string or the identity-based
+  `AzureWebJobsStorage__blobServiceUri` setting that `azd` provisions —
+  history is written to **Azure Blob Storage** via the runtime's
+  `BlobHistoryProvider`. One Append Blob per session is stored under
+  `agent-sessions/{session_id}.jsonl` inside the
+  `azure-functions-agents` container (override with
+  `AZURE_FUNCTIONS_AGENTS_SESSION_CONTAINER`). No file share, no storage
+  account key, no mount path; the same identity that the function app
+  already uses for `AzureWebJobsStorage` reads and writes sessions. In
+  multi-identity Function Apps, set `AZURE_CLIENT_ID` so
+  `DefaultAzureCredential` selects the intended managed identity.
+- **Local dev fallback.** When neither `AzureWebJobsStorage` nor
+  `AzureWebJobsStorage__blobServiceUri` is set, history falls back to MAF's
+  `FileHistoryProvider` writing to
+  `{AZURE_FUNCTIONS_AGENTS_SESSION_DIR}/agent-sessions/{session_id}.jsonl`,
+  defaulting to `~/.azure-functions-agents/agent-sessions/`.
+
+Session ids must match `^[A-Za-z0-9._-]{1,128}$` — anything else is rejected at the API boundary.
+
+> **Single-process scope**: A per-session `asyncio.Lock` serializes concurrent turns within a single Function instance. The contract is "one active turn per session id". Multi-instance distributed locking is intentionally out of scope.
+
+## Samples
+
+See the [`samples/`](samples/) directory for complete, deployable example apps:
+
+- [`basic-chat`](samples/basic-chat) — minimal chat agent with sandbox
+- [`daily-azure-report`](samples/daily-azure-report) — timer-triggered agent that emails a daily Azure status report
+- [`daily-tech-news-email`](samples/daily-tech-news-email) — timer-triggered agent that scrapes news and emails a digest
+- [`outlook-reply-agent`](samples/outlook-reply-agent) — connector-triggered agent that drafts replies to incoming Office 365 Outlook email
+
+## Deployment Notes
+
+### Required Azure App Settings
+
+Set the model provider env vars described above. The preview samples use Microsoft Foundry (`AZURE_FUNCTIONS_AGENTS_PROVIDER=foundry`, `FOUNDRY_PROJECT_ENDPOINT`, and `FOUNDRY_MODEL`). Azure OpenAI (`AZURE_OPENAI_ENDPOINT` + `AZURE_OPENAI_DEPLOYMENT`) and OpenAI (`OPENAI_API_KEY` and optionally `AZURE_FUNCTIONS_AGENTS_MODEL`) are supported alternatives. For Microsoft Foundry and Azure OpenAI, the provider-specific model/deployment setting takes precedence over `AZURE_FUNCTIONS_AGENTS_MODEL`.
+
+When the agent uses connector-backed MCP servers, connector triggers, or `dynamic_sessions_code_interpreter`, the function app's **system-assigned or user-assigned Managed Identity** must be enabled and granted access to the target resource — otherwise `DefaultAzureCredential` will fail to obtain a token. In multi-identity Function Apps, set `AZURE_CLIENT_ID` so the runtime uses the intended managed identity for Azure OpenAI, Foundry, blob-backed session storage, ACA Dynamic Sessions, and ARM/data-plane connector calls. For an individual MCP server, set `auth.client_id` in `mcp.json` to choose a different managed identity just for that server. For an individual code interpreter pool, set `system_tools.dynamic_sessions_code_interpreter.client_id`.
+
+### Optional config overrides
+
+| Setting | Purpose |
+|---|---|
+| `AZURE_FUNCTIONS_AGENTS_APP_ROOT` | Override the app root used to discover `*.agent.md`, `tools/`, `skills/`, and `mcp.json` |
+| `AZURE_FUNCTIONS_AGENTS_SESSION_DIR` | Override the directory used for local session storage |
+| `AZURE_FUNCTIONS_AGENTS_TIMEOUT_SECONDS` | Per-call timeout in seconds (default `900`) |
+| `AZURE_FUNCTIONS_AGENTS_PROVIDER` | Pin the model provider (`openai`/`azure_openai`/`foundry`) and skip auto-detection |
+| `AZURE_FUNCTIONS_AGENTS_MODEL` | Runtime-owned model fallback when no provider-specific model/deployment is set |
+| `AZURE_FUNCTIONS_AGENTS_REASONING_EFFORT` | Optional reasoning effort for supported reasoning models (valid values include `none`, `low`, `medium`, `high`, `xhigh`) |
+| `AZURE_FUNCTIONS_AGENTS_REASONING_SUMMARY` | Optional reasoning summary mode for supported reasoning models (valid values are `auto`, `concise`, `detailed`) |
+
+## Development
+
+```bash
+# Clone the repo
+git clone https://github.com/Azure/azure-functions-agents-runtime.git
+cd azure-functions-agents-runtime
+
+# Install in development mode
+pip install -e .
+
+# Build a wheel
+pip install build
+python -m build --wheel
+```
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+## License
+
+MIT — see [LICENSE.md](LICENSE.md).