From 2315d797e23a27d71da801417935e7cd19d7b725 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 5 Aug 2026 09:32:42 +0200
Subject: [PATCH 01/17] Rewrite docs to be more Microsoft Foundry centric
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
Makefile | 6 +-
docs/scripts/auto-generate-examples.py | 10 +-
docs/scripts/auto-update-toctree.py | 29 +--
docs/source/_redirects.yml | 39 ++--
docs/source/_toctree.yml | 115 ++++++++----
docs/source/agents/introduction.mdx | 1 +
docs/source/deprecated/faq.mdx | 11 ++
docs/source/deprecated/features.mdx | 17 ++
.../examples/build-agents-with-smolagents.mdx | 27 +++
.../examples/deploy-large-language-models.mdx | 27 +++
.../examples/deploy-nvidia-parakeet-asr.mdx | 26 +++
.../foundry/examples/deploy-smollm3.mdx | 26 +++
.../deploy-vision-language-models.mdx | 26 +++
docs/source/deprecated/foundry/hardware.mdx | 5 +
.../deprecated/foundry/introduction.mdx | 5 +
docs/source/deprecated/foundry/models.mdx | 9 +
docs/source/deprecated/foundry/tasks.mdx | 5 +
.../deprecated/guides/access-gated-models.mdx | 13 ++
.../configure-azure-ml-microsoft-foundry.mdx | 17 ++
.../source/deprecated/guides/introduction.mdx | 17 ++
.../guides/managed-compute-foundry.mdx | 12 ++
.../guides/one-click-deployment-foundry.mdx | 17 ++
.../guides/request-model-addition.mdx | 13 ++
.../tool-calling-agent-fine-tuning.mdx | 22 +++
docs/source/deprecated/overview.mdx | 11 ++
docs/source/{ => deprecated}/resources.mdx | 20 +-
docs/source/deprecated/security.mdx | 14 ++
docs/source/faq.mdx | 28 ---
docs/source/features.mdx | 81 --------
docs/source/foundry/hardware.mdx | 43 -----
docs/source/foundry/introduction.mdx | 20 --
docs/source/foundry/models.mdx | 29 ---
docs/source/foundry/tasks.mdx | 41 ----
...els-from-microsoft-foundry-with-python.mdx | 1 +
...loy-open-models-from-microsoft-foundry.mdx | 1 +
docs/source/guides/access-gated-models.mdx | 136 --------------
.../configure-azure-ml-microsoft-foundry.mdx | 134 --------------
docs/source/guides/introduction.mdx | 11 --
.../source/guides/managed-compute-foundry.mdx | 175 ------------------
.../guides/one-click-deployment-foundry.mdx | 27 ---
docs/source/guides/request-model-addition.mdx | 23 ---
docs/source/index.mdx | 49 ++++-
.../large-language-models/introduction.mdx | 1 +
docs/source/security.mdx | 25 ---
44 files changed, 509 insertions(+), 856 deletions(-)
create mode 100644 docs/source/agents/introduction.mdx
create mode 100644 docs/source/deprecated/faq.mdx
create mode 100644 docs/source/deprecated/features.mdx
create mode 100644 docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
create mode 100644 docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
create mode 100644 docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
create mode 100644 docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
create mode 100644 docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
create mode 100644 docs/source/deprecated/foundry/hardware.mdx
create mode 100644 docs/source/deprecated/foundry/introduction.mdx
create mode 100644 docs/source/deprecated/foundry/models.mdx
create mode 100644 docs/source/deprecated/foundry/tasks.mdx
create mode 100644 docs/source/deprecated/guides/access-gated-models.mdx
create mode 100644 docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
create mode 100644 docs/source/deprecated/guides/introduction.mdx
create mode 100644 docs/source/deprecated/guides/managed-compute-foundry.mdx
create mode 100644 docs/source/deprecated/guides/one-click-deployment-foundry.mdx
create mode 100644 docs/source/deprecated/guides/request-model-addition.mdx
create mode 100644 docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
create mode 100644 docs/source/deprecated/overview.mdx
rename docs/source/{ => deprecated}/resources.mdx (68%)
create mode 100644 docs/source/deprecated/security.mdx
delete mode 100644 docs/source/faq.mdx
delete mode 100644 docs/source/features.mdx
delete mode 100644 docs/source/foundry/hardware.mdx
delete mode 100644 docs/source/foundry/introduction.mdx
delete mode 100644 docs/source/foundry/models.mdx
delete mode 100644 docs/source/foundry/tasks.mdx
create mode 100644 docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx
create mode 100644 docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx
delete mode 100644 docs/source/guides/access-gated-models.mdx
delete mode 100644 docs/source/guides/configure-azure-ml-microsoft-foundry.mdx
delete mode 100644 docs/source/guides/introduction.mdx
delete mode 100644 docs/source/guides/managed-compute-foundry.mdx
delete mode 100644 docs/source/guides/one-click-deployment-foundry.mdx
delete mode 100644 docs/source/guides/request-model-addition.mdx
create mode 100644 docs/source/large-language-models/introduction.mdx
delete mode 100644 docs/source/security.mdx
diff --git a/Makefile b/Makefile
index ee13bf7..072a57d 100644
--- a/Makefile
+++ b/Makefile
@@ -7,8 +7,8 @@ install:
docs: clean
@$(foreach svc,$(SERVICES), \
- echo "Creating docs/source/$(svc)/examples directory for examples/$(svc)..." && \
- mkdir -p docs/source/$(svc)/examples && \
+ echo "Creating docs/source/deprecated/$(svc)/examples directory for examples/$(svc)..." && \
+ mkdir -p docs/source/deprecated/$(svc)/examples && \
echo "Converting Jupyter Notebooks to MDX for $(svc)..." && \
doc-builder notebook-to-mdx examples/$(svc)/ && \
) true
@@ -26,7 +26,7 @@ docs: clean
clean:
@echo "Cleaning up generated documentation..."
@$(foreach svc,$(SERVICES), \
- rm -rf docs/source/$(svc)/examples && \
+ rm -rf docs/source/deprecated/$(svc)/examples && \
) true
@awk '/# GENERATED CONTENT DO NOT EDIT/,/# END OF GENERATED CONTENT/{next} {print}' docs/source/_toctree.yml | sed -e :a -e '/^\n*$$/{$$d;N;ba' -e '}' > docs/source/_toctree.yml.tmp; mv docs/source/_toctree.yml.tmp docs/source/_toctree.yml
@echo "Cleaning up generated Markdown Notebook files (if any)..."
diff --git a/docs/scripts/auto-generate-examples.py b/docs/scripts/auto-generate-examples.py
index 354aa77..9025ae9 100644
--- a/docs/scripts/auto-generate-examples.py
+++ b/docs/scripts/auto-generate-examples.py
@@ -3,10 +3,12 @@
import subprocess
SERVICES = [
- ("Microsoft Foundry", "foundry"),
- ("Azure Machine Learning", "machine-learning"),
+ ("Archived Microsoft Foundry", "foundry"),
+ ("Archived Azure Machine Learning", "machine-learning"),
]
+TARGET_ROOT = "docs/source/deprecated"
+
def get_git_date(file_path: str) -> str | None:
"""Get the last commit date (YYYY-MM-DD) for a file using git."""
@@ -29,7 +31,7 @@ def get_git_date(file_path: str) -> str | None:
def process_readme_files():
for _, dir_name in SERVICES:
print(f"Processing azure-notebook.md files from examples/{dir_name}...")
- os.makedirs(f"docs/source/{dir_name}/examples", exist_ok=True)
+ os.makedirs(f"{TARGET_ROOT}/{dir_name}/examples", exist_ok=True)
for root, _, files in os.walk(f"examples/{dir_name}"):
for file in files:
@@ -42,7 +44,7 @@ def process_file(root, file, dir_name):
subdir = root.replace(f"examples/{dir_name}/", "")
base = os.path.basename(subdir)
- target = f"docs/source/{dir_name}/examples/{base}.mdx"
+ target = f"{TARGET_ROOT}/{dir_name}/examples/{base}.mdx"
print(f"Processing {file_path} to {target}")
with open(file_path, "r") as f:
diff --git a/docs/scripts/auto-update-toctree.py b/docs/scripts/auto-update-toctree.py
index 36436bd..c18fa03 100644
--- a/docs/scripts/auto-update-toctree.py
+++ b/docs/scripts/auto-update-toctree.py
@@ -6,8 +6,8 @@
from pathlib import Path
SERVICES = [
- ("Microsoft Foundry", "foundry"),
- ("Azure Machine Learning", "machine-learning"),
+ ("Archived Microsoft Foundry examples", "foundry"),
+ ("Archived Azure Machine Learning examples", "machine-learning"),
]
@@ -129,7 +129,7 @@ def inject_author_date(content: str, author: str | None, date: str | None) -> st
def get_example_entries(dir_name: str) -> list:
"""Find, process, and sort example files for a given service directory."""
- example_files = sorted(glob.glob(f"docs/source/{dir_name}/examples/*.mdx"))
+ example_files = sorted(glob.glob(f"docs/source/deprecated/{dir_name}/examples/*.mdx"))
if not example_files:
return []
@@ -179,20 +179,19 @@ def get_example_entries(dir_name: str) -> list:
return entries
-def build_examples_section(dir_name: str, entries: list) -> list:
+def build_examples_section(dir_name: str, entries: list, indent: str) -> list:
"""Build the YAML lines for an Examples sub-section."""
lines = []
- lines.append(" # GENERATED CONTENT DO NOT EDIT")
- lines.append(" - sections:")
+ lines.append(f"{indent}# GENERATED CONTENT DO NOT EDIT")
+ lines.append(f"{indent}- sections:")
for base, title, is_new, creation_date in entries:
- lines.append(f" - local: {dir_name}/examples/{base}")
- lines.append(f' title: "{title}"')
+ lines.append(f"{indent} - local: deprecated/{dir_name}/examples/{base}")
+ lines.append(f'{indent} title: "{title}"')
# if is_new:
# lines.append(" new: true")
- lines.append(" title: Examples")
- # NOTE: set to true now, to improve discoverability
- lines.append(" isExpanded: true")
- lines.append(" # END OF GENERATED CONTENT")
+ lines.append(f"{indent} title: Examples")
+ lines.append(f"{indent} isExpanded: false")
+ lines.append(f"{indent}# END OF GENERATED CONTENT")
return lines
@@ -223,7 +222,9 @@ def inject_examples_for_service(
result_lines = []
for line in lines:
if is_service_title_line(line, display_name):
- result_lines.extend(build_examples_section(dir_name, entries))
+ indent_match = re.match(r"^(\s*)title:", line)
+ indent = indent_match.group(1) if indent_match else " "
+ result_lines.extend(build_examples_section(dir_name, entries, indent))
result_lines.append(line)
return result_lines
@@ -235,7 +236,7 @@ def inject_examples_for_service(
new_section.append("- sections:")
new_section.append(" - sections:")
for base, title, is_new, creation_date in entries:
- new_section.append(f" - local: {dir_name}/examples/{base}")
+ new_section.append(f" - local: deprecated/{dir_name}/examples/{base}")
new_section.append(f' title: "{title}"')
new_section.append(" title: Examples")
new_section.append(" isExpanded: true")
diff --git a/docs/source/_redirects.yml b/docs/source/_redirects.yml
index 3c9ae61..6bbd906 100644
--- a/docs/source/_redirects.yml
+++ b/docs/source/_redirects.yml
@@ -1,16 +1,29 @@
-guides/one-click-deployment-azure-ml: guides/one-click-deployment-foundry
-guides/one-click-deployment-azure-ai: guides/one-click-deployment-foundry
-azure-ai/configure: guides/configure-azure-ml-microsoft-foundry
-azure-ai/set-up: guides/configure-azure-ml-microsoft-foundry
+guides/one-click-deployment-azure-ml: deprecated/guides/one-click-deployment-foundry
+guides/one-click-deployment-azure-ai: deprecated/guides/one-click-deployment-foundry
+azure-ai/configure: deprecated/guides/configure-azure-ml-microsoft-foundry
+azure-ai/set-up: deprecated/guides/configure-azure-ml-microsoft-foundry
# NOTE: The redirects below are required only for the entries and examples
# published before the rename from Azure AI Foundry to Microsoft Foundry
-azure-ai/hardware: foundry/hardware
-azure-ai/introduction: foundry/introduction
-azure-ai/models: foundry/models
-azure-ai/tasks: foundry/tasks
-azure-ai/examples/build-agents-with-smolagents: foundry/examples/build-agents-with-smolagents
-azure-ai/examples/deploy-large-language-models: foundry/examples/deploy-large-language-models
-azure-ai/examples/deploy-nvidia-parakeet-asr: foundry/examples/deploy-nvidia-parakeet-asr
-azure-ai/examples/deploy-smollm3: foundry/examples/deploy-smollm3
-azure-ai/examples/deploy-vision-language-models: foundry/examples/deploy-vision-language-models
+azure-ai/hardware: deprecated/foundry/hardware
+azure-ai/introduction: deprecated/foundry/introduction
+azure-ai/models: deprecated/foundry/models
+azure-ai/tasks: deprecated/foundry/tasks
+azure-ai/examples/build-agents-with-smolagents: deprecated/foundry/examples/build-agents-with-smolagents
+azure-ai/examples/deploy-large-language-models: deprecated/foundry/examples/deploy-large-language-models
+azure-ai/examples/deploy-nvidia-parakeet-asr: deprecated/foundry/examples/deploy-nvidia-parakeet-asr
+azure-ai/examples/deploy-smollm3: deprecated/foundry/examples/deploy-smollm3
+azure-ai/examples/deploy-vision-language-models: deprecated/foundry/examples/deploy-vision-language-models
+
+features: deprecated/features
+security: deprecated/security
+faq: deprecated/faq
+guides/introduction: deprecated/guides/introduction
+guides/managed-compute-foundry: deprecated/guides/managed-compute-foundry
+guides/access-gated-models: deprecated/guides/access-gated-models
+guides/configure-azure-ml-microsoft-foundry: deprecated/guides/configure-azure-ml-microsoft-foundry
+guides/one-click-deployment-foundry: deprecated/guides/one-click-deployment-foundry
+foundry/introduction: deprecated/foundry/introduction
+foundry/models: deprecated/foundry/models
+foundry/tasks: deprecated/foundry/tasks
+foundry/hardware: deprecated/foundry/hardware
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index b7fce87..d0acc6a 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -1,35 +1,88 @@
- sections:
- local: index
- title: Hugging Face on Microsoft Azure
- - local: features
- title: Features & Benefits
- - local: security
- title: Security & Compliance
- - local: resources
- title: Other Resources
- - local: faq
- title: Frequent Asked Questions (FAQ)
- title: Getting Started
+ title: Overview
+ title: Overview
- sections:
- - local: guides/managed-compute-foundry
- title: Deploy Hugging Face Models in Foundry with Managed Compute
- - local: guides/one-click-deployment-foundry
- title: One-click deployments from the Hugging Face Hub on Microsoft Foundry
- - local: guides/access-gated-models
- title: Deploy Hugging Face gated models on Microsoft Foundry
- - local: guides/request-model-addition
- title: Request a model addition in the Hugging Face collection on Microsoft Foundry
- - local: guides/configure-azure-ml-microsoft-foundry
- title: Configure Azure Machine Learning and Microsoft Foundry
- local: guides/introduction
- title: Guides
+ - local: get-started/deploy-open-models-on-microsoft-foundry-with-python
+ title: Deploy open-models on Microsoft Foundry with Python
+ - local: get-started/deploy-open-models-on-microsoft-foundry
+ title: Deploy open-models on Microsoft Foundry
+ title: Get started
- sections:
- - local: foundry/introduction
- title: Introduction
- - local: foundry/tasks
- title: Supported Tasks
- - local: foundry/hardware
- title: Supported Hardware
- - local: foundry/models
- title: Supported Models
- title: Microsoft Foundry
+ - local: agents/introduction
+ title: Agents
+ title: Agents
+- sections:
+ - local: large-language-models/introduction
+ title: Large Language Models
+ title: Large Language Models
+- sections:
+ - local: deprecated/overview
+ title: Overview
+ - sections:
+ - local: deprecated/features
+ title: Features & Benefits
+ - local: deprecated/security
+ title: Security & Compliance
+ - local: deprecated/resources
+ title: Other Resources
+ - local: deprecated/faq
+ title: FAQ
+ title: Legacy top-level pages
+ isExpanded: false
+ - sections:
+ - local: deprecated/guides/introduction
+ title: Guides index
+ - local: deprecated/guides/configure-azure-ml-microsoft-foundry
+ title: Configure Azure Machine Learning and Microsoft Foundry
+ - local: deprecated/guides/managed-compute-foundry
+ title: Deploy Hugging Face Models in Foundry with Managed Compute
+ - local: deprecated/guides/one-click-deployment-foundry
+ title: One-click deployments from the Hugging Face Hub on Microsoft Foundry
+ - local: deprecated/guides/access-gated-models
+ title: Deploy Hugging Face gated models on Microsoft Foundry
+ - local: deprecated/guides/request-model-addition
+ title: Request a model addition in the Hugging Face collection on Microsoft Foundry
+ title: Legacy guides
+ isExpanded: false
+ - sections:
+ - local: deprecated/foundry/introduction
+ title: Introduction
+ - local: deprecated/foundry/tasks
+ title: Supported tasks
+ - local: deprecated/foundry/hardware
+ title: Supported hardware
+ - local: deprecated/foundry/models
+ title: Supported models
+ title: Legacy Foundry reference
+ isExpanded: false
+ - sections:
+ # GENERATED CONTENT DO NOT EDIT
+ - sections:
+ - local: deprecated/foundry/examples/build-agents-with-smolagents
+ title: "Archived Example: Build Agents with smolagents on Microsoft Foundry"
+ - local: deprecated/foundry/examples/deploy-large-language-models
+ title: "Archived Example: Deploy Large Language Models on Microsoft Foundry"
+ - local: deprecated/foundry/examples/deploy-nvidia-parakeet-asr
+ title: "Archived Example: Deploy NVIDIA Parakeet for ASR on Microsoft Foundry"
+ - local: deprecated/foundry/examples/deploy-smollm3
+ title: "Archived Example: Deploy SmolLM3 on Microsoft Foundry"
+ - local: deprecated/foundry/examples/deploy-vision-language-models
+ title: "Archived Example: Deploy Vision Language Models on Microsoft Foundry"
+ title: Examples
+ isExpanded: false
+ # END OF GENERATED CONTENT
+ title: Archived Microsoft Foundry examples
+ isExpanded: false
+ - sections:
+ # GENERATED CONTENT DO NOT EDIT
+ - sections:
+ - local: deprecated/machine-learning/examples/tool-calling-agent-fine-tuning
+ title: "Archived Example: Tool-calling Agent Fine-tuning on Azure Machine Learning"
+ title: Examples
+ isExpanded: false
+ # END OF GENERATED CONTENT
+ title: Archived Azure Machine Learning examples
+ isExpanded: false
+ title: Deprecated / Archived
+ isExpanded: false
diff --git a/docs/source/agents/introduction.mdx b/docs/source/agents/introduction.mdx
new file mode 100644
index 0000000..57be659
--- /dev/null
+++ b/docs/source/agents/introduction.mdx
@@ -0,0 +1 @@
+# Agents
diff --git a/docs/source/deprecated/faq.mdx b/docs/source/deprecated/faq.mdx
new file mode 100644
index 0000000..c4cff70
--- /dev/null
+++ b/docs/source/deprecated/faq.mdx
@@ -0,0 +1,11 @@
+# Archived: FAQ
+
+This page preserves the older FAQ topics from the previous docs structure.
+
+## What did the old FAQ focus on?
+
+- The distinction between Azure Machine Learning and Microsoft Foundry
+- Why hub-based projects mattered for open-model deployments
+- What capabilities were limited in standalone Foundry projects
+
+That content has been simplified in the current [FAQ](../reference/faq), but the old framing is still useful when reading older screenshots, tutorials, or issue threads that refer to Azure AI Foundry hubs and projects.
diff --git a/docs/source/deprecated/features.mdx b/docs/source/deprecated/features.mdx
new file mode 100644
index 0000000..0ead4dc
--- /dev/null
+++ b/docs/source/deprecated/features.mdx
@@ -0,0 +1,17 @@
+# Archived: Features & Benefits
+
+This page preserves the former high-level features summary from the previous documentation structure.
+
+The legacy framing emphasized:
+
+- A large Hugging Face catalog available through Microsoft Foundry and Azure Machine Learning
+- Managed deployment paths with Azure-hosted security, scaling, and monitoring
+- Coverage across text, multimodal, audio, vision, and embeddings workloads
+- Open-source runtimes such as TGI, vLLM, SGLang, and TEI
+- Enterprise controls around compliance, isolation, and governance
+
+For the current task-oriented docs, use:
+
+- [Overview](../index)
+- [Supported models](../reference/supported-models)
+- [Security and model eligibility](../reference/security-and-eligibility)
diff --git a/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx b/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
new file mode 100644
index 0000000..c8ff608
--- /dev/null
+++ b/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
@@ -0,0 +1,27 @@
+# Archived Example: Build Agents with smolagents on Microsoft Foundry
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example focused on building an agent with `smolagents` on top of a Hugging Face deployment in Microsoft Foundry.
+
+## What it covered
+
+- Deploying a coding-oriented LLM from the Hugging Face collection
+- Invoking the model from Python
+- Wiring the deployment into a `smolagents` workflow
+- Comparing Hub, Azure ML, and Foundry views of the same model
+
+## Original assets
+
+- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/build-agents-with-smolagents/azure-notebook.ipynb)
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/build-agents-with-smolagents)
+
+## Current docs to read instead
+
+- [Build agents with Foundry deployments](../../../agents/introduction)
+- [Define custom tools](../../../agents/define-custom-tools)
+- [Connect MCP servers](../../../agents/connect-mcp)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx b/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
new file mode 100644
index 0000000..9e8b004
--- /dev/null
+++ b/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
@@ -0,0 +1,27 @@
+# Archived Example: Deploy Large Language Models on Microsoft Foundry
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example showed a more notebook-heavy path for deploying a text-generation model and then calling it from several clients.
+
+## What it covered
+
+- Programmatic deployment with the Azure ML SDK
+- OpenAI-compatible inference calls
+- A local Gradio chat client
+- The relationship between the Hugging Face model ID and the Azure model URI
+
+## Original assets
+
+- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-large-language-models/azure-notebook.ipynb)
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-large-language-models)
+
+## Current docs to read instead
+
+- [Deploy your first model](../../../get-started/deploy-first-model)
+- [Call your deployment](../../../get-started/call-your-deployment)
+- [Third-party integrations](../../../guides/third-party-integrations)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx b/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
new file mode 100644
index 0000000..6ead456
--- /dev/null
+++ b/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
@@ -0,0 +1,26 @@
+# Archived Example: Deploy NVIDIA Parakeet for ASR on Microsoft Foundry
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example focused on automatic speech recognition using NVIDIA Parakeet.
+
+## What it covered
+
+- Deploying an ASR model from the Hugging Face collection
+- Sending audio transcription requests
+- Comparing different client approaches, including cURL and Python
+- Working with a speech-focused deployment instead of a text chat model
+
+## Original assets
+
+- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-nvidia-parakeet-asr/azure-notebook.ipynb)
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-nvidia-parakeet-asr)
+
+## Current docs to read instead
+
+- [Deploy your first model](../../../get-started/deploy-first-model)
+- [Supported tasks](../../../reference/supported-tasks)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx b/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
new file mode 100644
index 0000000..de6ce17
--- /dev/null
+++ b/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
@@ -0,0 +1,26 @@
+# Archived Example: Deploy SmolLM3 on Microsoft Foundry
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example focused on deploying `HuggingFaceTB/SmolLM3-3B` and calling it through the OpenAI-compatible route.
+
+## What it covered
+
+- Building the Azure model URI from the Hugging Face model ID
+- Creating a managed endpoint and deployment
+- Running text-generation requests
+- Reasoning-oriented and long-context positioning for a small model
+
+## Original assets
+
+- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-smollm3/azure-notebook.ipynb)
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-smollm3)
+
+## Current docs to read instead
+
+- [Deploy your first model](../../../get-started/deploy-first-model)
+- [Thinking levels](../../../guides/thinking-levels)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx b/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
new file mode 100644
index 0000000..053525d
--- /dev/null
+++ b/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
@@ -0,0 +1,26 @@
+# Archived Example: Deploy Vision Language Models on Microsoft Foundry
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example focused on multimodal deployments, using a vision-language model that accepts both images and text.
+
+## What it covered
+
+- Deploying a VLM from the Hugging Face collection
+- Sending multimodal requests
+- Using the deployment through both SDK and notebook flows
+- Handling image-aware prompts in a Foundry deployment
+
+## Original assets
+
+- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-vision-language-models/azure-notebook.ipynb)
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-vision-language-models)
+
+## Current docs to read instead
+
+- [Deploy your first model](../../../get-started/deploy-first-model)
+- [Supported tasks](../../../reference/supported-tasks)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/hardware.mdx b/docs/source/deprecated/foundry/hardware.mdx
new file mode 100644
index 0000000..0d18581
--- /dev/null
+++ b/docs/source/deprecated/foundry/hardware.mdx
@@ -0,0 +1,5 @@
+# Archived: Supported Hardware
+
+This page preserves the older hardware table references for GPU and CPU instance families used in Foundry-related deployment flows.
+
+The maintained version is [Supported hardware](../../reference/supported-hardware).
diff --git a/docs/source/deprecated/foundry/introduction.mdx b/docs/source/deprecated/foundry/introduction.mdx
new file mode 100644
index 0000000..4048557
--- /dev/null
+++ b/docs/source/deprecated/foundry/introduction.mdx
@@ -0,0 +1,5 @@
+# Archived: Hugging Face on Microsoft Foundry
+
+This page preserves the former service-introduction page that described the broader Hugging Face and Microsoft collaboration, the expansion through Build and Ignite announcements, and the catalog-scale messaging used in the earlier docs.
+
+That material has been replaced in the main docs by a shorter, task-oriented [Overview](../../index).
diff --git a/docs/source/deprecated/foundry/models.mdx b/docs/source/deprecated/foundry/models.mdx
new file mode 100644
index 0000000..6e3721e
--- /dev/null
+++ b/docs/source/deprecated/foundry/models.mdx
@@ -0,0 +1,9 @@
+# Archived: Supported Models
+
+This page preserves the earlier explanation of how to check whether a Hugging Face model is available in the Foundry catalog, including:
+
+- Checking the **Deploy on Microsoft Foundry** action on the Hub
+- Searching the Hugging Face collection in Foundry
+- Using the old Azure lookup endpoint mentioned in the earlier docs
+
+The maintained version is [Supported models](../../reference/supported-models).
diff --git a/docs/source/deprecated/foundry/tasks.mdx b/docs/source/deprecated/foundry/tasks.mdx
new file mode 100644
index 0000000..2ac9d59
--- /dev/null
+++ b/docs/source/deprecated/foundry/tasks.mdx
@@ -0,0 +1,5 @@
+# Archived: Supported Tasks
+
+This page preserves the older task list wording that grouped supported workloads across text, multimodal, audio, and vision.
+
+The maintained version is [Supported tasks](../../reference/supported-tasks).
diff --git a/docs/source/deprecated/guides/access-gated-models.mdx b/docs/source/deprecated/guides/access-gated-models.mdx
new file mode 100644
index 0000000..a964851
--- /dev/null
+++ b/docs/source/deprecated/guides/access-gated-models.mdx
@@ -0,0 +1,13 @@
+# Archived: Deploy Hugging Face gated models on Microsoft Foundry
+
+This page preserves the former gated-model deployment flow.
+
+## Legacy flow summary
+
+1. Request access to the gated repository on the Hugging Face Hub
+2. Create a Hugging Face token with gated-repository read permissions
+3. Store that token in an Azure Machine Learning connection
+4. Ensure the endpoint can access the secret store
+5. Deploy the model using the Azure ML SDK
+
+The maintained version of this guidance is [Gated models](../../guides/gated-models).
diff --git a/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx b/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
new file mode 100644
index 0000000..e91c641
--- /dev/null
+++ b/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
@@ -0,0 +1,17 @@
+# Archived: Configure Azure Machine Learning and Microsoft Foundry
+
+This page preserves the former setup flow that walked through:
+
+1. Installing and authenticating the Azure CLI
+2. Installing the `az ml` extension
+3. Creating a resource group
+4. Creating an Azure AI Foundry hub
+5. Creating a project attached to that hub
+
+That flow assumed the older Azure AI Foundry naming and hub/project model. The maintained version is [Configure Microsoft Foundry](../../get-started/configure-foundry).
+
+## Legacy notes
+
+- Older guides and notebooks may refer to Azure AI Foundry instead of Microsoft Foundry
+- Older commands may reference hub-based projects explicitly
+- Some screenshots and resource names in notebooks still follow that older wording
diff --git a/docs/source/deprecated/guides/introduction.mdx b/docs/source/deprecated/guides/introduction.mdx
new file mode 100644
index 0000000..fbd7cb1
--- /dev/null
+++ b/docs/source/deprecated/guides/introduction.mdx
@@ -0,0 +1,17 @@
+# Archived: Guides
+
+This page used to act as the guides index in the former documentation structure.
+
+The old guide set centered on:
+
+- One-click deployments from the Hugging Face Hub
+- Deploying gated models
+- Requesting model additions
+- Configuring Azure Machine Learning and Microsoft Foundry
+- Managed compute
+
+The maintained equivalents now live under:
+
+- [Get started](../../get-started/introduction)
+- [Guides](../../guides/managed-compute)
+- [Agents](../../agents/introduction)
diff --git a/docs/source/deprecated/guides/managed-compute-foundry.mdx b/docs/source/deprecated/guides/managed-compute-foundry.mdx
new file mode 100644
index 0000000..da79f67
--- /dev/null
+++ b/docs/source/deprecated/guides/managed-compute-foundry.mdx
@@ -0,0 +1,12 @@
+# Archived: Deploy Hugging Face Models in Foundry with Managed Compute
+
+This archived page keeps the older, more detailed managed-compute framing that predated the simplified guide set.
+
+The former guide emphasized:
+
+- Managed compute as a dedicated-capacity deployment option
+- Accelerator-family-specific quota requirements
+- Template-driven deployment choices
+- Validation through the Foundry playground before moving to code
+
+For the current streamlined version, see [Managed compute](../../guides/managed-compute).
diff --git a/docs/source/deprecated/guides/one-click-deployment-foundry.mdx b/docs/source/deprecated/guides/one-click-deployment-foundry.mdx
new file mode 100644
index 0000000..7f79db7
--- /dev/null
+++ b/docs/source/deprecated/guides/one-click-deployment-foundry.mdx
@@ -0,0 +1,17 @@
+# Archived: One-click deployments from the Hugging Face Hub on Microsoft Foundry
+
+This page preserves the former one-click deployment entry point.
+
+## Legacy flow
+
+1. Browse models on the Hugging Face Hub
+2. Use the **Deploy** button on a supported model card
+3. Choose **Deploy on Microsoft Foundry**
+4. Review the model card in Foundry
+5. Create the deployment and test the endpoint
+
+The current maintained equivalent is [Deploy your first model](../../get-started/deploy-first-model).
+
+## Why keep this archived page?
+
+Older tutorials, screenshots, and issues often refer to the Hub-first flow rather than the current docs navigation.
diff --git a/docs/source/deprecated/guides/request-model-addition.mdx b/docs/source/deprecated/guides/request-model-addition.mdx
new file mode 100644
index 0000000..cbf61ee
--- /dev/null
+++ b/docs/source/deprecated/guides/request-model-addition.mdx
@@ -0,0 +1,13 @@
+# Archived: Request a model addition in the Hugging Face collection on Microsoft Foundry
+
+This page preserves the earlier model-addition guidance from the old docs structure.
+
+The previous checklist focused on:
+
+- `Transformers`, `Diffusers`, or `Sentence-Transformers` compatibility
+- A supported task taxonomy
+- Runtime alignment for TGI, vLLM, SGLang, or TEI when relevant
+- Public visibility on the Hub
+- Secure artifact formats and security scanning
+
+The maintained version is [Request model addition](../../guides/request-model-addition).
diff --git a/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx b/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
new file mode 100644
index 0000000..b74f669
--- /dev/null
+++ b/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
@@ -0,0 +1,22 @@
+# Archived Example: Tool-calling Agent Fine-tuning on Azure Machine Learning
+
+
Last updated 2026-03-02
+
+
+
Last updated 2026-03-02
+
+
+This archived example comes from the earlier Azure Machine Learning example set rather than the current Foundry-first docs path.
+
+## What it covered
+
+- Fine-tuning an agent-oriented model
+- Preparing training data for tool-calling behavior
+- Running an Azure Machine Learning job
+- Inspecting experiment and log outputs
+
+## Original assets
+
+- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/machine-learning/tool-calling-agent-fine-tuning)
+
+This material remains archived because the active docs are now centered on Foundry deployment and integration workflows instead of Azure ML training examples.
\ No newline at end of file
diff --git a/docs/source/deprecated/overview.mdx b/docs/source/deprecated/overview.mdx
new file mode 100644
index 0000000..a266581
--- /dev/null
+++ b/docs/source/deprecated/overview.mdx
@@ -0,0 +1,11 @@
+# Deprecated / Archived
+
+This section preserves the former documentation layout and legacy examples that existed before the docs were reorganized around the simpler Foundry-focused structure.
+
+Use this section when you need to:
+
+- Follow an old link that no longer belongs in the main learning path
+- Recover older wording, screenshots, or step-by-step examples
+- Compare the previous docs organization with the current one
+
+The archived pages are kept for continuity, not as the recommended entry point for new users. For the current docs, start from the main [Overview](../index).
diff --git a/docs/source/resources.mdx b/docs/source/deprecated/resources.mdx
similarity index 68%
rename from docs/source/resources.mdx
rename to docs/source/deprecated/resources.mdx
index 3b0cf10..6dcf149 100644
--- a/docs/source/resources.mdx
+++ b/docs/source/deprecated/resources.mdx
@@ -1,20 +1,14 @@
-# Resources
+# Archived: Other Resources
-- [Hugging Face on Azure](https://azure.microsoft.com/en-us/solutions/hugging-face-on-azure)
-
-## Posts
+This page keeps the older external-reading collection that used to live near the top of the docs.
-### 2025
+## Legacy links
+- [Hugging Face on Azure](https://azure.microsoft.com/en-us/solutions/hugging-face-on-azure)
- [Microsoft and Hugging Face expand collaboration](https://huggingface.co/blog/azure-ai-foundry)
- [Microsoft and Hugging Face expand collaboration to accelerate Open-Source AI Innovation on Azure AI Foundry](https://devblogs.microsoft.com/foundry/microsoft-and-hugging-face-expand-partnership-to-accelerate-open-source-ai-innovation-on-azure-ai-foundry/)
-
-### 2024
-
-- [From cloud to developers: Hugging Face and Microsoft Deepen Collaboration](https://huggingface.co/blog/microsoft-collaboration)
+- [From cloud to developers: Hugging Face and Microsoft deepen collaboration](https://huggingface.co/blog/microsoft-collaboration)
- [Microsoft and Hugging Face deepen generative AI partnership](https://techcommunity.microsoft.com/blog/aiplatformblog/microsoft-and-hugging-face-deepen-generative-ai-partnership/4144565)
+- [Hugging Face collaborates with Microsoft to launch Hugging Face Model Catalog on Azure](https://huggingface.co/blog/hugging-face-endpoints-on-azure)
-### 2023
-
-- [Hugging Face Collaborates with Microsoft to launch Hugging Face Model Catalog on Azure](https://huggingface.co/blog/hugging-face-endpoints-on-azure)
-- [Accelerating over 130,000 Hugging Face models with ONNX Runtime](https://opensource.microsoft.com/blog/2023/10/04/accelerating-over-130000-hugging-face-models-with-onnx-runtime/)
+For the maintained external-links page, see [Resources](../resources).
diff --git a/docs/source/deprecated/security.mdx b/docs/source/deprecated/security.mdx
new file mode 100644
index 0000000..4d552b4
--- /dev/null
+++ b/docs/source/deprecated/security.mdx
@@ -0,0 +1,14 @@
+# Archived: Security & Compliance
+
+This page preserves the earlier security-focused explanation from the old docs layout.
+
+The legacy guidance highlighted the following model eligibility requirements:
+
+- Public availability on the Hugging Face Hub, including gated public repositories
+- Safe weight formats such as `safetensors`
+- No unreviewed `trust_remote_code` or unsupported custom execution code
+- Security scanning on Hub artifacts before catalog inclusion
+
+It also stressed that enterprise controls such as private networking, auditability, and access control still depend on the surrounding Microsoft Foundry and Azure environment.
+
+For the maintained version of this material, see [Security and model eligibility](../reference/security-and-eligibility).
diff --git a/docs/source/faq.mdx b/docs/source/faq.mdx
deleted file mode 100644
index b721ec0..0000000
--- a/docs/source/faq.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
-# Frequent Asked Questions (FAQ)
-
-## What is Azure Machine Learning (Azure ML)?
-
-Azure ML is Microsoft’s cloud-native platform for fully managing the ML lifecycle—training, deployment, monitoring, pipelines, AutoML, model registries, and responsible AI tooling—designed for data scientists and ML engineers.
-
-## What is Microsoft Foundry (formerly Azure AI Foundry, and Azure AI Studio before)?
-
-Microsoft Foundry builds on Azure Machine Learning but is tailored specifically for generative AI and agent-based applications. It offers:
-
-* A unified experience for building, evaluating, and deploying LLMs and multimodal agents.
-* Access to a broad catalog of open-source and commercial frontier models—from Azure OpenAI, Hugging Face, Meta, DeepSeek, etc.
-* Integrated tools like model evaluation leaderboards, prompt flows (for RAG), content safety, and agent orchestration.
-
-More information can be found at [What is Microsoft Foundry?](https://learn.microsoft.com/en-us/azure/ai-foundry/what-is-azure-ai-foundry).
-
-## What’s the difference between a **Hub-based project** and a **Foundry (standalone) project**?
-
-| Feature | Hub-based project | Standalone Foundry project |
-|--------|--------------------|-----------------------------|
-| Requires a Hub resource | ✅ Yes—project is linked to a hub | ❌ No—project created individually |
-| Shared infrastructure (compute/quota) | ✅ Yes | ❌ No |
-| Shared security/network settings | ✅ Yes | ❌ No |
-| Shared resource connections | ✅ Yes (e.g., models, storage) | ❌ Per‑project only |
-| Full Generative AI tooling (fine-tuning, evaluation, RAG, agent orchestration) | ✅ Yes | ⚠️ Limited support |
-| Accessible from Azure ML Studio | ✅ Yes | Limited/absent |
-
-Hub-based projects provide **complete** access to generative-AI features; standalone projects operate with **limited** capabilities. Open-model deployments are only accessible through Hub-based project for now.
diff --git a/docs/source/features.mdx b/docs/source/features.mdx
deleted file mode 100644
index 35e278f..0000000
--- a/docs/source/features.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
-# Features & Benefits
-
-1. Extensive Model Catalog Integration
-
- Over 11,000 Hugging Face models, including text, vision, speech, and multimodal models are directly accessible within Microsoft Foundry Hub and Azure Machine Learning Studio for one-click deployment.
-
- Continuous updates ensure day-0 releases of new and trending models from the Hugging Face Hub are available on Azure as soon as they launch.
-
-2. Secure, Scalable, and Managed Deployments
-
- Models can be deployed on managed online endpoints within Azure Machine Learning, providing secure, scalable REST APIs for real-time inference.
-
- Azure's infrastructure supports both CPU and GPU deployments, with features like autoscaling, traffic splitting, and monitoring built in.
-
- Models are scanned for vulnerabilities, and certain model weights are hosted directly on Azure for enhanced security and compliance, including private network deployments with no external egress.
-
-3. Multimodal and Domain-Specific Support
-
- The collaboration covers a wide range of modalities and tasks: text generation, translation, image classification, segmentation, speech recognition, audio classification, and more.
-
- Ongoing expansion includes support for video, 3D, time series, protein folding, and other specialized domains.
-
-4. Enterprise-Grade Infrastructure and Developer Tools
-
- Integration leverages Azure's enterprise-grade infrastructure, including the latest GPU and CPU offerings.
-
- Hugging Face models are optimized for Azure's hardware, ensuring high performance and efficiency, especially for demanding generative AI applications.
-
- Integration with Azure Machine Learning SDK, Azure AI SDK, and Python APIs for seamless automation and scripting.
-
-6. Community and Open-Source Ecosystem
-
- The partnership brings the innovation of Hugging Face's open-source community (nearly 2 million models and 8 million users) to Azure's enterprise customers.
-
- The Hugging Face models are powered by open-source inference engines backed by Transformers, Diffusers, or Sentence Transformers; as well as efficient production-ready solutions such as Text Generation Inference (TGI), vLLM, SGLang and Text Embeddings Inference (TEI), among others to come.
-
-7. Enhanced Security, Compliance, and Monitoring
-
- All models available via Azure are subject to security scans and compliance checks, as the model weights are ensured to be distributed in Safetensors format, scanned with JFrog, Protect AI, and ClamAV, as Hugging Face Security Partners, and Hugging Face's Pickelscan.
-
- Azure's enterprise security features (private endpoints, network isolation, audit trails) are available for Hugging Face model deployments.
-
-## Benefits for Enterprises and Developers
-
-1. Accelerated AI Adoption and Innovation
-
- Rapid access to the latest open-source models and state-of-the-art AI capabilities without the overhead of infrastructure setup or maintenance.
-
- Enables organizations to build, experiment, and iterate on AI solutions faster, keeping pace with the evolving AI landscape.
-
-2. Lower Barriers to Production-Ready AI
-
- Simplifies the deployment of complex models (like Transformers and LLMs) into secure, production environments with minimal configuration.
-
- Reduces the need for specialized DevOps or ML infrastructure expertise.
-
-3. Flexibility and Control
-
- Enterprises retain full control over data, model selection, and deployment environments, supporting both public and private cloud scenarios.
-
-4. Cost and Resource Optimization
-
- Azure's flexible scaling, global availability, and pay-as-you-go pricing help optimize costs for both experimentation and large-scale production.
-
- Efficient resource utilization through auto-scaling and traffic management features.
-
-5. Security and Compliance
-
- Enterprise-grade security, compliance, and privacy controls are built into every stage of the model lifecycle.
-
- Models are vetted for vulnerabilities and can be deployed in isolated environments to meet regulatory requirements.
-
-6. Future-Proofing and Ecosystem Growth
-
- Ongoing collaboration ensures regular updates, support for new modalities, and integration with emerging Azure and Hugging Face features.
-
- Access to both open and proprietary models, as well as tools for building modular, agentic, and composable AI applications.
-
----
-
-This deep integration between Hugging Face and Microsoft Azure empowers organizations to harness the best of open-source AI with the reliability, security, and scalability of Azure's cloud ecosystem.
diff --git a/docs/source/foundry/hardware.mdx b/docs/source/foundry/hardware.mdx
deleted file mode 100644
index 60aa465..0000000
--- a/docs/source/foundry/hardware.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
-# Supported Hardware
-
-## NVIDIA GPUs
-
-Instance Name | GPU Type | GPUs | Total GPU VRAM
---------------------------|------------------|------|----------------
-Standard_NC4as_T4_v3 | NVIDIA TESLA T4 | 1 | 16 GB
-Standard_NC8as_T4_v3 | NVIDIA TESLA T4 | 1 | 16 GB
-Standard_NC16as_T4_v3 | NVIDIA TESLA T4 | 1 | 16 GB
-Standard_NC64as_T4_v3 | NVIDIA TESLA T4 | 4 | 64 GB
-Standard_NC24ads_A100_v4 | NVIDIA A100 80GB | 1 | 80 GB
-Standard_NC40ads_H100_v5 | NVIDIA H100 80GB | 1 | 80 GB
-Standard_NC48ads_A100_v4 | NVIDIA A100 80GB | 2 | 160 GB
-Standard_NC80adis_H100_v5 | NVIDIA H100 80GB | 2 | 160 GB
-Standard_NC96ads_A100_v4 | NVIDIA A100 80GB | 4 | 320 GB
-Standard_ND96asr_v4 | NVIDIA A100 40GB | 8 | 320 GB
-Standard_ND96amsr_A100_v4 | NVIDIA A100 80GB | 8 | 640 GB
-Standard_ND96isr_H100_v5 | NVIDIA H100 80GB | 8 | 640 GB
-Standard_ND96is_H100_v5 | NVIDIA H100 80GB | 8 | 640 GB
-
-More information about those GPU Types / Families can be found in the [Microsoft Azure Documentation - Sizes for virtual machines in Azure - GPU accelerated](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview?tabs=breakdownseries%2Cgeneralsizelist%2Ccomputesizelist%2Cmemorysizelist%2Cstoragesizelist%2Cgpusizelist%2Cfpgasizelist%2Chpcsizelist#gpu-accelerated).
-
-## Intel CPUs
-
-Instance | CPU Model (Family) | vCPUs | RAM (GiB)
------------------|--------------------------------|-------|-----------
-Standard_F2s_v2 | Intel Xeon Platinum 8272CL | 2 | 4
-Standard_DS2_v2 | Intel Xeon E5-2673 v4 / 8272CL | 2 | 7
-Standard_F4s_v2 | Intel Xeon Platinum 8272CL | 4 | 8
-Standard_DS3_v2 | Intel Xeon E5-2673 v4 / 8272CL | 4 | 14
-Standard_E2s_v3 | Intel Xeon Platinum 8272CL | 2 | 16
-Standard_F8s_v2 | Intel Xeon Platinum 8272CL | 8 | 16
-Standard_DS4_v2 | Intel Xeon Platinum 8272CL | 8 | 28
-Standard_E4s_v3 | Intel Xeon 8171M | 4 | 32
-Standard_F16s_v2 | Intel Xeon Platinum 8272CL | 16 | 32
-Standard_DS5_v2 | Intel Xeon Platinum 8272CL | 16 | 56
-Standard_F32s_v2 | Intel Xeon Platinum 8272CL | 32 | 64
-Standard_F48s_v2 | Intel Xeon Platinum 8272CL | 48 | 96
-Standard_E16s_v3 | Intel Xeon Platinum 8272CL | 16 | 128
-Standard_F64s_v2 | Intel Xeon Platinum 8272CL | 64 | 128
-Standard_F72s_v2 | Intel Xeon Platinum 8272CL | 72 | 144
-
-More information about those CPU Models / Families can be found in the [Microsoft Azure Documentation - Sizes for virtual machines in Azure](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview) under the bookmarks [General Purpose](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview?tabs=breakdownseries%2Cgeneralsizelist%2Ccomputesizelist%2Cmemorysizelist%2Cstoragesizelist%2Cgpusizelist%2Cfpgasizelist%2Chpcsizelist#general-purpose) and [Compute Optimized](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview?tabs=breakdownseries%2Cgeneralsizelist%2Ccomputesizelist%2Cmemorysizelist%2Cstoragesizelist%2Cgpusizelist%2Cfpgasizelist%2Chpcsizelist#compute-optimized).
diff --git a/docs/source/foundry/introduction.mdx b/docs/source/foundry/introduction.mdx
deleted file mode 100644
index d1cc049..0000000
--- a/docs/source/foundry/introduction.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
-# Hugging Face on Microsoft Foundry
-
-Hugging Face has partnered with Microsoft to bring open-source models from the [Hugging Face Hub](https://huggingface.co) into [Microsoft Foundry](https://ai.azure.com/) and [Azure Machine Learning](https://ml.azure.com/). The Hugging Face Hub is the home of over 1,700,000 public access open-source models, as well as datasets, spaces and much more. The integration with Microsoft Foundry and Azure Machine Learning enables you to deploy open-source models of your choice to secure and scalable inference infrastructure on Azure powered by Hugging Face and other open-source inference solutions such as Text Generation Inference (TGI), vLLM or SGLang for LLMs and VLMs, or Text Embeddings Inference (TEI) for embeddings, and many more. Now, the Microsoft Foundry and Azure Machine Learning model catalogs are the home for over 11,000 of the most popular and downloaded open-source models on the Hugging Face Hub, ensuring secure and verified weights, that can be deployed to managed online endpoints with ease. Once deployed, the managed online endpoint gives you secure REST API to score your model in real time.
-
-The Microsoft Foundry and Azure Machine Learning model catalogs contain over 11,000 Hugging Face deployable models, ranging a wide-variety of models for different tasks such as image generation, Large Language Models (LLMs), Visual Language Models (VLMs), or embeddings, among many others; all of those powered by open-source inference solutions. Additionally, each of those models can be deployed in a wide variety of hardware available on Microsoft Azure, ranging NVIDIA GPUs to CPUs, so that each model comes with a default suggested hardware.
-
-At Microsoft Build 2025, an expansion of the partnership between Hugging Face and Microsoft Azure was announced. Among the main takeaways, the expanded collaboration will not only cover [Azure Machine Learning](https://azure.microsoft.com/en-us/products/machine-learning), but also [Azure AI Foundry Hub](https://azure.microsoft.com/en-us/products/ai-foundry) allowing Microsoft Azure users to design, customize, and manage AI apps and agents at scale with open-source models from Hugging Face.
-
-
-
-Later that year, at Microsoft Ignite 2025, Azure AI Foundry was renamed to Microsoft Foundry, along with the announcement of a new experience, for a unified Azure platform-as-a-service offering for enterprise AI operations, model builders, and application development.
-
-Read more about Azure AI Foundry evolving into Microsoft Foundry and other announcements at Microsoft Ignite 2025 in the [Microsoft Ignite Book of news](https://news.microsoft.com/ignite-2025-book-of-news/).
-
-## Resources
-
-- [Azure Machine Learning - Deploy models from Hugging Face Hub to Azure Machine Learning online endpoints for real-time inference](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-deploy-models-from-huggingface)
-- [Azure Machine Learning - How to use Open Source foundation models curated by Azure Machine Learning](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-use-foundation-models)
-- [Microsoft and Hugging Face expand collaboration](https://huggingface.co/blog/azure-ai-foundry)
-- [Microsoft and Hugging Face expand collaboration to accelerate Open-Source AI Innovation on Microsoft Foundry](https://devblogs.microsoft.com/foundry/microsoft-and-hugging-face-expand-partnership-to-accelerate-open-source-ai-innovation-on-azure-ai-foundry/)
diff --git a/docs/source/foundry/models.mdx b/docs/source/foundry/models.mdx
deleted file mode 100644
index fef3b22..0000000
--- a/docs/source/foundry/models.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-# Supported Models
-
-Around +11,000 open models from the Hugging Face Hub are available through Microsoft Foundry and Azure Machine Learning. This curated subset of the +2,200,000 public open-models on the Hub includes the most downloaded and relevant models, all compatible with Transformers, Sentence Transformers, Diffusers, and other Hugging Face libraries and solutions.
-
-
-
-Even if you don't have a Microsoft Azure account, you can still explore the [public Hugging Face Collection on Microsoft Foundry](https://ai.azure.com/catalog/publishers/hugging%20face,huggingface).
-
-
-
-This being said, the supported models range different architectures and backends, but a way to identify whether a model from the Hugging Face Hub is made available within the model catalog in Microsoft Foundry and Azure Machine Learning is to either:
-
-1. Navigate to the model card of the given model under https://huggingface.co/models, and check whether the "Deploy" button is available with the "Deploy on Microsoft Foundry" option listed there. If available, the URL pointing to the model on Microsoft Foundry will be provided via the "Go to model on Microsoft Foundry" button. Otherwise, you can request the model's addition by clicking "Request to add" (See [Request a model addition in the Hugging Face collection on Microsoft Foundry](../guides/request-model-addition) for details).
-
-2. On the other hand, you can also navigate to either the Microsoft Foundry (from a Hub-based project) or the Azure Machine Learning model catalogs under the Hugging Face collection, and search the given model. If the model appears, it means it's supported and you can grab the URI pointing to it to programmatically deploy it. Otherwise, you can either [open an issue](https://github.com/huggingface/Microsoft-Azure/issues/new) requesting the model addition, or request it via the Hugging Face Hub model card with the "Request to add" button as mentioned before.
-
-3. Alternatively, you can also check if the given model is available on Microsoft Foundry programmatically with the following Python snippet, that sends a request to an Azure API that given a model ID from the Hugging Face Hub returns either HTTP 200 with the model URL if it's available, or just HTTP 404 if not available.
-
-```python
-import requests
-
-model_id = "HuggingFaceTB/SmolLM3-3B"
-response = requests.get("https://get-azure-ai-url.azurewebsites.net/api/get-azure-ai-url", params={"model_id": model_id})
-if response.status_code == 200:
- print(response.json())
- # {"url": "https://ai.azure.com/explore/models/HuggingFaceTB-SmolLM3-3B/version/6/registry/HuggingFace"}
-```
-
-We are really excited for this partnership between Hugging Face and Microsoft Azure, and working really hard to bring Azure customers the best open models from the Hugging Face collection into Microsoft Foundry and Azure Machine Learning, so stay tuned for updates and a lot more models to come in the following months!
diff --git a/docs/source/foundry/tasks.mdx b/docs/source/foundry/tasks.mdx
deleted file mode 100644
index 54644b1..0000000
--- a/docs/source/foundry/tasks.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
-# Supported Tasks
-
-The following Hugging Face tasks are natively supported on Azure Machine Learning and, so on, on Microsoft Foundry:
-
-- `embeddings` (also known as `feature-extraction`)
-- `sentence-similarity`
-- `text-ranking` (also formerly known as `sentence-ranking`)
-- `automatic-speech-recognition`
-- `text-to-speech` (also formerly known as `text-to-audio`)
-- `speech-to-text`
-- `translation`
-- `text-translation`
-- `question-answering`
-- `text-classification`
-- `fill-mask`
-- `token-classification`
-- `summarization` (also known as `text-summarization`)
-- `text-generation` (also know as either `completions`, `chat-completion`, `text2text-generation` or `conversational`)
-- `image-text-to-text` (also know as `chat-completion` with vision-capabilities)
-- `image-classification`
-- `image-segmentation`
-- `object-detection`
-- `text-to-image`
-- `zero-shot-image-classification`
-- `table-question-answering`
-- `zero-shot-classification`
-- `visual-question-answering`
-- `mask-generation`
-
-With upcoming support for some of the following tasks:
-
-- `image-to-image`
-- `text-to-image` with LoRA
-- `image-feature-extraction`
-- `image-to-text` (also known as `image-captioning`)
-- `text-to-speech`
-- `image-to-3d`
-- `audio-to-audio` (also known as `speech-to-speech`)
-- `text-to-video`
-
-More information about all the supported tasks at [Hugging Face Tasks](https://huggingface.co/tasks).
diff --git a/docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx b/docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx
new file mode 100644
index 0000000..2d6f9c8
--- /dev/null
+++ b/docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx
@@ -0,0 +1 @@
+# Deploy open-models from Microsoft Foundry with Python
diff --git a/docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx b/docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx
new file mode 100644
index 0000000..e379b3e
--- /dev/null
+++ b/docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx
@@ -0,0 +1 @@
+# Deploy open-models from Microsoft Foundry
diff --git a/docs/source/guides/access-gated-models.mdx b/docs/source/guides/access-gated-models.mdx
deleted file mode 100644
index dddfbcf..0000000
--- a/docs/source/guides/access-gated-models.mdx
+++ /dev/null
@@ -1,136 +0,0 @@
-# Deploy Hugging Face gated models on Microsoft Foundry
-
-Some Hugging Face models on Microsoft Foundry are **gated**, meaning you must request access from the model publisher on the Hugging Face Hub before you can deploy them on Foundry. The access request is then tied to your Hugging Face identity and allows you to download the model weights from the Hub.
-
-This guide walks you through how to deploy a Hugging Face gated model on Microsoft Foundry.
-
-## 0. Pre-requisites
-
-To run the guide, you will need to comply with the following pre-requisites:
-
-- An Azure account with an active subscription.
-- The Azure CLI installed and logged in.
-- The Azure Machine Learning extension for the Azure CLI.
-- An Azure Resource Group.
-- A Hub-based project on Microsoft Foundry (classic, i.e., Azure AI Foundry Hub-based project).
-
-For more information, please go through the steps in [Configure Azure Machine Learning and Microsoft Foundry](https://huggingface.co/docs/microsoft-azure/guides/configure-azure-ml-microsoft-foundry).
-
-In this example, the [Azure Machine Learning SDK for Python](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/ml/azure-ai-ml) will be used to create the endpoint and the deployment. Along with it, you will also need to install `azure-identity` to authenticate with your Azure credentials via Python.
-
-```bash
-pip install azure-ai-ml azure-identity --upgrade --quiet
-```
-
-Then, setting the following environment variables is recommended as those will be used along the example for the Azure ML Client, so make sure to update and set those values accordingly.
-
-```bash
-env LOCATION eastus
-env SUBSCRIPTION_ID
-env RESOURCE_GROUP
-env WORKSPACE_NAME
-```
-
-You also need to define both the endpoint and deployment names. Those will be used throughout the example.
-
-> Endpoint names must to be globally unique per region i.e., even if you don't have any endpoint named that way running under your subscription, if the name is reserved by another Azure customer, then you won't be able to use the same name. Adding a timestamp or a custom identifier is recommended to prevent running into HTTP 400 validation issues when trying to deploy an endpoint with an already locked / reserved name. Also the endpoint name must be between 3 and 32 characters long.
-
-```python
-import os
-from uuid import uuid4
-
-os.environ["ENDPOINT_NAME"] = f"endpoint-{str(uuid4())[:8]}"
-os.environ["DEPLOYMENT_NAME"] = f"deployment-{str(uuid4())[:8]}"
-```
-
-## 1. Identify a gated model in the catalog
-
-When you select a model from the Microsoft Foundry catalog under the Hugging Face collection, if the model is gated, you will see a banner at the top mentioning a **Gated Model Access** is required, as well as the `isGated` property set.
-
-## 2. Request access on Hugging Face
-
-In the model page for the gated model on Microsoft Foundry you will see a link to the model on the Hugging Face Hub. If you then go to the Hub, you can **Request access** / **Agree and access repository** action (wording varies by model). Finally, you need to wait for approval from the model authors or organization in charge.
-
-Note that some models approve instantly; others require review that can take up to a day.
-
-## 3. Create a Hugging Face Token
-
-You can manage your access tokens in your Hugging Face account settings. Create a fine-grained token with `Read access to contents of all public gated repositories you can access` selected [here](https://huggingface.co/settings/tokens/new?canReadGatedRepos=true&tokenType=fineGrained).
-
-> For organizations seeking stronger oversight on their user’s token, [Hugging Face Team and Enterprise Plans](https://huggingface.co/enterprise) offer enhanced token governance capabilities to companies.
-
-## 4. Create an Azure Machine Learning Connection with Custom keys
-
-Create a **Custom keys** workspace connection with your Hugging Face Token. This connection is how the deployment process authenticates to the Hugging Face Hub to validate access and download the gated model.
-
-```bash
-az ml connection create \
- --name HuggingFaceTokenConnection \
- --type "Generic" \
- --resource-group $RESOURCE_GROUP \
- --workspace-name $WORKSPACE_NAME \
- --secret "HF_TOKEN="
-```
-
-### 5. Create the Managed Online Endpoint with secret-store access enabled
-
-First you need to authenticate into the Microsoft Foundry via Azure Machine Learning with the Python SDK:
-
-```bash
-import os
-from azure.ai.ml import MLClient
-from azure.identity import DefaultAzureCredential
-
-client = MLClient(
- credential=DefaultAzureCredential(),
- subscription_id=os.getenv("SUBSCRIPTION_ID"),
- resource_group_name=os.getenv("RESOURCE_GROUP"),
- workspace_name=os.getenv("WORKSPACE_NAME"),
-)
-```
-
-Then, when creating the Managed Online Endpoint for the deployment, ensure the endpoint is configured to allow access to default secret stores. this is what allows the Managed Online Endpoint in Azure Machine Learning to read the Connection Secret. It can only be done programmatically for now.
-
-```python
-from azure.ai.ml.entities import ManagedOnlineEndpoint
-
-endpoint = ManagedOnlineEndpoint(
- name=os.getenv("ENDPOINT_NAME"),
- properties={"enforce_access_to_default_secret_stores": "enabled"},
-)
-
-client.begin_create_or_update(endpoint).wait()
-```
-
-This allows the endpoint deployment to read the secret connection value (your token) at deployment time.
-
-### 6. Create the Managed Online Deployment
-
-After creating the endpoint, you need to create the [ManagedOnlineDeployment via the Azure ML Python SDK](https://learn.microsoft.com/en-us/python/api/azure-ai-ml/azure.ai.ml.entities.managedonlinedeployment?view=azure-python) i.e., create a deployment linked to the given endpoint.
-
-To create the Azure Machine Learning Managed Online Endpoint you don't need to provide the model ID on the Hugging Face Hub but rather the model URI on Azure Machine Learning formatted as follows:
-
-```python
-model_id = "facebook/sam3" # example gated model
-
-model_uri = f"azureml://registries/HuggingFace/models/{model_id.replace('/', '-').replace('_', '-').lower()}/labels/latest"
-model_uri
-```
-
-Make sure to select the instance type recommended for the model you want to deploy. You can find it in the model catalog deploy page.
-
-```python
-from azure.ai.ml.entities import ManagedOnlineDeployment
-
-deployment = ManagedOnlineDeployment(
- name=os.getenv("DEPLOYMENT_NAME"),
- endpoint_name=os.getenv("ENDPOINT_NAME"),
- model=model_uri,
- instance_type="Standard_NC40ads_H100_v5",
- instance_count=1,
-)
-
-client.online_deployments.begin_create_or_update(deployment).wait()
-```
-
-That's it, you deployed your first Hugging Face gated model on Microsoft Foundry!
\ No newline at end of file
diff --git a/docs/source/guides/configure-azure-ml-microsoft-foundry.mdx b/docs/source/guides/configure-azure-ml-microsoft-foundry.mdx
deleted file mode 100644
index 6ba9e34..0000000
--- a/docs/source/guides/configure-azure-ml-microsoft-foundry.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
-# Configure Azure Machine Learning and Microsoft Foundry
-
-
-
-Throughout this guide you'll see references to both Azure AI Foundry and Microsoft Foundry simultaneously, but that's because Microsoft Foundry has superseded Azure AI Foundry, but still referencing to it for the "classic" experience, which is the one that supports Hub-based projects and then, models from the Hugging Face Hub.
-
-
-
-This guide explains how to configure Azure Machine Learning and Microsoft Foundry in your Microsoft Azure subscription. These pre-requisites are required to run the Microsoft Foundry examples in this documentation, as well as any example on Azure Machine Learning.
-
-You can either follow along the below steps, or either read more about those in the [Azure Machine Learning Tutorial: Create resources you need to get started](https://learn.microsoft.com/en-us/azure/machine-learning/quickstart-create-resources?view=azureml-api-2).
-
-Also note that the steps below will use the `az` CLI i.e., the Azure CLI, but there are other alternatives such as e.g. the Azure SDK for Python, or even the Azure Portal, so pick the one you feel more comfortable with.
-
-## Azure Account
-
-A Microsoft Azure account with an active subscription. If you don't have a Microsoft Azure account, you can now [create one for free](https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account), including 200 USD worth of credits to use within the next 30 days after the account creation.
-
-## Azure CLI
-
-The Azure CLI (`az`) installed on the instance that you're running this example on, see [the installation steps](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest), and follow the steps of the preferred method based on your instance. Then log in into your subscription as follows:
-
-```bash
-az login
-```
-
-More information at [Sign in with Azure CLI - Login and Authentication](https://learn.microsoft.com/en-us/cli/azure/authenticate-azure-cli?view=azure-cli-latest).
-
-## Azure CLI extension for Azure Machine Learning
-
-Besides the Azure CLI (`az`), you also need to install the Azure Machine Learning CLI extension (`az ml`) which will be used to create the Azure Machine Learning and Microsoft Foundry required resources.
-
-First you will need to list the current extensions and remove any `ml`-related extension before installing the latest one i.e., v2.
-
-```bash
-az extension list
-az extension remove --name azure-cli-ml
-az extension remove --name ml
-```
-
-Then you can install the `az ml` v2 extension as follows:
-
-```bash
-az extension add --name ml
-```
-
-More information at [Azure Machine Learning (ML) - Install and setup the CLI (v2)](https://learn.microsoft.com/en-us/azure/machine-learning/how-to-configure-cli?view=azureml-api-2&tabs=public).
-
-## Azure Resource Group
-
-An Azure Resource Group under the one you will create the Microsoft Foundry (classic) i.e., an Azure AI Foundry Hub-based project (note it will create an Azure AI Foundry resource as an Azure Machine Learning Workspace, but not the other way around, meaning that the Azure AI Foundry Hub will be listed as an Azure Machine Learning workspace, but leveraging the Microsoft Foundry capabilities for Gen AI), and the rest of the required resources. If you don't have one, you can create it as follows:
-
-```bash
-az group create --name huggingface-azure-rg --location eastus
-```
-
-Then, you can ensure that the resource group was created successfully by e.g. listing all the available resource groups that you have access to on your subscription:
-
-```bash
-az group list --output table
-```
-
-More information at [Manage Azure resource groups by using Azure CLI](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-cli).
-
-
-
-You can also create the Azure Resource Group [via the Azure Portal](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/manage-resource-groups-portal), or [via the Azure Resource Management Python SDK](https://learn.microsoft.com/en-us/azure/developer/python/sdk/examples/azure-sdk-example-resource-group?tabs=bash) (requires it to be installed as `pip install azure-mgmt-resource` in advance).
-
-
-
-## Azure AI Foundry Hub-based project
-
-An Azure AI Foundry Hub-based project (given that the new experience on Microsoft Foundry does not yet support Hugging Face models, but rather only the classic experience which is the same as saying Azure AI Foundry) under the aforementioned subscription and resource group. If you don't have one, you can create it as follows:
-
-```bash
-az ml workspace create \
- --kind hub \
- --name huggingface-azure-hub \
- --resource-group huggingface-azure-rg \
- --location eastus
-```
-
-
-
-Note that the main difference with an standard Azure Machine Learning Workspace is that the Microsoft Foundry (classic) i.e., Azure AI Foundry Hub, requires you to specify the `--kind hub`, removing it would create a standard Azure Machine Learning Workspace instead, so you wouldn't benefit from the features that the Microsoft Foundry brings. But, when you create an Azure AI Foundry Hub, you can still benefit from all the features that Azure Machine Learning brings, since Microsoft Foundry will still rely on Azure Machine Learning, but not the other way around.
-
-
-
-Then, you can ensure that the workspace was created successfully by e.g. listing all the available workspaces that you have access to on your subscription:
-
-```bash
-az ml workspace list --filtered-kinds hub --query "[].{Name:name, Kind:kind}" --resource-group huggingface-azure-rg --output table
-```
-
-
-
-The `--filtered-kinds` argument has been recently included as of [Azure Machine Learning CLI 2.37.0](https://learn.microsoft.com/en-us/azure/machine-learning/azure-machine-learning-release-notes-cli-v2?view=azureml-api-2#azure-machine-learning-cli-v2-v-2370), meaning that you may need to upgrade `az ml` as `az extension update --name ml`.
-
-
-
-Once the Azure AI Foundry Hub-based project is created, you need to create an Azure AI Foundry project linked to that Hub, to do so you first need to obtain the Azure AI Foundry Hub ID of the recently created Hub as follows (replace the resource names with yours):
-
-```bash
-az ml workspace show \
- --name huggingface-azure-hub \
- --resource-group huggingface-azure-rg \
- --query "id" \
- -o tsv
-```
-
-That command will provide the ID as follows `/subscriptions//resourceGroups//providers/Microsoft.MachineLearningServices/workspaces/huggingface-azure-hub`, meaning that you can also format it manually yourself with the appropriate replacements. Then you need to run the following command to create the Microsoft Foundry Project for that Hub as:
-
-```bash
-az ml workspace create \
- --kind project \
- --hub-id $(az ml workspace show --name huggingface-azure-hub --resource-group huggingface-azure-rg --query "id" -o tsv) \
- --name huggingface-azure-project \
- --resource-group huggingface-azure-rg \
- --location eastus
-```
-
-Finally, you can verify that it was correctly created with the following command:
-
-```bash
-az ml workspace list --filtered-kinds project --query "[].{Name:name, Kind:kind}" --resource-group huggingface-azure-rg --output table
-```
-
-More information at [How to create and manage an Azure AI Foundry Hub](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/create-azure-ai-resource?tabs=portal) and at [How to create a Hub using the Azure CLI](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/develop/create-hub-project-sdk?tabs=azurecli).
-
-
-
-You can also create the Azure AI Foundry Hub [via the Azure Portal](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/create-secure-ai-hub), or [via the Azure Machine Learning Python SDK](https://learn.microsoft.com/en-us/azure/ai-foundry/how-to/develop/create-hub-project-sdk?tabs=python), among other options listed in [Manage AI Hub Resources](https://learn.microsoft.com/en-us/azure/ai-foundry/concepts/ai-resources).
-
-
diff --git a/docs/source/guides/introduction.mdx b/docs/source/guides/introduction.mdx
deleted file mode 100644
index 901e92e..0000000
--- a/docs/source/guides/introduction.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-# Guides
-
-Take a look at our guides on how to get started with Hugging Face models on Microsoft Foundry.
-
-- [Deploy Hugging Face Models in Foundry with Managed Compute](./managed-compute-foundry)
-- [One-click deployments from the Hugging Face Hub on Microsoft Foundry](./one-click-deployment-foundry)
-- [Deploy Hugging Face gated models on Microsoft Foundry](./access-gated-models)
-- [Request a model addition in the Hugging Face collection on Microsoft Foundry](./request-model-addition)
-- [Configure Azure Machine Learning and Microsoft Foundry](./configure-azure-ml-microsoft-foundry)
-
-For more detailed examples please check the "Examples" section under each service.
diff --git a/docs/source/guides/managed-compute-foundry.mdx b/docs/source/guides/managed-compute-foundry.mdx
deleted file mode 100644
index 6088541..0000000
--- a/docs/source/guides/managed-compute-foundry.mdx
+++ /dev/null
@@ -1,175 +0,0 @@
-# Deploy Hugging Face Models in Foundry with Managed Compute
-
-
-
-Managed compute in Microsoft Foundry is currently in **Public Preview**, expect no SLA for the time being.
-
-
-
-Managed compute is a deployment type in Microsoft Foundry that hosts open-source models from the Hugging Face collection on dedicated GPU capacity, without requiring you to provision virtual machines, operate a Kubernetes cluster, or build and patch your own container images. Microsoft owns the GPU topology, the serving runtime (vLLM, SGLang, TEI, and more depending on the model), the container image, and security patching. You choose the model, a deployment template, the accelerator family (NVIDIA A100, NVIDIA H100, or AMD MI300X), and how many instances to run.
-
-Managed compute deployments live behind the same unified Foundry Routing Endpoint, authentication (Microsoft Entra ID or API key), SDKs, and observability surface as any other Foundry deployment, so switching from a pay-per-token model to an open-source one is just a change of the `model` field in your requests.
-
-This guide walks you through discovering a Hugging Face model in the Foundry catalog, deploying it with managed compute, and sending inference requests.
-
-To see managed compute in action, watch the deep-dive session from Microsoft Build 2026, [Hugging Face open-source models to production on Microsoft Foundry](https://build.microsoft.com/en-US/sessions/DEM320):
-
-
-
-## Prerequisites
-
-- An Azure account with an active subscription and a [Microsoft Foundry](https://ai.azure.com/) project. If you don't have one yet, see [Configure Azure Machine Learning and Microsoft Foundry](./configure-azure-ml-microsoft-foundry).
-- The following role assignments on the Foundry account scope:
- - **Cognitive Services Contributor** (or **Foundry Owner** / **Foundry Account Owner**) to create, update, and delete managed compute deployments.
- - **Foundry User** to call the deployment with Microsoft Entra ID from the Playground, SDK, or REST.
-- Approved managed compute quota for the accelerator family you plan to deploy on (A100, H100, or MI300X) in your target region. Managed compute quota is separate from Azure VM quota; see [Request more quota](#request-more-quota) below.
-- If you plan to deploy via the Python SDK, install the management and inference clients:
-
-```bash
-pip install azure-mgmt-cognitiveservices azure-identity openai --upgrade --quiet
-```
-
-## 1. Find a model in the catalog
-
-Managed compute deploys models from the **Hugging Face Collection** in the Foundry model catalog from the `azure-huggingface` registry.
-
-1. Open the [Foundry portal](https://ai.azure.com/nextgen), make sure the New Foundry toggle is on, and go to **Discover** > **Models**.
-2. In the **Collections** filter, select **Hugging Face**. Use the other filters (model family, modality, task) or the search box to narrow down the model you want.
-3. In the **Deployment options** filter, select **Managed compute** to only show models available for this deployment type.
-4. Select a model card to open its details.
-
-
-
-The model card shows the upstream license, modality, supported tasks, and the deployment templates published for the model. If you plan to deploy via the Python SDK or REST instead of the portal wizard, note down the following values from the model card and the deployment wizard:
-
-- **Model ID**, the fully qualified registry asset ID, for example:
-
- ```
- azureml://registries/azure-huggingface/models/qwen--qwen3-32b/versions/3
- ```
-
-- **Deployment template ID**, which pins the runtime, accelerator family and count, and context length, for example:
-
- ```
- azureml://registries/azure-huggingface/deploymenttemplates/qwen--qwen3-32b--40k-nvidia-h100/labels/latest
- ```
-
-- **Accelerator type**, for example `H100_80GB`, `A100_80GB`, or `MI300_192GB`, shown next to each template in the deployment wizard.
-
-| Template | Runtime | Accelerator | Context |
-| --- | --- | --- | --- |
-| qwen–qwen3-32b–40k-nvidia-a100 | vLLM | 1 × A100 80 GB | 40K |
-| qwen–qwen3-32b–40k-nvidia-h100 | vLLM | 1 × H100 80 GB | 40K |
-| qwen–qwen3-32b–128k-nvidia-2xa100 | vLLM | 2 × A100 80 GB | 128K |
-| qwen–qwen3-32b–128k-nvidia-2xh100 | vLLM | 2 × H100 80 GB | 128K |
-
-A model and a deployment template must be compatible; the portal wizard only shows templates published for the model you selected.
-
-## 2. Deploy the model
-
-On the model card, select **Deploy** to open the deployment wizard:
-
-1. Enter a **Deployment name**. This is what your application passes in the `model` field at inference time, so pick a stable, application-friendly name (for example, `qwen3-32b`).
-2. Select the **Deployment template** that matches your workload, for example the H100 single-accelerator template for lower cost, or a two-accelerator template for a longer context length.
-3. Select the **Accelerator type**.
-4. Set **Model instances** to `1` to start. You can scale out later by increasing the instance count.
-5. Acknowledge the deployment cost and select **Deploy**. Provisioning typically takes 10 to 15 minutes.
-
-
-
-Alternatively, deploy the same model with the Python SDK. Replace the placeholders with your subscription ID, resource group, Foundry account name, and the model and template IDs from the previous step.
-
-```python
-from azure.identity import DefaultAzureCredential
-from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
-
-SUBSCRIPTION_ID = ""
-RESOURCE_GROUP = ""
-ACCOUNT_NAME = ""
-DEPLOYMENT_NAME = "qwen3-32b"
-
-MODEL = "azureml://registries/azure-huggingface/models/qwen--qwen3-32b/versions/3"
-TEMPLATE = "azureml://registries/azure-huggingface/deploymenttemplates/qwen--qwen3-32b--40k-nvidia-h100/labels/latest"
-
-client = CognitiveServicesManagementClient(DefaultAzureCredential(), SUBSCRIPTION_ID)
-
-deployment = client.managed_compute_deployments.begin_create_or_update(
- resource_group_name=RESOURCE_GROUP,
- account_name=ACCOUNT_NAME,
- deployment_name=DEPLOYMENT_NAME,
- resource={
- "sku": {"name": "GlobalManagedCompute", "capacity": 1},
- "properties": {
- "model": MODEL,
- "deploymentTemplate": TEMPLATE,
- "acceleratorType": "H100_80GB",
- "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
- },
- },
-).result() # blocks until terminal state (~10-15 min)
-
-print(f"State: {deployment.properties.provisioning_state}")
-```
-
-## 3. Send a test request
-
-Once the deployment's provisioning state is `Succeeded`, you can test it interactively from the **Chat Playground** tab on the deployment details page, or call it from code through the unified Foundry endpoint:
-
-```
-https://.services.ai.azure.com/openai/v1/
-```
-
-The `model` field in the request body takes the **deployment name** you chose, not the model ID.
-
-```python
-from azure.identity import DefaultAzureCredential, get_bearer_token_provider
-from openai import OpenAI
-
-RESOURCE = ""
-DEPLOYMENT_NAME = "qwen3-32b"
-
-token_provider = get_bearer_token_provider(
- DefaultAzureCredential(),
- "https://cognitiveservices.azure.com/.default",
-)
-
-client = OpenAI(
- base_url=f"https://{RESOURCE}.services.ai.azure.com/openai/v1",
- api_key=token_provider(),
-)
-
-response = client.chat.completions.create(
- model=DEPLOYMENT_NAME,
- messages=[{"role": "user", "content": "What is the capital of France?"}],
-)
-
-print(response.choices[0].message.content)
-```
-
-Calling the deployment with Microsoft Entra ID requires the **Foundry User** role on the Foundry account. You can alternatively authenticate with the account API key by passing `api_key=` to the `OpenAI` client.
-
-## Scale, monitor, and delete the deployment
-
-Because managed compute deployments are model-centric, you scale by changing the number of model instances rather than sizing a node. Increase `sku.capacity` and call `begin_create_or_update` again to scale out.
-
-Managed compute deployments emit metrics on the same Azure Monitor surface as other Foundry deployments, including request counts by status code, latency percentiles, and, for chat-completion models, token usage and time-to-first-token. Open the deployment in the [Azure portal](https://portal.azure.com/) under **Metrics** to chart these and configure alerts.
-
-To delete a deployment and release its accelerator allocation:
-
-```python
-client.managed_compute_deployments.begin_delete(
- resource_group_name=RESOURCE_GROUP,
- account_name=ACCOUNT_NAME,
- deployment_name=DEPLOYMENT_NAME,
-).result()
-```
-
-## Request more quota
-
-Managed compute quota is granted per accelerator family per region and is **separate from Azure VM quota**; existing VM quota can't be applied to a managed compute deployment. To request more:
-
-1. In the Foundry portal, go to **Operate** > **Quota**.
-2. Select the **Managed compute** tab to see current allocations grouped by accelerator family and region.
-3. Select **Request quota**, choose the accelerator family (A100, H100, or MI300X) and target region, and submit the request.
-
-Allow up to 15 minutes for an approved quota change to propagate.
diff --git a/docs/source/guides/one-click-deployment-foundry.mdx b/docs/source/guides/one-click-deployment-foundry.mdx
deleted file mode 100644
index 32b43b7..0000000
--- a/docs/source/guides/one-click-deployment-foundry.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
-# One-click deployments from the Hugging Face Hub on Microsoft Foundry
-
-This guide introduces the Hugging Face Hub and Microsoft Foundry one-click deployment experience for open-source models as Azure Machine Learning Managed Online Endpoints for real-time inference.
-
-TL;DR The Hugging Face Hub is a collaborative platform hosting over a million open-source machine learning models, datasets, and demos. It supports a wide range of tasks across natural language processing, vision, and audio, and provides version-controlled repositories with metadata, model cards, and programmatic access via APIs and popular ML libraries. Microsoft Foundry builds on Azure Machine Learning but is tailored specifically for generative AI and agent-based applications. Azure Machine Learning is a cloud-based platform for building, deploying, and managing machine learning models at scale. It provides managed infrastructure, including powerful CPU and GPU instances, automated scaling, secure endpoints, and monitoring, making it suitable for both experimentation and production deployment.
-
-The integration between Hugging Face Hub and Microsoft Foundry and Azure Machine Learning allows users to deploy thousands of Hugging Face models directly onto Azure's managed infrastructure with minimal configuration. This is achieved through a native model catalog in Microsoft Foundry and Azure Machine Learning Studio, which features Hugging Face models ready for real-time deployment.
-
-The steps required to deploy an open-source model from the Hugging Face Hub to Microsoft Foundry as an Azure Machine Learning Managed Online Endpoint for real-time inference are the following:
-
-1. Go to the [Hugging Face Hub Models page](https://huggingface.co/models), and browse all the open-source models available on the Hub.
-
-
-
- Alternatively, you can also start directly from the [Hugging Face Collection on Microsoft Foundry (public URL, no authentication required)](https://ai.azure.com/catalog/publishers/hugging%20face,huggingface), or from the [Hugging Face Collection on Microsoft Foundry (requires Azure authentication)](https://ai.azure.com/explore/models?selectedCollection=Hugging+Face) instead of the Hugging Face Hub, and just explore the available models using the Microsoft Foundry model catalog filters to deploy the models that you want.
-
-
-
-2. Leverage the Hub filters to easily find and discover new models based on the filters as e.g. task type, size based in number of parameters, inference engine support, and much more.
-
-3. Select the model that you want, and within its model card click on the "Deploy" button. Then select the option "Deploy on Microsoft Foundry", and click on "Go to model in Microsoft Foundry". Note that the "Deploy" button may be unavailable for some models, indicating they cannot be deployed. In other cases, the "Deploy on Microsoft Foundry" option may not appear, meaning the model is not supported by any of the inference engines or tasks available in Microsoft Foundry. If the option appears as "Request to add", the model is not yet available but can be requested for its addition in the Hugging Face collection within the Microsoft Foundry model catalog.
-
-4. On Microsoft Foundry Foundry, you will be redirected to the model card. Once there, click "Use this model" and fill the configuration values for the endpoint and the deployment, such as the endpoint name, the instance type, or the instance count, among others; then click "Deploy".
-
-5. After the endpoint is created and the deployment is ready, you will be able to send requests to the deployed API. For more information on how to send inference requests to it, you can either check the "Consume" tab within the Azure Machine Learning Endpoint in Microsoft Foundry Foundry, or check any of the available Microsoft Foundry examples on the documentation.
-
-
diff --git a/docs/source/guides/request-model-addition.mdx b/docs/source/guides/request-model-addition.mdx
deleted file mode 100644
index a3b88ca..0000000
--- a/docs/source/guides/request-model-addition.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
-# Request a model addition in the Hugging Face collection on Microsoft Foundry
-
-At the moment the Hugging Face collection on Microsoft Foundry and Azure Machine Learning contains +11,000 open models from the Hugging Face Hub, leveraging open-source inference solutions such as Text Generation Inference (TGI), vLLM, SGLang, Text Embeddings Inference (TEI), Transformers, Diffusers, Sentence Transformers, among many others.
-
-
-
-Alternatively, you can also [open an issue](https://github.com/huggingface/Microsoft-Azure/issues/new) with the model or models you'd like to see on the Hugging Face collection on Microsoft Foundry and Azure Machine Learning.
-
-Before requesting a model addition, you need to make sure that the model or models match the following criteria:
-
-- Have any of the `Transformers`, `Diffusers` or `Sentence-Transformers` tags on the Hugging Face Hub, meaning that the model architecture is compatible with any of those. If the model you'd like to see in the collection doesn't match this criteria, you can maybe check the [Contributing a new model to Transformers](https://huggingface.co/docs/transformers/main/en/modular_transformers) guide on how to add new modular-based model architectures into Transformers.
-
-- Make sure that the `pipeline_tag` tag i.e., the task, is any of the supported tasks as per [Microsoft Foundry - Supported Tasks](../foundry/tasks). If it's not there nor listed among the upcoming tasks, then feel free to [open an issue](https://github.com/huggingface/Microsoft-Azure/issues/new) requesting the support for that task. Again, as per the point above, it needs to be a `Transformers`, `Diffusers`, or `Sentence-Transformers` compatible task.
-
-- If you want to benefit from the production-like inference solutions and the OpenAI-compatible interfaces for text generation and embeddings, you should also make sure that the given model has either the `text-generation-inference` (shortened as `tgi`), `vllm` and/or `sglang` tags, or `text-embeddings-inference` (shortened as `tei`), respectively.
-
-- There might be some cases where neither the "Deploy" nor "Deploy on Microsoft Foundry" buttons are enabled for a given model, in that case feel free to [open an issue](https://github.com/huggingface/Microsoft-Azure/issues/new) sharing the URL to the model on the Hugging Face Hub, so that we can help fix the metadata if applicable.
-
-- The Hugging Face Hub models MUST be public (including gated models), as private models won't be considered at the moment.
-
-- The Hugging Face Hub models with `trust_remote_code` or `custom_code` tags are not allowed for security reasons, unless manually verified or coming from an already verified organization e.g. `microsoft`.
-
-- And finally, the model weights need to be in Safetensors format and have passed the JFrog, ClamAV, and the rest of the security checks performed in the Hugging Face Hub. More information in [Malware scanning](https://huggingface.co/docs/hub/en/security-malware).
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index f64339c..6c00fe0 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -1,11 +1,50 @@
-# Hugging Face on Microsoft Azure
+# Hugging Face on Microsoft Foundry

-Hugging Face collaborates with Microsoft Azure across open science, open source, and cloud, to enable companies to build their own AI with the latest open models from Hugging Face and the latest infrastructure features from Microsoft Azure.
+Hugging Face and Microsoft work together to make open models easier to discover and deploy on Microsoft Foundry. The Hugging Face collection in Foundry brings a large catalog of open models into the Foundry experience so teams can deploy them from the UI or from Python without building the full serving stack themselves.
-Hugging Face enables new experiences for Microsoft Azure customers, allowing them to [deploy models on their Microsoft Azure infrastructure directly from the Hugging Face Hub via one-click deployments](./guides/one-click-deployment-foundry) in a secure and scalable way, as well as from either the Microsoft Foundry or the Azure Machine Learning model catalog, or even programmatically via the Azure CLI or the Python SDK.
+With Hugging Face on Microsoft Foundry, you can:
-This collaboration aims to offer developers access to an everyday growing catalog of open-source models from the Hugging Face Hub, using Hugging Face open-source libraries across a broad spectrum of Microsoft Azure services and hardware platforms.
+- Discover open models from the Hugging Face catalog directly in Microsoft Foundry.
+- Deploy supported models from the UI or programmatically from Python.
+- Use the resulting deployments behind Foundry-managed endpoints.
+- Build applications, agents, and examples on top of those deployments.
-By combining Hugging Face's open-source models, libraries and solutions with Microsoft Azure's scalable and secure cloud services, developers can more easily and affordably incorporate advanced AI capabilities into their applications.
+## Microsoft Foundry
+
+The Hugging Face collection is available from the Foundry model catalog, where you can filter models by family, modality, task, and deployment option before starting a deployment.
+
+
+
+Once a deployment is ready, you can call it through the Foundry endpoint with a standard OpenAI-compatible client:
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://.services.ai.azure.com/openai/v1/",
+ api_key="",
+)
+
+response = client.chat.completions.create(
+ model="",
+ messages=[{"role": "user", "content": "Hello from Microsoft Foundry."}],
+)
+```
+
+## Where to start?
+
+Before deploying a model from Microsoft Foundry, you will usually need:
+
+- An Azure subscription
+- A Microsoft Foundry project
+- Permission to create deployments in that project
+- Enough quota in the target region for the hardware you want to use
+
+Start with the Getting started section:
+
+- [Deploy open-models from Microsoft Foundry with Python](./get-started/deploy-open-models-from-microsoft-foundry-with-python)
+ This will cover the prerequisites and a simple programmatic deployment flow.
+- [Deploy open-models from Microsoft Foundry](./get-started/deploy-open-models-from-microsoft-foundry)
+ This will cover the equivalent flow from the Foundry UI.
diff --git a/docs/source/large-language-models/introduction.mdx b/docs/source/large-language-models/introduction.mdx
new file mode 100644
index 0000000..2137d53
--- /dev/null
+++ b/docs/source/large-language-models/introduction.mdx
@@ -0,0 +1 @@
+# Large Language Models
diff --git a/docs/source/security.mdx b/docs/source/security.mdx
deleted file mode 100644
index fd70cea..0000000
--- a/docs/source/security.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
-# Security & Compliance
-
-In addition to the enterprise-grade features available in Microsoft Azure services, the following security measures and requirements are enforced to safeguard the deployment and use of open models on Azure:
-
-## Model Eligibility Requirements
-
-Only models that meet strict security criteria are included in the Hugging Face collection on Microsoft Foundry and Azure Machine Learning:
-
-- **Public availability:** Models must be public on the [Hugging Face Hub](https://huggingface.co/models), even if gated; private models are currently not eligible.
-
-- **`trust_remote_code` and `custom_code` not allowed:** Models that require `trust_remote_code=True` are disallowed unless they are explicitly verified by Hugging Face or come from a trusted/verified organization e.g. `microsoft`.
-
-- **Secure format:** Model weights must be uploaded in the [Safetensors](https://github.com/huggingface/safetensors) format to eliminate the risks associated with pickle-based formats.
-
-## Mandatory Security Scanning
-
-All models made available via the Hugging Face collection on Microsoft Foundry and Azure Machine Learning undergo a robust set of security scans like [ClamAV malware scanning](https://huggingface.co/docs/hub/en/security-malware), including third-party scanners such as [Protect AI](https://huggingface.co/docs/hub/en/security-protectai) and [JFrog](https://huggingface.co/docs/hub/en/security-jfrog) solutions.
-
-These checks help identify embedded malware or harmful binaries, unsafe deserialization, unintended external connections and security-sensitive content in model artifacts before being imported in customers' tenancy.
-
-For more details on Hugging Face Hub's security practices and tooling, refer to [Hugging Face Hub Security](https://huggingface.co/docs/hub/en/security).
-
-## Network Isolation and Compliance
-
-For enhanced protection and compliance, model hosting and serving can be configured to run in isolated compute environments on Microsoft Foundry and Azure Machine Learning, aligned with regulatory or internal policy requirements. Azure Foundry and Azure ML comes with enterprise-grade audit, logging, and access control frameworks that ensures full traceability and governance.
From e0aed53cb189ab259c4d6fac602f4e7691d16434 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 5 Aug 2026 13:07:16 +0200
Subject: [PATCH 02/17] Fix file names for `docs/source/get-started/...`
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
...dx => deploy-open-models-on-microsoft-foundry-with-python.mdx} | 0
...ft-foundry.mdx => deploy-open-models-on-microsoft-foundry.mdx} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename docs/source/get-started/{deploy-open-models-from-microsoft-foundry-with-python.mdx => deploy-open-models-on-microsoft-foundry-with-python.mdx} (100%)
rename docs/source/get-started/{deploy-open-models-from-microsoft-foundry.mdx => deploy-open-models-on-microsoft-foundry.mdx} (100%)
diff --git a/docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
similarity index 100%
rename from docs/source/get-started/deploy-open-models-from-microsoft-foundry-with-python.mdx
rename to docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
diff --git a/docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
similarity index 100%
rename from docs/source/get-started/deploy-open-models-from-microsoft-foundry.mdx
rename to docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
From 05418e24a731bcbe4472f3616a5b109c988436f4 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Thu, 13 Aug 2026 21:52:28 +0200
Subject: [PATCH 03/17] Add `harness/hermes-agent.mdx` (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 3 +++
docs/source/harness/hermes-agent.mdx | 35 ++++++++++++++++++++++++++++
2 files changed, 38 insertions(+)
create mode 100644 docs/source/harness/hermes-agent.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index d0acc6a..0792f5e 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -12,6 +12,9 @@
- local: agents/introduction
title: Agents
title: Agents
+ - local: harness/hermes-agent
+ title: Hermes Agent (Coming soon)
+ title: Harness
- sections:
- local: large-language-models/introduction
title: Large Language Models
diff --git a/docs/source/harness/hermes-agent.mdx b/docs/source/harness/hermes-agent.mdx
new file mode 100644
index 0000000..e527d82
--- /dev/null
+++ b/docs/source/harness/hermes-agent.mdx
@@ -0,0 +1,35 @@
+# Hermes Agent
+
+
+
+[Hermes Agent](https://hermes-agent.nousresearch.com/) is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.
+
+You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
+
+```bash
+curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
+```
+
+Or on Windows as:
+
+```bash
+irm https://hermes-agent.nousresearch.com/install.ps1 | iex
+```
+
+Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
+
+
+
+Alternatively, from the desktop application you can also open the settings and click on "Providers -> Custom Endpoints" and create the endpoint with the deployed model, then set the following:
+
+- Name and Provider ID set to "Microsoft Foundry" and "microsoft-foundry", respectively.
+- Endpoint URL set to "https://.openai.azure.com/openai/v1"
+- Default Model set to the *deployment name* not the model name, as it's the name that Microsoft Foundry uses in the top-level router to forward the requests to the deployed models.
+- Context set to the maximum context length supported by the model, which is usually any of 65536, 131072, 262144, 524288, etc. but check it out first in the deployment template as it's usually mentioned in the description. But note that even though the underlying model might support a larger (or shorter) context length, the one defined in the deployment template is the correct one.
+- API Key set to the primary key displayed in Microsoft Foundry, or rather the output of `az cognitiveservices account keys list --subscription --resource-group --name -o tsv --query key1`.
+
+
+
+Finally, before using the model you can test it beforehand to make sure that everything's correctly configured, then you're all set!
+
+
From 6d75d7176aeff01819dae221686a36cc757387ee Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Thu, 13 Aug 2026 21:54:59 +0200
Subject: [PATCH 04/17] Update `_toctree.yml` and drop "Agents"
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 3 ---
docs/source/agents/introduction.mdx | 1 -
2 files changed, 4 deletions(-)
delete mode 100644 docs/source/agents/introduction.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 0792f5e..107c7cc 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -9,9 +9,6 @@
title: Deploy open-models on Microsoft Foundry
title: Get started
- sections:
- - local: agents/introduction
- title: Agents
- title: Agents
- local: harness/hermes-agent
title: Hermes Agent (Coming soon)
title: Harness
diff --git a/docs/source/agents/introduction.mdx b/docs/source/agents/introduction.mdx
deleted file mode 100644
index 57be659..0000000
--- a/docs/source/agents/introduction.mdx
+++ /dev/null
@@ -1 +0,0 @@
-# Agents
From 730bd7c97c44947c3fe7e6ad40406abe818297aa Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Sun, 16 Aug 2026 17:40:07 +0200
Subject: [PATCH 05/17] Update `harness/hermes-agent.mdx`
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/harness/hermes-agent.mdx | 50 ++++++++++++++++++++++++----
1 file changed, 43 insertions(+), 7 deletions(-)
diff --git a/docs/source/harness/hermes-agent.mdx b/docs/source/harness/hermes-agent.mdx
index e527d82..452f9f5 100644
--- a/docs/source/harness/hermes-agent.mdx
+++ b/docs/source/harness/hermes-agent.mdx
@@ -1,8 +1,10 @@
# Hermes Agent
+[Hermes Agent](https://hermes-agent.nousresearch.com/) is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.
+

-[Hermes Agent](https://hermes-agent.nousresearch.com/) is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.
+## Install
You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
@@ -16,20 +18,54 @@ Or on Windows as:
irm https://hermes-agent.nousresearch.com/install.ps1 | iex
```
+## Connect with Foundry
+
Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
-
+You need to create or add the following into your Hermes Agent configuration file at `~/.hermes/config.yaml`. More information at [Hermes Agent - Configuring Models](https://hermes-agent.nousresearch.com/docs/user-guide/configuring-models).
+
+Let's assume that you want to [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo` then the `~/.hermes/config.yaml` would look like:
+
+```yaml
+model:
+ default: qwen--qwen3-8-27b
+ provider: microsoft-foundry
+ base_url: https://huggingface-demo.openai.azure.com/openai/v1
+ key_env: HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY
+
+providers:
+ microsoft-foundry:
+ name: Microsoft Foundry
+ base_url: https://huggingface-demo.openai.azure.com/openai/v1
+ model:
+ discover_models: false
+
+ models:
+ qwen--qwen3-8-27b:
+ context_length: 262144
+ supports_vision: true
+
+agent:
+ reasoning_overrides:
+ qwen--qwen3-8-27b: medium
+```
+
+
+ As a reminder, the value for `HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY` is either obtained from [Microsoft Foundry](https://ai.azure.com) or programmatically with the `az` CLI as `az cognitiveservices account keys list --subscription --resource-group --name huggingface-demo -o tsv --query key1`.
+
Alternatively, from the desktop application you can also open the settings and click on "Providers -> Custom Endpoints" and create the endpoint with the deployed model, then set the following:
-- Name and Provider ID set to "Microsoft Foundry" and "microsoft-foundry", respectively.
-- Endpoint URL set to "https://.openai.azure.com/openai/v1"
-- Default Model set to the *deployment name* not the model name, as it's the name that Microsoft Foundry uses in the top-level router to forward the requests to the deployed models.
-- Context set to the maximum context length supported by the model, which is usually any of 65536, 131072, 262144, 524288, etc. but check it out first in the deployment template as it's usually mentioned in the description. But note that even though the underlying model might support a larger (or shorter) context length, the one defined in the deployment template is the correct one.
-- API Key set to the primary key displayed in Microsoft Foundry, or rather the output of `az cognitiveservices account keys list --subscription --resource-group --name -o tsv --query key1`.
+- **Name** and **Provider ID** set to "Microsoft Foundry" and "microsoft-foundry", respectively.
+- **Endpoint URL** set to "https://.openai.azure.com/openai/v1"
+- **Default Model** set to the *deployment name* not the model name, as it's the name that Microsoft Foundry uses in the top-level router to forward the requests to the deployed models.
+- **Context** set to the maximum context length supported by the model, which is usually any of 65536, 131072, 262144, 524288, etc. but check it out first in the deployment template as it's usually mentioned in the description. But note that even though the underlying model might support a larger (or shorter) context length, the one defined in the deployment template is the correct one.
+- **API Key** set to the primary key displayed in Microsoft Foundry, or rather the output of `az cognitiveservices account keys list --subscription --resource-group --name -o tsv --query key1`.

+## Use
+
Finally, before using the model you can test it beforehand to make sure that everything's correctly configured, then you're all set!
From 4f3e567943fb280c7b1b66e026157fec8349021e Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Sun, 16 Aug 2026 17:57:24 +0200
Subject: [PATCH 06/17] Add `large-language-models/*` and more `harness/` (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 12 +-
docs/source/harness/claude-code.mdx | 0
docs/source/harness/codex.mdx | 71 ++++++++++++
docs/source/harness/pi.mdx | 0
.../large-language-models/glm-5-2-fp8.mdx | 105 ++++++++++++++++++
.../large-language-models/introduction.mdx | 1 -
6 files changed, 187 insertions(+), 2 deletions(-)
create mode 100644 docs/source/harness/claude-code.mdx
create mode 100644 docs/source/harness/codex.mdx
create mode 100644 docs/source/harness/pi.mdx
create mode 100644 docs/source/large-language-models/glm-5-2-fp8.mdx
delete mode 100644 docs/source/large-language-models/introduction.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 107c7cc..7be3dee 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -9,8 +9,18 @@
title: Deploy open-models on Microsoft Foundry
title: Get started
- sections:
+ - local: large-language-models/glm-5-2-fp8
+ title: GLM 5.2 FP8
+ title: Large Language Models
+- sections:
+ - local: harness/claude-code
+ title: Claude Code (Coming soon)
+ - local: harness/codex
+ title: Codex
- local: harness/hermes-agent
- title: Hermes Agent (Coming soon)
+ title: Hermes Agent
+ - local: harness/pi
+ title: Pi (Coming soon)
title: Harness
- sections:
- local: large-language-models/introduction
diff --git a/docs/source/harness/claude-code.mdx b/docs/source/harness/claude-code.mdx
new file mode 100644
index 0000000..e69de29
diff --git a/docs/source/harness/codex.mdx b/docs/source/harness/codex.mdx
new file mode 100644
index 0000000..da21fc7
--- /dev/null
+++ b/docs/source/harness/codex.mdx
@@ -0,0 +1,71 @@
+# Codex
+
+[Codex]() is ...
+
+![]()
+
+## Install
+
+You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
+
+```bash
+curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
+```
+
+Or on Windows as:
+
+```bash
+irm https://hermes-agent.nousresearch.com/install.ps1 | iex
+```
+
+## Connect with Foundry
+
+Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
+
+You need to create or add the following into your Hermes Agent configuration file at `~/.hermes/config.yaml`. More information at [Hermes Agent - Configuring Models](https://hermes-agent.nousresearch.com/docs/user-guide/configuring-models).
+
+Let's assume that you want to [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo` then the `~/.hermes/config.yaml` would look like:
+
+```yaml
+model:
+ default: qwen--qwen3-8-27b
+ provider: microsoft-foundry
+ base_url: https://huggingface-demo.openai.azure.com/openai/v1
+ key_env: HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY
+
+providers:
+ microsoft-foundry:
+ name: Microsoft Foundry
+ base_url: https://huggingface-demo.openai.azure.com/openai/v1
+ model:
+ discover_models: false
+
+ models:
+ qwen--qwen3-8-27b:
+ context_length: 262144
+ supports_vision: true
+
+agent:
+ reasoning_overrides:
+ qwen--qwen3-8-27b: medium
+```
+
+
+ As a reminder, the value for `HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY` is either obtained from [Microsoft Foundry](https://ai.azure.com) or programmatically with the `az` CLI as `az cognitiveservices account keys list --subscription --resource-group --name huggingface-demo -o tsv --query key1`.
+
+
+Alternatively, from the desktop application you can also open the settings and click on "Providers -> Custom Endpoints" and create the endpoint with the deployed model, then set the following:
+
+- **Name** and **Provider ID** set to "Microsoft Foundry" and "microsoft-foundry", respectively.
+- **Endpoint URL** set to "https://.openai.azure.com/openai/v1"
+- **Default Model** set to the *deployment name* not the model name, as it's the name that Microsoft Foundry uses in the top-level router to forward the requests to the deployed models.
+- **Context** set to the maximum context length supported by the model, which is usually any of 65536, 131072, 262144, 524288, etc. but check it out first in the deployment template as it's usually mentioned in the description. But note that even though the underlying model might support a larger (or shorter) context length, the one defined in the deployment template is the correct one.
+- **API Key** set to the primary key displayed in Microsoft Foundry, or rather the output of `az cognitiveservices account keys list --subscription --resource-group --name -o tsv --query key1`.
+
+
+
+## Use
+
+Finally, before using the model you can test it beforehand to make sure that everything's correctly configured, then you're all set!
+
+
diff --git a/docs/source/harness/pi.mdx b/docs/source/harness/pi.mdx
new file mode 100644
index 0000000..e69de29
diff --git a/docs/source/large-language-models/glm-5-2-fp8.mdx b/docs/source/large-language-models/glm-5-2-fp8.mdx
new file mode 100644
index 0000000..9f14a24
--- /dev/null
+++ b/docs/source/large-language-models/glm-5-2-fp8.mdx
@@ -0,0 +1,105 @@
+# GLM 5.2 FP8
+
+[`zai-org/GLM-5.2-FP8`](https://huggingface.co/zai-org/GLM-5.2-FP8) is an open-weight reasoning model for coding, tool use, and long-running agent tasks.
+
+
+
+On Microsoft Foundry, it runs with vLLM on AMD ROCm using:
+
+- 8 x AMD Instinct MI300X 192 GB GPUs
+- A 524,288 token context window
+- Up to 32 concurrent requests per batch
+- OpenAI compatible Responses API
+
+## Pre-requisites
+
+- A Microsoft Azure subscription with access to Microsoft Foundry
+- A Microsoft Foundry project / account
+- Python 3.10 or higher
+
+Then install the following Python dependencies:
+
+```bash
+pip install azure-identity azure-ai-ml "azure-mgmt-cognitiveservices>=15.0.0b2" openai
+```
+
+And sign-in with the `az` CLI with `az login`.
+
+## Deployment
+
+Then you are all set to deploy models programmatically with the Python SDK as follows:
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "zai-org--glm-5-2-fp8"
+
+client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+deployment = client.managed_compute_deployments.begin_create_or_update(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+ resource={
+ "sku": {"name": "GlobalManagedCompute", "capacity": 1},
+ "properties": {
+ "model": "azureml://registries/azure-huggingface/models/zai-org--glm-5.2-fp8/versions/5",
+ "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/zai-org--glm-52-fp8--512k-amd-8xmi300x/labels/latest",
+ "acceleratorType": "MI300_192GB",
+ "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
+ },
+ },
+).result()
+
+print(deployment.properties.provisioning_state)
+```
+
+
+ The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
+
+
+## Inference
+
+As GLM 5.2 is a reasoning model, then using the OpenAI Responses API at `/v1/responses` is recommended.
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+from openai import OpenAI
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "zai-org--glm-5-2-fp8"
+
+az_client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+client = OpenAI(
+ base_url=f"https://{ACCOUNT_NAME}.services.ai.azure.com/openai/v1",
+ api_key=az_client.accounts.list_keys(RESOURCE_GROUP, ACCOUNT_NAME).key1,
+)
+
+response = client.responses.create(
+ model=DEPLOYMENT_NAME,
+ input="Build a small FastAPI health-check endpoint.",
+ reasoning={"effort": "high"},
+)
+
+print(response.output_text)
+```
+
+## Next steps
+
+[Connect the deployment to Codex](../harness/codex), or your favourite harness, to use your model as an agent.
+
+
diff --git a/docs/source/large-language-models/introduction.mdx b/docs/source/large-language-models/introduction.mdx
deleted file mode 100644
index 2137d53..0000000
--- a/docs/source/large-language-models/introduction.mdx
+++ /dev/null
@@ -1 +0,0 @@
-# Large Language Models
From 6a157d258d739f7d2bfbb9c8fa049a745d74e384 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Sun, 16 Aug 2026 18:08:19 +0200
Subject: [PATCH 07/17] Tentative clean-up (WIP)
Note that despite most of the files being gone, the idea is to add those
as deprecated within the repository on a later stage, but removing those
now to keep things simpler whilst rewriting the actual docs.
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
.github/workflows/doc-build.yml | 1 -
.github/workflows/doc-pr-build.yml | 1 -
Makefile | 36 +--
docs/scripts/auto-generate-examples.py | 128 --------
docs/scripts/auto-update-toctree.py | 282 ------------------
docs/source/_redirects.yml | 29 --
docs/source/_toctree.yml | 82 +----
docs/source/deprecated/faq.mdx | 11 -
docs/source/deprecated/features.mdx | 17 --
.../examples/build-agents-with-smolagents.mdx | 27 --
.../examples/deploy-large-language-models.mdx | 27 --
.../examples/deploy-nvidia-parakeet-asr.mdx | 26 --
.../foundry/examples/deploy-smollm3.mdx | 26 --
.../deploy-vision-language-models.mdx | 26 --
docs/source/deprecated/foundry/hardware.mdx | 5 -
.../deprecated/foundry/introduction.mdx | 5 -
docs/source/deprecated/foundry/models.mdx | 9 -
docs/source/deprecated/foundry/tasks.mdx | 5 -
.../deprecated/guides/access-gated-models.mdx | 13 -
.../configure-azure-ml-microsoft-foundry.mdx | 17 --
.../source/deprecated/guides/introduction.mdx | 17 --
.../guides/managed-compute-foundry.mdx | 12 -
.../guides/one-click-deployment-foundry.mdx | 17 --
.../guides/request-model-addition.mdx | 13 -
.../tool-calling-agent-fine-tuning.mdx | 22 --
docs/source/deprecated/overview.mdx | 11 -
docs/source/deprecated/resources.mdx | 14 -
docs/source/deprecated/security.mdx | 14 -
...odels-on-microsoft-foundry-with-python.mdx | 99 +++++-
...eploy-open-models-on-microsoft-foundry.mdx | 35 ++-
docs/source/harness/claude-code.mdx | 3 +
docs/source/harness/codex.mdx | 70 +----
docs/source/harness/pi.mdx | 3 +
docs/source/index.mdx | 12 +-
.../deepseek-v4-flash-0731.mdx | 130 ++++++++
35 files changed, 282 insertions(+), 963 deletions(-)
delete mode 100644 docs/scripts/auto-generate-examples.py
delete mode 100644 docs/scripts/auto-update-toctree.py
delete mode 100644 docs/source/_redirects.yml
delete mode 100644 docs/source/deprecated/faq.mdx
delete mode 100644 docs/source/deprecated/features.mdx
delete mode 100644 docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
delete mode 100644 docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
delete mode 100644 docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
delete mode 100644 docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
delete mode 100644 docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
delete mode 100644 docs/source/deprecated/foundry/hardware.mdx
delete mode 100644 docs/source/deprecated/foundry/introduction.mdx
delete mode 100644 docs/source/deprecated/foundry/models.mdx
delete mode 100644 docs/source/deprecated/foundry/tasks.mdx
delete mode 100644 docs/source/deprecated/guides/access-gated-models.mdx
delete mode 100644 docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
delete mode 100644 docs/source/deprecated/guides/introduction.mdx
delete mode 100644 docs/source/deprecated/guides/managed-compute-foundry.mdx
delete mode 100644 docs/source/deprecated/guides/one-click-deployment-foundry.mdx
delete mode 100644 docs/source/deprecated/guides/request-model-addition.mdx
delete mode 100644 docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
delete mode 100644 docs/source/deprecated/overview.mdx
delete mode 100644 docs/source/deprecated/resources.mdx
delete mode 100644 docs/source/deprecated/security.mdx
create mode 100644 docs/source/large-language-models/deepseek-v4-flash-0731.mdx
diff --git a/.github/workflows/doc-build.yml b/.github/workflows/doc-build.yml
index 938f9d1..141f5e5 100644
--- a/.github/workflows/doc-build.yml
+++ b/.github/workflows/doc-build.yml
@@ -19,7 +19,6 @@ jobs:
package: Microsoft-Azure
package_name: microsoft-azure
additional_args: --not_python_module
- pre_command: cd Microsoft-Azure && make docs
secrets:
token: ${{ secrets.HUGGINGFACE_PUSH }}
hf_token: ${{ secrets.HF_DOC_BUILD_PUSH }}
diff --git a/.github/workflows/doc-pr-build.yml b/.github/workflows/doc-pr-build.yml
index 4d7778a..7eb70cb 100644
--- a/.github/workflows/doc-pr-build.yml
+++ b/.github/workflows/doc-pr-build.yml
@@ -21,4 +21,3 @@ jobs:
package: Microsoft-Azure
package_name: microsoft-azure
additional_args: --not_python_module
- pre_command: cd Microsoft-Azure && make docs
diff --git a/Makefile b/Makefile
index 072a57d..e326e9f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,47 +1,13 @@
-.PHONY: install docs clean serve help
-
-SERVICES := foundry machine-learning
+.PHONY: install serve help
install:
@uv pip install hf-doc-builder requests watchdog
-docs: clean
- @$(foreach svc,$(SERVICES), \
- echo "Creating docs/source/deprecated/$(svc)/examples directory for examples/$(svc)..." && \
- mkdir -p docs/source/deprecated/$(svc)/examples && \
- echo "Converting Jupyter Notebooks to MDX for $(svc)..." && \
- doc-builder notebook-to-mdx examples/$(svc)/ && \
- ) true
- @echo "Auto-generating example files for documentation..."
- @python docs/scripts/auto-generate-examples.py
- @$(foreach svc,$(SERVICES), \
- echo "Cleaning up generated Markdown Notebook files for $(svc)..." && \
- find examples/$(svc)/ -name "azure-notebook.md" -type f -delete && \
- ) true
- @echo "Generating YAML tree structure and appending to _toctree.yml..."
- @python docs/scripts/auto-update-toctree.py
- @echo "YAML tree structure appended to docs/source/_toctree.yml"
- @echo "Documentation setup complete."
-
-clean:
- @echo "Cleaning up generated documentation..."
- @$(foreach svc,$(SERVICES), \
- rm -rf docs/source/deprecated/$(svc)/examples && \
- ) true
- @awk '/# GENERATED CONTENT DO NOT EDIT/,/# END OF GENERATED CONTENT/{next} {print}' docs/source/_toctree.yml | sed -e :a -e '/^\n*$$/{$$d;N;ba' -e '}' > docs/source/_toctree.yml.tmp; mv docs/source/_toctree.yml.tmp docs/source/_toctree.yml
- @echo "Cleaning up generated Markdown Notebook files (if any)..."
- @$(foreach svc,$(SERVICES), \
- find examples/$(svc) -name "azure-notebook.md" -type f -delete && \
- ) true
- @echo "Cleanup complete."
-
serve:
@echo "Serving documentation via doc-builder"
doc-builder preview microsoft-azure docs/source --not_python_module
help:
@echo "Usage:"
- @echo " make clean - Remove the auto-generated docs"
- @echo " make docs - Auto-generate the examples for the docs"
@echo " make install - Install the required Python dependencies"
@echo " make serve - Serve the docs locally at http://localhost:5173"
diff --git a/docs/scripts/auto-generate-examples.py b/docs/scripts/auto-generate-examples.py
deleted file mode 100644
index 9025ae9..0000000
--- a/docs/scripts/auto-generate-examples.py
+++ /dev/null
@@ -1,128 +0,0 @@
-import os
-import re
-import subprocess
-
-SERVICES = [
- ("Archived Microsoft Foundry", "foundry"),
- ("Archived Azure Machine Learning", "machine-learning"),
-]
-
-TARGET_ROOT = "docs/source/deprecated"
-
-
-def get_git_date(file_path: str) -> str | None:
- """Get the last commit date (YYYY-MM-DD) for a file using git."""
- if not file_path or not os.path.exists(file_path):
- return None
- try:
- date = (
- subprocess.check_output(
- ["git", "log", "-1", "--format=%ad", "--date=short", file_path],
- stderr=subprocess.STDOUT,
- )
- .decode("utf-8")
- .strip()
- )
- return date or None
- except Exception:
- return None
-
-
-def process_readme_files():
- for _, dir_name in SERVICES:
- print(f"Processing azure-notebook.md files from examples/{dir_name}...")
- os.makedirs(f"{TARGET_ROOT}/{dir_name}/examples", exist_ok=True)
-
- for root, _, files in os.walk(f"examples/{dir_name}"):
- for file in files:
- if file == "azure-notebook.md":
- process_file(root, file, dir_name)
-
-
-def process_file(root, file, dir_name):
- file_path = os.path.join(root, file)
- subdir = root.replace(f"examples/{dir_name}/", "")
- base = os.path.basename(subdir)
-
- target = f"{TARGET_ROOT}/{dir_name}/examples/{base}.mdx"
-
- print(f"Processing {file_path} to {target}")
- with open(file_path, "r") as f:
- content = f.read()
-
- # For Jupyter Notebooks, uncomment the metadata block i.e. ``
- # but keep it in the content so auto-update-toctree.py can parse it
- content = re.sub(r"", r"\1", content, flags=re.DOTALL)
-
- content = re.sub(
- r"\(\./([^/)]*\.png)\)",
- r"(https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/microsoft-azure/"
- + root.replace("examples/", "")
- + r"/\1)",
- content,
- )
- content = re.sub(
- r"\(\.\./([^)]+)\)",
- r"(https://github.com/huggingface/Microsoft-Azure/tree/main/examples/"
- + dir_name
- + r"/\1)",
- content,
- )
- content = re.sub(
- r"\(\.\/([^)]+)\)",
- r"(https://github.com/huggingface/Microsoft-Azure/tree/main/" + root + r"/\1)",
- content,
- )
-
- def replacement(match) -> str:
- block_type = match.group(1)
- content = match.group(2)
-
- # Remove '> ' from the beginning of each line
- lines = [line[2:] for line in content.split("\n") if line.strip()]
-
- # Determine the Tip type
- tip_type = " warning" if block_type == "WARNING" else ""
-
- # Construct the new block
- new_block = f"\n\n"
- new_block += "\n".join(lines)
- new_block += "\n\n\n"
-
- return new_block
-
- # Regular expression to match the specified blocks
- pattern = r"> \[!(NOTE|WARNING)\]\n((?:>.*(?:\n|$))+)"
-
- # Perform the transformation
- content = re.sub(pattern, replacement, content, flags=re.MULTILINE)
-
- # Remove any remaining '>' or '> ' at the beginning of lines
- content = re.sub(r"^>[ ]?", "", content, flags=re.MULTILINE)
-
- # Check for remaining relative paths
- if re.search(r"\(\.\./|\(\./", content):
- print("WARNING: Relative paths still exist in the processed file.")
- print(
- "The following lines contain relative paths, consider replacing those with GitHub URLs instead:"
- )
- for i, line in enumerate(content.split("\n"), 1):
- if re.search(r"\(\.\./|\(\./", line):
- print(f"{i}: {line}")
- else:
- print("No relative paths found in the processed file.")
-
- # Calculate the example URL
- example_url = f"https://github.com/huggingface/Microsoft-Azure/tree/main/{root}"
- if file.__contains__("azure-notebook"):
- example_url += "/azure-notebook.ipynb"
-
- # Add the final note
- content += f"\n\n---\n\n\n📍 Find the complete example on GitHub [here]({example_url})!\n\n"
-
- with open(target, "w") as f:
- f.write(content)
-
-
-if __name__ == "__main__":
- process_readme_files()
diff --git a/docs/scripts/auto-update-toctree.py b/docs/scripts/auto-update-toctree.py
deleted file mode 100644
index c18fa03..0000000
--- a/docs/scripts/auto-update-toctree.py
+++ /dev/null
@@ -1,282 +0,0 @@
-import glob
-import os
-import re
-import subprocess
-from datetime import datetime, timedelta
-from pathlib import Path
-
-SERVICES = [
- ("Archived Microsoft Foundry examples", "foundry"),
- ("Archived Azure Machine Learning examples", "machine-learning"),
-]
-
-
-def get_git_date(file_path: str) -> str | None:
- """Get the last commit date (YYYY-MM-DD) for a file using git."""
- if not file_path or not os.path.exists(file_path):
- return None
- try:
- date = (
- subprocess.check_output(
- ["git", "log", "-1", "--format=%ad", "--date=short", file_path],
- stderr=subprocess.STDOUT,
- )
- .decode("utf-8")
- .strip()
- )
- return date or None
- except Exception:
- return None
-
-
-def get_notebook_creation_date(base_name: str, dir_name: str) -> datetime:
- """Get the creation date of a notebook file using git."""
- notebook_pattern = f"examples/{dir_name}/*/{base_name}/azure-notebook.ipynb"
- notebook_files = glob.glob(notebook_pattern)
-
- if not notebook_files:
- notebook_pattern = f"examples/{dir_name}/*/azure-notebook.ipynb"
- all_notebooks = glob.glob(notebook_pattern)
-
- for notebook in all_notebooks:
- if base_name in notebook:
- notebook_files = [notebook]
- break
-
- if not notebook_files:
- return datetime.min
-
- notebook_file = notebook_files[0]
-
- try:
- result = subprocess.run(
- ["git", "log", "--format=%ct", "--diff-filter=A", "--", notebook_file],
- capture_output=True,
- text=True,
- check=True,
- )
-
- if result.stdout.strip():
- creation_timestamp = int(result.stdout.strip().split("\n")[-1])
- return datetime.fromtimestamp(creation_timestamp)
- else:
- stat_info = os.stat(notebook_file)
- creation_time = getattr(stat_info, "st_birthtime", stat_info.st_mtime)
- return datetime.fromtimestamp(creation_time)
- except (subprocess.CalledProcessError, OSError, ValueError):
- return datetime.min
-
-
-def is_notebook_new(creation_date: datetime) -> bool:
- """Check if a notebook is considered new (created in last 7 days)."""
- days_ago = datetime.now() - timedelta(days=7)
- return creation_date > days_ago
-
-
-def get_original_notebook_path(mdx_file: str, dir_name: str) -> str | None:
- """Map an MDX file back to the original notebook for git date lookups."""
- base = Path(mdx_file).stem
- nb_path = f"examples/{dir_name}/{base}/azure-notebook.ipynb"
- if os.path.exists(nb_path):
- return nb_path
- return None
-
-
-def parse_metadata(content: str) -> dict:
- """Parse YAML-like metadata from --- ... --- block at the top of content."""
- metadata_match = re.search(
- r"^\s*(?:)?",
- content,
- re.DOTALL | re.MULTILINE,
- )
- if not metadata_match:
- return {}
- metadata_str = metadata_match.group(1)
- return {k.strip(): v.strip() for k, v in re.findall(r"(\w+):\s*(.+)", metadata_str)}
-
-
-def strip_metadata_block(content: str) -> str:
- """Remove the --- ... --- metadata block from content."""
- content = re.sub(
- r"^\s*(?:)?\s*\n",
- "",
- content,
- count=1,
- flags=re.DOTALL | re.MULTILINE,
- )
- return content.strip()
-
-
-def inject_author_date(content: str, author: str | None, date: str | None) -> str:
- extra_parts = []
- if author:
- extra_parts.append(f"Written by {author}")
- if date:
- extra_parts.append(f"Last updated {date}")
-
- if not extra_parts:
- return content
-
- extra_info = "
" + " ".join(extra_parts) + "
"
-
- match = re.search(r"^(# .+)$", content, re.MULTILINE)
- if match:
- title_line = match.group(1)
- content = content.replace(title_line, f"{title_line}\n\n{extra_info}\n", 1)
-
- return content
-
-
-def get_example_entries(dir_name: str) -> list:
- """Find, process, and sort example files for a given service directory."""
- example_files = sorted(glob.glob(f"docs/source/deprecated/{dir_name}/examples/*.mdx"))
- if not example_files:
- return []
-
- entries = []
- for file in example_files:
- with open(file, "r+") as mdx_file:
- content = mdx_file.read()
-
- # Parse and remove metadata block
- metadata = parse_metadata(content)
- content = strip_metadata_block(content)
-
- # Get author from metadata and last-updated date from git
- author = metadata.get("author")
- original_file = get_original_notebook_path(file, dir_name)
- date = get_git_date(original_file) # type: ignore
-
- # Inject author/date info into the content
- content = inject_author_date(content, author, date)
-
- # Write back the processed content (metadata stripped, author/date injected)
- mdx_file.seek(0)
- mdx_file.write(content)
- mdx_file.truncate()
-
- # Extract title from first # heading
- title = metadata.get("title")
- if not title:
- title_match = re.search(r"^# (.+)", content, re.MULTILINE)
- if title_match:
- title = title_match.group(1).strip()
-
- if not title:
- print(f"WARNING: No title found in {file}")
- continue
-
- base = Path(file).stem
-
- # Get creation date for sorting
- creation_date = get_notebook_creation_date(base, dir_name)
- is_new = is_notebook_new(creation_date)
-
- entries.append((base, title, is_new, creation_date))
-
- # Sort by creation date (newest first)
- entries.sort(key=lambda x: x[3], reverse=True)
- return entries
-
-
-def build_examples_section(dir_name: str, entries: list, indent: str) -> list:
- """Build the YAML lines for an Examples sub-section."""
- lines = []
- lines.append(f"{indent}# GENERATED CONTENT DO NOT EDIT")
- lines.append(f"{indent}- sections:")
- for base, title, is_new, creation_date in entries:
- lines.append(f"{indent} - local: deprecated/{dir_name}/examples/{base}")
- lines.append(f'{indent} title: "{title}"')
- # if is_new:
- # lines.append(" new: true")
- lines.append(f"{indent} title: Examples")
- lines.append(f"{indent} isExpanded: false")
- lines.append(f"{indent}# END OF GENERATED CONTENT")
- return lines
-
-
-def is_service_title_line(line: str, display_name: str) -> bool:
- """Return True when a YAML line defines the requested title.
-
- Supports both quoted and unquoted forms:
- `title: Microsoft Foundry` and `title: "Microsoft Foundry"`.
- """
- match = re.match(r'^\s*title:\s*"?(.+?)"?\s*$', line)
- return bool(match and match.group(1) == display_name)
-
-
-def inject_examples_for_service(
- lines: list, display_name: str, dir_name: str, entries: list
-) -> list:
- """Inject generated example entries into an existing service section.
-
- If the toctree already has a section with `title: `, the
- examples block is inserted right before that title line (so it becomes a
- nested sub-section). If no such section exists, a brand-new top-level
- section is appended at the end of the file.
- """
- # Check whether the section already exists
- has_section = any(is_service_title_line(line, display_name) for line in lines)
-
- if has_section:
- result_lines = []
- for line in lines:
- if is_service_title_line(line, display_name):
- indent_match = re.match(r"^(\s*)title:", line)
- indent = indent_match.group(1) if indent_match else " "
- result_lines.extend(build_examples_section(dir_name, entries, indent))
- result_lines.append(line)
- return result_lines
-
- # Section does not exist yet — create a whole new top-level entry.
- # The entire block is wrapped inside the generated-content markers so
- # that `make clean` can remove it completely (including the outer
- # `- sections:` and `title:` lines).
- new_section = ["# GENERATED CONTENT DO NOT EDIT"]
- new_section.append("- sections:")
- new_section.append(" - sections:")
- for base, title, is_new, creation_date in entries:
- new_section.append(f" - local: deprecated/{dir_name}/examples/{base}")
- new_section.append(f' title: "{title}"')
- new_section.append(" title: Examples")
- new_section.append(" isExpanded: true")
- new_section.append(f" title: {display_name}")
- new_section.append(" new: true")
- new_section.append("# END OF GENERATED CONTENT")
- return lines + new_section
-
-
-def update_toctree_yaml():
- toctree_file = "docs/source/_toctree.yml"
-
- with open(toctree_file, "r") as f:
- content = f.read()
-
- # Remove any existing generated content between markers
- content = re.sub(
- r"^\s*# GENERATED CONTENT DO NOT EDIT.*?^\s*# END OF GENERATED CONTENT\n?",
- "",
- content,
- flags=re.MULTILINE | re.DOTALL,
- )
-
- # Clean up any extra newlines that might be left
- content = content.strip() + "\n"
-
- lines = content.split("\n")
-
- for display_name, dir_name in SERVICES:
- entries = get_example_entries(dir_name)
- if not entries:
- print(f"No example files found for {display_name}")
- continue
- lines = inject_examples_for_service(lines, display_name, dir_name, entries)
-
- # Ensure the file ends with exactly one newline (POSIX compliant)
- output = "\n".join(lines).rstrip("\n") + "\n"
- with open(toctree_file, "w") as f:
- f.write(output)
-
-
-if __name__ == "__main__":
- update_toctree_yaml()
diff --git a/docs/source/_redirects.yml b/docs/source/_redirects.yml
deleted file mode 100644
index 6bbd906..0000000
--- a/docs/source/_redirects.yml
+++ /dev/null
@@ -1,29 +0,0 @@
-guides/one-click-deployment-azure-ml: deprecated/guides/one-click-deployment-foundry
-guides/one-click-deployment-azure-ai: deprecated/guides/one-click-deployment-foundry
-azure-ai/configure: deprecated/guides/configure-azure-ml-microsoft-foundry
-azure-ai/set-up: deprecated/guides/configure-azure-ml-microsoft-foundry
-
-# NOTE: The redirects below are required only for the entries and examples
-# published before the rename from Azure AI Foundry to Microsoft Foundry
-azure-ai/hardware: deprecated/foundry/hardware
-azure-ai/introduction: deprecated/foundry/introduction
-azure-ai/models: deprecated/foundry/models
-azure-ai/tasks: deprecated/foundry/tasks
-azure-ai/examples/build-agents-with-smolagents: deprecated/foundry/examples/build-agents-with-smolagents
-azure-ai/examples/deploy-large-language-models: deprecated/foundry/examples/deploy-large-language-models
-azure-ai/examples/deploy-nvidia-parakeet-asr: deprecated/foundry/examples/deploy-nvidia-parakeet-asr
-azure-ai/examples/deploy-smollm3: deprecated/foundry/examples/deploy-smollm3
-azure-ai/examples/deploy-vision-language-models: deprecated/foundry/examples/deploy-vision-language-models
-
-features: deprecated/features
-security: deprecated/security
-faq: deprecated/faq
-guides/introduction: deprecated/guides/introduction
-guides/managed-compute-foundry: deprecated/guides/managed-compute-foundry
-guides/access-gated-models: deprecated/guides/access-gated-models
-guides/configure-azure-ml-microsoft-foundry: deprecated/guides/configure-azure-ml-microsoft-foundry
-guides/one-click-deployment-foundry: deprecated/guides/one-click-deployment-foundry
-foundry/introduction: deprecated/foundry/introduction
-foundry/models: deprecated/foundry/models
-foundry/tasks: deprecated/foundry/tasks
-foundry/hardware: deprecated/foundry/hardware
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 7be3dee..7537cef 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -3,14 +3,18 @@
title: Overview
title: Overview
- sections:
- - local: get-started/deploy-open-models-on-microsoft-foundry-with-python
- title: Deploy open-models on Microsoft Foundry with Python
- local: get-started/deploy-open-models-on-microsoft-foundry
title: Deploy open-models on Microsoft Foundry
+ - local: get-started/deploy-open-models-on-microsoft-foundry-with-python
+ title: Deploy open-models on Microsoft Foundry with Python
title: Get started
- sections:
- local: large-language-models/glm-5-2-fp8
title: GLM 5.2 FP8
+ - local: large-language-models/deepseek-v4-flash-0731
+ title: DeepSeek V4 Flash 0731
+ - local: large-language-models/qwen3-8-27b
+ title: Qwen3.8 27B
title: Large Language Models
- sections:
- local: harness/claude-code
@@ -22,77 +26,3 @@
- local: harness/pi
title: Pi (Coming soon)
title: Harness
-- sections:
- - local: large-language-models/introduction
- title: Large Language Models
- title: Large Language Models
-- sections:
- - local: deprecated/overview
- title: Overview
- - sections:
- - local: deprecated/features
- title: Features & Benefits
- - local: deprecated/security
- title: Security & Compliance
- - local: deprecated/resources
- title: Other Resources
- - local: deprecated/faq
- title: FAQ
- title: Legacy top-level pages
- isExpanded: false
- - sections:
- - local: deprecated/guides/introduction
- title: Guides index
- - local: deprecated/guides/configure-azure-ml-microsoft-foundry
- title: Configure Azure Machine Learning and Microsoft Foundry
- - local: deprecated/guides/managed-compute-foundry
- title: Deploy Hugging Face Models in Foundry with Managed Compute
- - local: deprecated/guides/one-click-deployment-foundry
- title: One-click deployments from the Hugging Face Hub on Microsoft Foundry
- - local: deprecated/guides/access-gated-models
- title: Deploy Hugging Face gated models on Microsoft Foundry
- - local: deprecated/guides/request-model-addition
- title: Request a model addition in the Hugging Face collection on Microsoft Foundry
- title: Legacy guides
- isExpanded: false
- - sections:
- - local: deprecated/foundry/introduction
- title: Introduction
- - local: deprecated/foundry/tasks
- title: Supported tasks
- - local: deprecated/foundry/hardware
- title: Supported hardware
- - local: deprecated/foundry/models
- title: Supported models
- title: Legacy Foundry reference
- isExpanded: false
- - sections:
- # GENERATED CONTENT DO NOT EDIT
- - sections:
- - local: deprecated/foundry/examples/build-agents-with-smolagents
- title: "Archived Example: Build Agents with smolagents on Microsoft Foundry"
- - local: deprecated/foundry/examples/deploy-large-language-models
- title: "Archived Example: Deploy Large Language Models on Microsoft Foundry"
- - local: deprecated/foundry/examples/deploy-nvidia-parakeet-asr
- title: "Archived Example: Deploy NVIDIA Parakeet for ASR on Microsoft Foundry"
- - local: deprecated/foundry/examples/deploy-smollm3
- title: "Archived Example: Deploy SmolLM3 on Microsoft Foundry"
- - local: deprecated/foundry/examples/deploy-vision-language-models
- title: "Archived Example: Deploy Vision Language Models on Microsoft Foundry"
- title: Examples
- isExpanded: false
- # END OF GENERATED CONTENT
- title: Archived Microsoft Foundry examples
- isExpanded: false
- - sections:
- # GENERATED CONTENT DO NOT EDIT
- - sections:
- - local: deprecated/machine-learning/examples/tool-calling-agent-fine-tuning
- title: "Archived Example: Tool-calling Agent Fine-tuning on Azure Machine Learning"
- title: Examples
- isExpanded: false
- # END OF GENERATED CONTENT
- title: Archived Azure Machine Learning examples
- isExpanded: false
- title: Deprecated / Archived
- isExpanded: false
diff --git a/docs/source/deprecated/faq.mdx b/docs/source/deprecated/faq.mdx
deleted file mode 100644
index c4cff70..0000000
--- a/docs/source/deprecated/faq.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-# Archived: FAQ
-
-This page preserves the older FAQ topics from the previous docs structure.
-
-## What did the old FAQ focus on?
-
-- The distinction between Azure Machine Learning and Microsoft Foundry
-- Why hub-based projects mattered for open-model deployments
-- What capabilities were limited in standalone Foundry projects
-
-That content has been simplified in the current [FAQ](../reference/faq), but the old framing is still useful when reading older screenshots, tutorials, or issue threads that refer to Azure AI Foundry hubs and projects.
diff --git a/docs/source/deprecated/features.mdx b/docs/source/deprecated/features.mdx
deleted file mode 100644
index 0ead4dc..0000000
--- a/docs/source/deprecated/features.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-# Archived: Features & Benefits
-
-This page preserves the former high-level features summary from the previous documentation structure.
-
-The legacy framing emphasized:
-
-- A large Hugging Face catalog available through Microsoft Foundry and Azure Machine Learning
-- Managed deployment paths with Azure-hosted security, scaling, and monitoring
-- Coverage across text, multimodal, audio, vision, and embeddings workloads
-- Open-source runtimes such as TGI, vLLM, SGLang, and TEI
-- Enterprise controls around compliance, isolation, and governance
-
-For the current task-oriented docs, use:
-
-- [Overview](../index)
-- [Supported models](../reference/supported-models)
-- [Security and model eligibility](../reference/security-and-eligibility)
diff --git a/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx b/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
deleted file mode 100644
index c8ff608..0000000
--- a/docs/source/deprecated/foundry/examples/build-agents-with-smolagents.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
-# Archived Example: Build Agents with smolagents on Microsoft Foundry
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example focused on building an agent with `smolagents` on top of a Hugging Face deployment in Microsoft Foundry.
-
-## What it covered
-
-- Deploying a coding-oriented LLM from the Hugging Face collection
-- Invoking the model from Python
-- Wiring the deployment into a `smolagents` workflow
-- Comparing Hub, Azure ML, and Foundry views of the same model
-
-## Original assets
-
-- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/build-agents-with-smolagents/azure-notebook.ipynb)
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/build-agents-with-smolagents)
-
-## Current docs to read instead
-
-- [Build agents with Foundry deployments](../../../agents/introduction)
-- [Define custom tools](../../../agents/define-custom-tools)
-- [Connect MCP servers](../../../agents/connect-mcp)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx b/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
deleted file mode 100644
index 9e8b004..0000000
--- a/docs/source/deprecated/foundry/examples/deploy-large-language-models.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
-# Archived Example: Deploy Large Language Models on Microsoft Foundry
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example showed a more notebook-heavy path for deploying a text-generation model and then calling it from several clients.
-
-## What it covered
-
-- Programmatic deployment with the Azure ML SDK
-- OpenAI-compatible inference calls
-- A local Gradio chat client
-- The relationship between the Hugging Face model ID and the Azure model URI
-
-## Original assets
-
-- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-large-language-models/azure-notebook.ipynb)
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-large-language-models)
-
-## Current docs to read instead
-
-- [Deploy your first model](../../../get-started/deploy-first-model)
-- [Call your deployment](../../../get-started/call-your-deployment)
-- [Third-party integrations](../../../guides/third-party-integrations)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx b/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
deleted file mode 100644
index 6ead456..0000000
--- a/docs/source/deprecated/foundry/examples/deploy-nvidia-parakeet-asr.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
-# Archived Example: Deploy NVIDIA Parakeet for ASR on Microsoft Foundry
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example focused on automatic speech recognition using NVIDIA Parakeet.
-
-## What it covered
-
-- Deploying an ASR model from the Hugging Face collection
-- Sending audio transcription requests
-- Comparing different client approaches, including cURL and Python
-- Working with a speech-focused deployment instead of a text chat model
-
-## Original assets
-
-- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-nvidia-parakeet-asr/azure-notebook.ipynb)
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-nvidia-parakeet-asr)
-
-## Current docs to read instead
-
-- [Deploy your first model](../../../get-started/deploy-first-model)
-- [Supported tasks](../../../reference/supported-tasks)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx b/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
deleted file mode 100644
index de6ce17..0000000
--- a/docs/source/deprecated/foundry/examples/deploy-smollm3.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
-# Archived Example: Deploy SmolLM3 on Microsoft Foundry
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example focused on deploying `HuggingFaceTB/SmolLM3-3B` and calling it through the OpenAI-compatible route.
-
-## What it covered
-
-- Building the Azure model URI from the Hugging Face model ID
-- Creating a managed endpoint and deployment
-- Running text-generation requests
-- Reasoning-oriented and long-context positioning for a small model
-
-## Original assets
-
-- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-smollm3/azure-notebook.ipynb)
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-smollm3)
-
-## Current docs to read instead
-
-- [Deploy your first model](../../../get-started/deploy-first-model)
-- [Thinking levels](../../../guides/thinking-levels)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx b/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
deleted file mode 100644
index 053525d..0000000
--- a/docs/source/deprecated/foundry/examples/deploy-vision-language-models.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
-# Archived Example: Deploy Vision Language Models on Microsoft Foundry
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example focused on multimodal deployments, using a vision-language model that accepts both images and text.
-
-## What it covered
-
-- Deploying a VLM from the Hugging Face collection
-- Sending multimodal requests
-- Using the deployment through both SDK and notebook flows
-- Handling image-aware prompts in a Foundry deployment
-
-## Original assets
-
-- [Notebook source](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-vision-language-models/azure-notebook.ipynb)
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/foundry/deploy-vision-language-models)
-
-## Current docs to read instead
-
-- [Deploy your first model](../../../get-started/deploy-first-model)
-- [Supported tasks](../../../reference/supported-tasks)
\ No newline at end of file
diff --git a/docs/source/deprecated/foundry/hardware.mdx b/docs/source/deprecated/foundry/hardware.mdx
deleted file mode 100644
index 0d18581..0000000
--- a/docs/source/deprecated/foundry/hardware.mdx
+++ /dev/null
@@ -1,5 +0,0 @@
-# Archived: Supported Hardware
-
-This page preserves the older hardware table references for GPU and CPU instance families used in Foundry-related deployment flows.
-
-The maintained version is [Supported hardware](../../reference/supported-hardware).
diff --git a/docs/source/deprecated/foundry/introduction.mdx b/docs/source/deprecated/foundry/introduction.mdx
deleted file mode 100644
index 4048557..0000000
--- a/docs/source/deprecated/foundry/introduction.mdx
+++ /dev/null
@@ -1,5 +0,0 @@
-# Archived: Hugging Face on Microsoft Foundry
-
-This page preserves the former service-introduction page that described the broader Hugging Face and Microsoft collaboration, the expansion through Build and Ignite announcements, and the catalog-scale messaging used in the earlier docs.
-
-That material has been replaced in the main docs by a shorter, task-oriented [Overview](../../index).
diff --git a/docs/source/deprecated/foundry/models.mdx b/docs/source/deprecated/foundry/models.mdx
deleted file mode 100644
index 6e3721e..0000000
--- a/docs/source/deprecated/foundry/models.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
-# Archived: Supported Models
-
-This page preserves the earlier explanation of how to check whether a Hugging Face model is available in the Foundry catalog, including:
-
-- Checking the **Deploy on Microsoft Foundry** action on the Hub
-- Searching the Hugging Face collection in Foundry
-- Using the old Azure lookup endpoint mentioned in the earlier docs
-
-The maintained version is [Supported models](../../reference/supported-models).
diff --git a/docs/source/deprecated/foundry/tasks.mdx b/docs/source/deprecated/foundry/tasks.mdx
deleted file mode 100644
index 2ac9d59..0000000
--- a/docs/source/deprecated/foundry/tasks.mdx
+++ /dev/null
@@ -1,5 +0,0 @@
-# Archived: Supported Tasks
-
-This page preserves the older task list wording that grouped supported workloads across text, multimodal, audio, and vision.
-
-The maintained version is [Supported tasks](../../reference/supported-tasks).
diff --git a/docs/source/deprecated/guides/access-gated-models.mdx b/docs/source/deprecated/guides/access-gated-models.mdx
deleted file mode 100644
index a964851..0000000
--- a/docs/source/deprecated/guides/access-gated-models.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
-# Archived: Deploy Hugging Face gated models on Microsoft Foundry
-
-This page preserves the former gated-model deployment flow.
-
-## Legacy flow summary
-
-1. Request access to the gated repository on the Hugging Face Hub
-2. Create a Hugging Face token with gated-repository read permissions
-3. Store that token in an Azure Machine Learning connection
-4. Ensure the endpoint can access the secret store
-5. Deploy the model using the Azure ML SDK
-
-The maintained version of this guidance is [Gated models](../../guides/gated-models).
diff --git a/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx b/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
deleted file mode 100644
index e91c641..0000000
--- a/docs/source/deprecated/guides/configure-azure-ml-microsoft-foundry.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-# Archived: Configure Azure Machine Learning and Microsoft Foundry
-
-This page preserves the former setup flow that walked through:
-
-1. Installing and authenticating the Azure CLI
-2. Installing the `az ml` extension
-3. Creating a resource group
-4. Creating an Azure AI Foundry hub
-5. Creating a project attached to that hub
-
-That flow assumed the older Azure AI Foundry naming and hub/project model. The maintained version is [Configure Microsoft Foundry](../../get-started/configure-foundry).
-
-## Legacy notes
-
-- Older guides and notebooks may refer to Azure AI Foundry instead of Microsoft Foundry
-- Older commands may reference hub-based projects explicitly
-- Some screenshots and resource names in notebooks still follow that older wording
diff --git a/docs/source/deprecated/guides/introduction.mdx b/docs/source/deprecated/guides/introduction.mdx
deleted file mode 100644
index fbd7cb1..0000000
--- a/docs/source/deprecated/guides/introduction.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-# Archived: Guides
-
-This page used to act as the guides index in the former documentation structure.
-
-The old guide set centered on:
-
-- One-click deployments from the Hugging Face Hub
-- Deploying gated models
-- Requesting model additions
-- Configuring Azure Machine Learning and Microsoft Foundry
-- Managed compute
-
-The maintained equivalents now live under:
-
-- [Get started](../../get-started/introduction)
-- [Guides](../../guides/managed-compute)
-- [Agents](../../agents/introduction)
diff --git a/docs/source/deprecated/guides/managed-compute-foundry.mdx b/docs/source/deprecated/guides/managed-compute-foundry.mdx
deleted file mode 100644
index da79f67..0000000
--- a/docs/source/deprecated/guides/managed-compute-foundry.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Archived: Deploy Hugging Face Models in Foundry with Managed Compute
-
-This archived page keeps the older, more detailed managed-compute framing that predated the simplified guide set.
-
-The former guide emphasized:
-
-- Managed compute as a dedicated-capacity deployment option
-- Accelerator-family-specific quota requirements
-- Template-driven deployment choices
-- Validation through the Foundry playground before moving to code
-
-For the current streamlined version, see [Managed compute](../../guides/managed-compute).
diff --git a/docs/source/deprecated/guides/one-click-deployment-foundry.mdx b/docs/source/deprecated/guides/one-click-deployment-foundry.mdx
deleted file mode 100644
index 7f79db7..0000000
--- a/docs/source/deprecated/guides/one-click-deployment-foundry.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-# Archived: One-click deployments from the Hugging Face Hub on Microsoft Foundry
-
-This page preserves the former one-click deployment entry point.
-
-## Legacy flow
-
-1. Browse models on the Hugging Face Hub
-2. Use the **Deploy** button on a supported model card
-3. Choose **Deploy on Microsoft Foundry**
-4. Review the model card in Foundry
-5. Create the deployment and test the endpoint
-
-The current maintained equivalent is [Deploy your first model](../../get-started/deploy-first-model).
-
-## Why keep this archived page?
-
-Older tutorials, screenshots, and issues often refer to the Hub-first flow rather than the current docs navigation.
diff --git a/docs/source/deprecated/guides/request-model-addition.mdx b/docs/source/deprecated/guides/request-model-addition.mdx
deleted file mode 100644
index cbf61ee..0000000
--- a/docs/source/deprecated/guides/request-model-addition.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
-# Archived: Request a model addition in the Hugging Face collection on Microsoft Foundry
-
-This page preserves the earlier model-addition guidance from the old docs structure.
-
-The previous checklist focused on:
-
-- `Transformers`, `Diffusers`, or `Sentence-Transformers` compatibility
-- A supported task taxonomy
-- Runtime alignment for TGI, vLLM, SGLang, or TEI when relevant
-- Public visibility on the Hub
-- Secure artifact formats and security scanning
-
-The maintained version is [Request model addition](../../guides/request-model-addition).
diff --git a/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx b/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
deleted file mode 100644
index b74f669..0000000
--- a/docs/source/deprecated/machine-learning/examples/tool-calling-agent-fine-tuning.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
-# Archived Example: Tool-calling Agent Fine-tuning on Azure Machine Learning
-
-
Last updated 2026-03-02
-
-
-
Last updated 2026-03-02
-
-
-This archived example comes from the earlier Azure Machine Learning example set rather than the current Foundry-first docs path.
-
-## What it covered
-
-- Fine-tuning an agent-oriented model
-- Preparing training data for tool-calling behavior
-- Running an Azure Machine Learning job
-- Inspecting experiment and log outputs
-
-## Original assets
-
-- [Example directory](https://github.com/huggingface/Microsoft-Azure/tree/main/examples/machine-learning/tool-calling-agent-fine-tuning)
-
-This material remains archived because the active docs are now centered on Foundry deployment and integration workflows instead of Azure ML training examples.
\ No newline at end of file
diff --git a/docs/source/deprecated/overview.mdx b/docs/source/deprecated/overview.mdx
deleted file mode 100644
index a266581..0000000
--- a/docs/source/deprecated/overview.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-# Deprecated / Archived
-
-This section preserves the former documentation layout and legacy examples that existed before the docs were reorganized around the simpler Foundry-focused structure.
-
-Use this section when you need to:
-
-- Follow an old link that no longer belongs in the main learning path
-- Recover older wording, screenshots, or step-by-step examples
-- Compare the previous docs organization with the current one
-
-The archived pages are kept for continuity, not as the recommended entry point for new users. For the current docs, start from the main [Overview](../index).
diff --git a/docs/source/deprecated/resources.mdx b/docs/source/deprecated/resources.mdx
deleted file mode 100644
index 6dcf149..0000000
--- a/docs/source/deprecated/resources.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Archived: Other Resources
-
-This page keeps the older external-reading collection that used to live near the top of the docs.
-
-## Legacy links
-
-- [Hugging Face on Azure](https://azure.microsoft.com/en-us/solutions/hugging-face-on-azure)
-- [Microsoft and Hugging Face expand collaboration](https://huggingface.co/blog/azure-ai-foundry)
-- [Microsoft and Hugging Face expand collaboration to accelerate Open-Source AI Innovation on Azure AI Foundry](https://devblogs.microsoft.com/foundry/microsoft-and-hugging-face-expand-partnership-to-accelerate-open-source-ai-innovation-on-azure-ai-foundry/)
-- [From cloud to developers: Hugging Face and Microsoft deepen collaboration](https://huggingface.co/blog/microsoft-collaboration)
-- [Microsoft and Hugging Face deepen generative AI partnership](https://techcommunity.microsoft.com/blog/aiplatformblog/microsoft-and-hugging-face-deepen-generative-ai-partnership/4144565)
-- [Hugging Face collaborates with Microsoft to launch Hugging Face Model Catalog on Azure](https://huggingface.co/blog/hugging-face-endpoints-on-azure)
-
-For the maintained external-links page, see [Resources](../resources).
diff --git a/docs/source/deprecated/security.mdx b/docs/source/deprecated/security.mdx
deleted file mode 100644
index 4d552b4..0000000
--- a/docs/source/deprecated/security.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Archived: Security & Compliance
-
-This page preserves the earlier security-focused explanation from the old docs layout.
-
-The legacy guidance highlighted the following model eligibility requirements:
-
-- Public availability on the Hugging Face Hub, including gated public repositories
-- Safe weight formats such as `safetensors`
-- No unreviewed `trust_remote_code` or unsupported custom execution code
-- Security scanning on Hub artifacts before catalog inclusion
-
-It also stressed that enterprise controls such as private networking, auditability, and access control still depend on the surrounding Microsoft Foundry and Azure environment.
-
-For the maintained version of this material, see [Security and model eligibility](../reference/security-and-eligibility).
diff --git a/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
index 2d6f9c8..1fecd9d 100644
--- a/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
+++ b/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
@@ -1 +1,98 @@
-# Deploy open-models from Microsoft Foundry with Python
+# Deploy open-models on Microsoft Foundry with Python
+
+Deploy open models on dedicated hardware with Microsoft Foundry Managed Compute. This example deploys [`zai-org/GLM-5.2-FP8`](https://huggingface.co/zai-org/GLM-5.2-FP8) on 8 AMD Instinct MI300X GPUs.
+
+## Prerequisites
+
+- An Azure subscription with Managed Compute preview access
+- A Microsoft Foundry account
+- `Cognitive Services Contributor` access to the account
+- Managed Compute quota for MI300X
+- Python 3.10 or later and the Azure CLI
+
+Sign in and install the dependencies:
+
+```bash
+az login
+uv pip install azure-identity "azure-mgmt-cognitiveservices>=15.0.0b2" openai
+```
+
+## Deploy the model
+
+Replace the placeholders, then run:
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "zai-org--glm-5-2-fp8"
+
+client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+deployment = client.managed_compute_deployments.begin_create_or_update(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+ resource={
+ "sku": {"name": "GlobalManagedCompute", "capacity": 1},
+ "properties": {
+ "model": "azureml://registries/azure-huggingface/models/zai-org--glm-5.2-fp8/versions/5",
+ "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/zai-org--glm-52-fp8--512k-amd-8xmi300x/labels/latest",
+ "acceleratorType": "MI300_192GB",
+ "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
+ },
+ },
+).result()
+
+print(deployment.properties.provisioning_state)
+```
+
+Provisioning is blocking and usually takes 15–20 minutes. The deployment is ready when its state is `Succeeded`.
+
+The model and deployment template IDs are model-specific. Copy them from the deployment wizard when deploying a different model.
+
+## Send a request
+
+```python
+from openai import OpenAI
+
+api_key = client.accounts.list_keys(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+).key1
+
+inference = OpenAI(
+ base_url=f"https://{ACCOUNT_NAME}.services.ai.azure.com/openai/v1",
+ api_key=api_key,
+)
+
+response = inference.responses.create(
+ model=DEPLOYMENT_NAME,
+ input="How does Hugging Face make money?",
+ reasoning={"effort": "none"},
+)
+
+print(response.output_text)
+```
+
+Use the deployment name in `model`, not the Foundry model name or Hugging Face model ID.
+
+## Delete the deployment
+
+Delete unused deployments to stop billing:
+
+```python
+client.managed_compute_deployments.begin_delete(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+).result()
+```
+
+For more context, see the [original GLM 5.2 walkthrough](https://alvarobartt.com/goal-glm-5.2-on-foundry) and the [Managed Compute documentation](https://learn.microsoft.com/azure/foundry/how-to/deploy-models-managed).
diff --git a/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
index e379b3e..abd5dfb 100644
--- a/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
+++ b/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
@@ -1 +1,34 @@
-# Deploy open-models from Microsoft Foundry
+# Deploy open-models on Microsoft Foundry
+
+Use Managed Compute to deploy open models on dedicated hardware without managing the serving stack.
+
+## Prerequisites
+
+- An Azure subscription and Microsoft Foundry account
+- Permission to create deployments
+- Managed Compute quota for the required accelerator
+
+## Find a model
+
+1. Open [Microsoft Foundry](https://ai.azure.com).
+2. Go to **Discover → Models**.
+3. Filter **Collection** by **Hugging Face**.
+4. Select a model and choose **Deploy**.
+
+## Deploy
+
+1. Enter a deployment name.
+2. Keep **Global Managed Compute** as the deployment type.
+3. Choose a compatible deployment template and accelerator.
+4. Start with one model instance.
+5. Acknowledge the cost and select **Deploy**.
+
+Provisioning usually takes 10–20 minutes. Wait for the deployment state to become `Succeeded`.
+
+## Test and monitor
+
+Open the deployment's **Playground** tab to send a request. Use **Monitor** to inspect request count, latency, token usage, and errors.
+
+The deployment name is the value applications pass in the API's `model` field.
+
+Delete unused deployments to release their accelerators and stop billing. For programmatic deployment, see [Deploy open-models on Microsoft Foundry with Python](./deploy-open-models-on-microsoft-foundry-with-python).
diff --git a/docs/source/harness/claude-code.mdx b/docs/source/harness/claude-code.mdx
index e69de29..248e267 100644
--- a/docs/source/harness/claude-code.mdx
+++ b/docs/source/harness/claude-code.mdx
@@ -0,0 +1,3 @@
+# Claude Code
+
+Coming soon!
diff --git a/docs/source/harness/codex.mdx b/docs/source/harness/codex.mdx
index da21fc7..92ec3ac 100644
--- a/docs/source/harness/codex.mdx
+++ b/docs/source/harness/codex.mdx
@@ -1,71 +1,3 @@
# Codex
-[Codex]() is ...
-
-![]()
-
-## Install
-
-You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
-
-```bash
-curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
-```
-
-Or on Windows as:
-
-```bash
-irm https://hermes-agent.nousresearch.com/install.ps1 | iex
-```
-
-## Connect with Foundry
-
-Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
-
-You need to create or add the following into your Hermes Agent configuration file at `~/.hermes/config.yaml`. More information at [Hermes Agent - Configuring Models](https://hermes-agent.nousresearch.com/docs/user-guide/configuring-models).
-
-Let's assume that you want to [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo` then the `~/.hermes/config.yaml` would look like:
-
-```yaml
-model:
- default: qwen--qwen3-8-27b
- provider: microsoft-foundry
- base_url: https://huggingface-demo.openai.azure.com/openai/v1
- key_env: HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY
-
-providers:
- microsoft-foundry:
- name: Microsoft Foundry
- base_url: https://huggingface-demo.openai.azure.com/openai/v1
- model:
- discover_models: false
-
- models:
- qwen--qwen3-8-27b:
- context_length: 262144
- supports_vision: true
-
-agent:
- reasoning_overrides:
- qwen--qwen3-8-27b: medium
-```
-
-
- As a reminder, the value for `HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY` is either obtained from [Microsoft Foundry](https://ai.azure.com) or programmatically with the `az` CLI as `az cognitiveservices account keys list --subscription --resource-group --name huggingface-demo -o tsv --query key1`.
-
-
-Alternatively, from the desktop application you can also open the settings and click on "Providers -> Custom Endpoints" and create the endpoint with the deployed model, then set the following:
-
-- **Name** and **Provider ID** set to "Microsoft Foundry" and "microsoft-foundry", respectively.
-- **Endpoint URL** set to "https://.openai.azure.com/openai/v1"
-- **Default Model** set to the *deployment name* not the model name, as it's the name that Microsoft Foundry uses in the top-level router to forward the requests to the deployed models.
-- **Context** set to the maximum context length supported by the model, which is usually any of 65536, 131072, 262144, 524288, etc. but check it out first in the deployment template as it's usually mentioned in the description. But note that even though the underlying model might support a larger (or shorter) context length, the one defined in the deployment template is the correct one.
-- **API Key** set to the primary key displayed in Microsoft Foundry, or rather the output of `az cognitiveservices account keys list --subscription --resource-group --name -o tsv --query key1`.
-
-
-
-## Use
-
-Finally, before using the model you can test it beforehand to make sure that everything's correctly configured, then you're all set!
-
-
+Coming soon!
diff --git a/docs/source/harness/pi.mdx b/docs/source/harness/pi.mdx
index e69de29..cb15a9d 100644
--- a/docs/source/harness/pi.mdx
+++ b/docs/source/harness/pi.mdx
@@ -0,0 +1,3 @@
+# Pi
+
+Coming soon!
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index 6c00fe0..e4cd4c7 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -33,7 +33,7 @@ response = client.chat.completions.create(
)
```
-## Where to start?
+## Get started
Before deploying a model from Microsoft Foundry, you will usually need:
@@ -42,9 +42,9 @@ Before deploying a model from Microsoft Foundry, you will usually need:
- Permission to create deployments in that project
- Enough quota in the target region for the hardware you want to use
-Start with the Getting started section:
+Follow this path:
-- [Deploy open-models from Microsoft Foundry with Python](./get-started/deploy-open-models-from-microsoft-foundry-with-python)
- This will cover the prerequisites and a simple programmatic deployment flow.
-- [Deploy open-models from Microsoft Foundry](./get-started/deploy-open-models-from-microsoft-foundry)
- This will cover the equivalent flow from the Foundry UI.
+1. [Deploy from the Foundry UI](./get-started/deploy-open-models-on-microsoft-foundry) or [deploy with Python](./get-started/deploy-open-models-on-microsoft-foundry-with-python).
+2. Start with [GLM 5.2 FP8](./large-language-models/glm-5-2-fp8) or [DeepSeek V4 Flash 0731](./large-language-models/deepseek-v4-flash-0731).
+3. Verify the deployment through its OpenAI-compatible endpoint.
+4. Connect it to an [agent harness](./agents/introduction), such as [Codex](./agents/harness-integrations/codex).
diff --git a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
new file mode 100644
index 0000000..ac23e2d
--- /dev/null
+++ b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
@@ -0,0 +1,130 @@
+# DeepSeek V4 Flash 0731
+
+[`deepseek-ai/DeepSeek-V4-Flash-0731`](https://huggingface.co/deepseek-ai/DeepSeek-V4-Flash-0731) is the official DeepSeek V4 Flash release, superseding the preview with stronger coding, tool-use, and agentic capabilities.
+
+DeepSeek V4 Flash is a mixture-of-experts model with 284B total parameters and 13B activated per token. It combines DeepSeek's compressed attention architecture with a fused DSpark speculative-decoding module, keeping inference efficient while supporting long-context workloads. The model is released under the MIT license.
+
+DeepSeek reports the following results for the `0731` release:
+
+| Benchmark | Score |
+|---|---:|
+| Terminal Bench 2.1 | 82.7 |
+| DeepSWE | 54.4 |
+| Toolathlon-Verified | 70.3 |
+| Agents' Last Exam | 25.2 |
+
+On Microsoft Foundry, it runs with vLLM using:
+
+- 8 NVIDIA H100 80 GB GPUs
+- A 524,288-token context window
+- OpenAI-compatible Chat Completions
+- `low`, `high`, and `max` reasoning-effort levels
+
+The upstream model supports up to 1,048,576 tokens. This deployment template uses 524,288 tokens to fit the model and KV cache on one 8×H100 node.
+
+## Pre-requisites
+
+- A Microsoft Azure subscription with access to Microsoft Foundry
+- A Microsoft Foundry project / account
+- Python 3.10 or higher
+
+Then install the following Python dependencies:
+
+```bash
+pip install azure-identity azure-ai-ml "azure-mgmt-cognitiveservices>=15.0.0b2" openai
+```
+
+And sign-in with the `az` CLI with `az login`.
+
+## Deployment
+
+Deploy the model programmatically with the Python SDK:
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "deepseek-ai--deepseek-v4-flash-0731"
+
+client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+deployment = client.managed_compute_deployments.begin_create_or_update(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+ resource={
+ "sku": {"name": "GlobalManagedCompute", "capacity": 1},
+ "properties": {
+ "model": "azureml://registries/azure-huggingface/models/deepseek-ai--deepseek-v4-flash-0731/versions/1",
+ "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/deepseek-ai--deepseek-v4-flash-0731--512k-nvidia-8xh100/labels/latest",
+ "acceleratorType": "H100_80GB",
+ "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
+ },
+ },
+).result()
+
+print(deployment.properties.provisioning_state)
+```
+
+
+ The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
+
+
+## Inference
+
+Use Chat Completions and pass the reasoning mode through vLLM's chat-template arguments:
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+from openai import OpenAI
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "deepseek-ai--deepseek-v4-flash-0731"
+
+az_client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+client = OpenAI(
+ base_url=f"https://{ACCOUNT_NAME}.services.ai.azure.com/openai/v1",
+ api_key=az_client.accounts.list_keys(RESOURCE_GROUP, ACCOUNT_NAME).key1,
+)
+
+response = client.chat.completions.create(
+ model=DEPLOYMENT_NAME,
+ messages=[
+ {
+ "role": "user",
+ "content": "Review this repository and propose the three highest-impact improvements.",
+ }
+ ],
+ temperature=1.0,
+ top_p=0.95,
+ extra_body={
+ "chat_template_kwargs": {
+ "thinking": True,
+ "reasoning_effort": "high",
+ }
+ },
+)
+
+print(response.choices[0].message.content)
+```
+
+Use `low` for quick tasks, `high` for most agentic work, and `max` for the hardest planning and coding tasks. DeepSeek recommends `temperature=1.0` and `top_p=0.95` for agentic scenarios.
+
+## Bonus: Use it in an agent harness
+
+Connect the deployment to one of the [agent harness integrations](../agents/introduction#harness-integrations). Confirm that the harness supports Chat Completions and the model's reasoning controls.
+
+For more model and serving details, see the [DeepSeek model card](https://huggingface.co/deepseek-ai/DeepSeek-V4-Flash-0731) and the [vLLM recipe](https://recipes.vllm.ai/deepseek-ai/DeepSeek-V4-Flash).
From b432883ce0e30cabfe334e1020605ebdc3061813 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Sun, 16 Aug 2026 19:00:04 +0200
Subject: [PATCH 08/17] Update `harness/*` and add missing Qwen3.8 27B example
(WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/harness/codex.mdx | 81 ++++++++++++++++++-
docs/source/harness/hermes-agent.mdx | 12 ++-
.../large-language-models/qwen3-8-27b.mdx | 3 +
3 files changed, 91 insertions(+), 5 deletions(-)
create mode 100644 docs/source/large-language-models/qwen3-8-27b.mdx
diff --git a/docs/source/harness/codex.mdx b/docs/source/harness/codex.mdx
index 92ec3ac..98c05cc 100644
--- a/docs/source/harness/codex.mdx
+++ b/docs/source/harness/codex.mdx
@@ -1,3 +1,82 @@
# Codex
-Coming soon!
+[Codex](https://developers.openai.com/codex/cli) is OpenAI's coding agent. The CLI works from your terminal, where it can inspect a repository, edit files, and run commands with your approval.
+
+
+
+## Install the harness
+
+On macOS or Linux, install the Codex CLI with:
+
+```bash
+curl -fsSL https://chatgpt.com/codex/install.sh | sh
+```
+
+On Windows, run:
+
+```powershell
+powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
+```
+
+You can also install Codex with [npm or Homebrew](https://github.com/openai/codex#installing-and-running-codex-cli).
+
+## Connect the model
+
+
+ This guide assumes that you already have a model running on Microsoft Foundry. If you do not, deploy one [with Python](../get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx) or [from the UI](../get-started/deploy-open-models-on-microsoft-foundry.mdx) first.
+
+
+Codex allows you to [define custom profiles to connect to custom model providers](https://learn.chatgpt.com/docs/config-file/config-advanced) through the Responses API.
+
+For example, suppose you [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo`, you can create a custom profile at `~/.codex/microsoft-foundry.config.toml` with:
+
+```toml
+model = "qwen--qwen3-8-27b"
+model_provider = "microsoft-foundry"
+model_reasoning_effort = "medium"
+
+[model_providers.microsoft-foundry]
+name = "Microsoft Foundry"
+base_url = "https://huggingface-demo.openai.azure.com/openai/v1"
+env_key = "MICROSOFT_FOUNDRY_API_KEY"
+wire_api = "responses"
+```
+
+The value of `model` must be the **deployment name**, which may differ from the model name shown in the catalog.
+
+Set the API key in the same shell where you will run Codex:
+
+```bash
+export MICROSOFT_FOUNDRY_API_KEY=""
+```
+
+For PowerShell, use:
+
+```powershell
+$env:MICROSOFT_FOUNDRY_API_KEY=""
+```
+
+You can copy the key from [Microsoft Foundry](https://ai.azure.com), or retrieve it with the Azure CLI:
+
+```bash
+az cognitiveservices account keys list \
+ --subscription \
+ --resource-group \
+ --name \
+ --query key1 \
+ --output tsv
+```
+
+
+
+## Test it!
+
+Finally, to test Codex with the open-model on Microsoft Foundry you can e.g., clone a repository and start `codex` with the previously created profile.
+
+```bash
+git clone https://github.com/huggingface/transformers.git
+cd transformers/
+codex --profile microsoft-foundry
+```
+
+
diff --git a/docs/source/harness/hermes-agent.mdx b/docs/source/harness/hermes-agent.mdx
index 452f9f5..9d7ff87 100644
--- a/docs/source/harness/hermes-agent.mdx
+++ b/docs/source/harness/hermes-agent.mdx
@@ -2,9 +2,9 @@
[Hermes Agent](https://hermes-agent.nousresearch.com/) is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.
-
+
-## Install
+## Install the harness
You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
@@ -18,7 +18,11 @@ Or on Windows as:
irm https://hermes-agent.nousresearch.com/install.ps1 | iex
```
-## Connect with Foundry
+## Connect the model
+
+
+ Here we assume that you already have a running model on Microsoft Foundry, if you don't, deploy it either [programmatically with Python](../get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx) or [from the UI](../get-started/deploy-open-models-on-microsoft-foundry.mdx).
+
Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
@@ -64,7 +68,7 @@ Alternatively, from the desktop application you can also open the settings and c

-## Use
+## Test it!
Finally, before using the model you can test it beforehand to make sure that everything's correctly configured, then you're all set!
diff --git a/docs/source/large-language-models/qwen3-8-27b.mdx b/docs/source/large-language-models/qwen3-8-27b.mdx
new file mode 100644
index 0000000..a6cabf2
--- /dev/null
+++ b/docs/source/large-language-models/qwen3-8-27b.mdx
@@ -0,0 +1,3 @@
+# Qwen3.8 27B
+
+Coming soon!
From 4d038043c247fd3f99d9b124447ae2b1aa437b6f Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Mon, 17 Aug 2026 10:32:59 +0200
Subject: [PATCH 09/17] Add `get-started/quickstart.mdx` instead (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 6 +-
...odels-on-microsoft-foundry-with-python.mdx | 98 ------------
...eploy-open-models-on-microsoft-foundry.mdx | 34 -----
docs/source/get-started/quickstart.mdx | 139 ++++++++++++++++++
docs/source/harness/codex.mdx | 2 +-
docs/source/harness/hermes-agent.mdx | 2 +-
docs/source/index.mdx | 4 +-
7 files changed, 145 insertions(+), 140 deletions(-)
delete mode 100644 docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
delete mode 100644 docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
create mode 100644 docs/source/get-started/quickstart.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 7537cef..c2075c1 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -3,10 +3,8 @@
title: Overview
title: Overview
- sections:
- - local: get-started/deploy-open-models-on-microsoft-foundry
- title: Deploy open-models on Microsoft Foundry
- - local: get-started/deploy-open-models-on-microsoft-foundry-with-python
- title: Deploy open-models on Microsoft Foundry with Python
+ - local: get-started/quickstart
+ title: Quickstart
title: Get started
- sections:
- local: large-language-models/glm-5-2-fp8
diff --git a/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
deleted file mode 100644
index 1fecd9d..0000000
--- a/docs/source/get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx
+++ /dev/null
@@ -1,98 +0,0 @@
-# Deploy open-models on Microsoft Foundry with Python
-
-Deploy open models on dedicated hardware with Microsoft Foundry Managed Compute. This example deploys [`zai-org/GLM-5.2-FP8`](https://huggingface.co/zai-org/GLM-5.2-FP8) on 8 AMD Instinct MI300X GPUs.
-
-## Prerequisites
-
-- An Azure subscription with Managed Compute preview access
-- A Microsoft Foundry account
-- `Cognitive Services Contributor` access to the account
-- Managed Compute quota for MI300X
-- Python 3.10 or later and the Azure CLI
-
-Sign in and install the dependencies:
-
-```bash
-az login
-uv pip install azure-identity "azure-mgmt-cognitiveservices>=15.0.0b2" openai
-```
-
-## Deploy the model
-
-Replace the placeholders, then run:
-
-```python
-from azure.identity import DefaultAzureCredential
-from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
-
-SUBSCRIPTION_ID = ""
-RESOURCE_GROUP = ""
-ACCOUNT_NAME = ""
-DEPLOYMENT_NAME = "zai-org--glm-5-2-fp8"
-
-client = CognitiveServicesManagementClient(
- credential=DefaultAzureCredential(),
- subscription_id=SUBSCRIPTION_ID,
-)
-
-deployment = client.managed_compute_deployments.begin_create_or_update(
- resource_group_name=RESOURCE_GROUP,
- account_name=ACCOUNT_NAME,
- deployment_name=DEPLOYMENT_NAME,
- resource={
- "sku": {"name": "GlobalManagedCompute", "capacity": 1},
- "properties": {
- "model": "azureml://registries/azure-huggingface/models/zai-org--glm-5.2-fp8/versions/5",
- "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/zai-org--glm-52-fp8--512k-amd-8xmi300x/labels/latest",
- "acceleratorType": "MI300_192GB",
- "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
- },
- },
-).result()
-
-print(deployment.properties.provisioning_state)
-```
-
-Provisioning is blocking and usually takes 15–20 minutes. The deployment is ready when its state is `Succeeded`.
-
-The model and deployment template IDs are model-specific. Copy them from the deployment wizard when deploying a different model.
-
-## Send a request
-
-```python
-from openai import OpenAI
-
-api_key = client.accounts.list_keys(
- resource_group_name=RESOURCE_GROUP,
- account_name=ACCOUNT_NAME,
-).key1
-
-inference = OpenAI(
- base_url=f"https://{ACCOUNT_NAME}.services.ai.azure.com/openai/v1",
- api_key=api_key,
-)
-
-response = inference.responses.create(
- model=DEPLOYMENT_NAME,
- input="How does Hugging Face make money?",
- reasoning={"effort": "none"},
-)
-
-print(response.output_text)
-```
-
-Use the deployment name in `model`, not the Foundry model name or Hugging Face model ID.
-
-## Delete the deployment
-
-Delete unused deployments to stop billing:
-
-```python
-client.managed_compute_deployments.begin_delete(
- resource_group_name=RESOURCE_GROUP,
- account_name=ACCOUNT_NAME,
- deployment_name=DEPLOYMENT_NAME,
-).result()
-```
-
-For more context, see the [original GLM 5.2 walkthrough](https://alvarobartt.com/goal-glm-5.2-on-foundry) and the [Managed Compute documentation](https://learn.microsoft.com/azure/foundry/how-to/deploy-models-managed).
diff --git a/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx b/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
deleted file mode 100644
index abd5dfb..0000000
--- a/docs/source/get-started/deploy-open-models-on-microsoft-foundry.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
-# Deploy open-models on Microsoft Foundry
-
-Use Managed Compute to deploy open models on dedicated hardware without managing the serving stack.
-
-## Prerequisites
-
-- An Azure subscription and Microsoft Foundry account
-- Permission to create deployments
-- Managed Compute quota for the required accelerator
-
-## Find a model
-
-1. Open [Microsoft Foundry](https://ai.azure.com).
-2. Go to **Discover → Models**.
-3. Filter **Collection** by **Hugging Face**.
-4. Select a model and choose **Deploy**.
-
-## Deploy
-
-1. Enter a deployment name.
-2. Keep **Global Managed Compute** as the deployment type.
-3. Choose a compatible deployment template and accelerator.
-4. Start with one model instance.
-5. Acknowledge the cost and select **Deploy**.
-
-Provisioning usually takes 10–20 minutes. Wait for the deployment state to become `Succeeded`.
-
-## Test and monitor
-
-Open the deployment's **Playground** tab to send a request. Use **Monitor** to inspect request count, latency, token usage, and errors.
-
-The deployment name is the value applications pass in the API's `model` field.
-
-Delete unused deployments to release their accelerators and stop billing. For programmatic deployment, see [Deploy open-models on Microsoft Foundry with Python](./deploy-open-models-on-microsoft-foundry-with-python).
diff --git a/docs/source/get-started/quickstart.mdx b/docs/source/get-started/quickstart.mdx
new file mode 100644
index 0000000..3897a13
--- /dev/null
+++ b/docs/source/get-started/quickstart.mdx
@@ -0,0 +1,139 @@
+# Quickstart
+
+Deploy a Hugging Face model on Microsoft Foundry, test it in the Playground, and call it from an application. You can use the Foundry portal for a guided setup or the Python SDK for a repeatable deployment.
+
+## Before you begin
+
+You need:
+
+- An Azure subscription and a Microsoft Foundry project
+- `Cognitive Services Contributor` access to create the deployment
+- `Foundry User` access to call it from the Playground
+- Managed compute quota for the accelerator used by your model
+
+Managed compute is currently in preview and uses dedicated GPU capacity. Delete deployments that you no longer need to stop billing.
+
+## Choose a deployment path
+
+| Foundry portal | Python SDK |
+|---|---|
+| The quickest path for a first deployment. [Start in the portal](#foundry-portal). | Best for automation and repeatable environments. [Start with Python](#python-sdk). |
+
+Both paths create the same type of managed compute deployment. Choose one, then continue to [Test the deployment](#test-the-deployment).
+
+## Foundry portal
+
+1. Open [Microsoft Foundry](https://ai.azure.com) and select your project.
+2. Go to **Discover → Models**. Filter **Collection** by **Hugging Face** and **Deployment options** by **Managed compute**.
+3. Select a model, choose **Deploy**, and enter a deployment name. Keep one instance for your first deployment, then select a compatible deployment template and accelerator.
+4. Select **Deploy** and wait for the deployment state to become `Succeeded`.
+
+Provisioning often takes 10–20 minutes and can take longer when accelerator capacity is limited.
+
+## Python SDK
+
+Install the dependencies and sign in to Azure:
+
+```bash
+pip install azure-identity "azure-mgmt-cognitiveservices>=15.0.0b2" openai
+az login
+```
+
+Open the model's deployment wizard in Foundry and copy its **Model ID**, **Deployment template ID**, and **Accelerator type**. Replace the placeholders below, then run the script:
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = ""
+
+MODEL = ""
+TEMPLATE = ""
+ACCELERATOR_TYPE = ""
+
+management_client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
+
+deployment = management_client.managed_compute_deployments.begin_create_or_update(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+ resource={
+ "sku": {"name": "GlobalManagedCompute", "capacity": 1},
+ "properties": {
+ "model": MODEL,
+ "deploymentTemplate": TEMPLATE,
+ "acceleratorType": ACCELERATOR_TYPE,
+ "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
+ },
+ },
+).result()
+
+print(deployment.properties.provisioning_state)
+```
+
+The call waits for provisioning to finish. The deployment is ready when it prints `Succeeded`.
+
+## Test the deployment
+
+Open the deployment in Foundry and select **Playground**. Send a simple prompt, such as:
+
+```text
+Explain what this model is best suited for in three short bullet points.
+```
+
+If the model responds, the deployment is ready. Applications must use the **deployment name** in the API's `model` field, not the model name from the catalog.
+
+## Call the model from Python
+
+Copy the endpoint and API key from the deployment page, then install the OpenAI client if you did not use the Python deployment path:
+
+```bash
+pip install openai
+```
+
+For a model that supports the Responses API:
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://.services.ai.azure.com/openai/v1",
+ api_key="",
+)
+
+response = client.responses.create(
+ model="",
+ input="Write a one-sentence hello from Microsoft Foundry.",
+)
+
+print(response.output_text)
+```
+
+Check the model card or deployment page for its supported API. Some models use Chat Completions instead of Responses.
+
+## Clean up
+
+Delete deployments that you are not using to release their accelerators and stop billing.
+
+- In Foundry, open the deployments list, select the deployment, and choose **Delete**.
+- If you deployed with Python, use the management client created earlier:
+
+```python
+management_client.managed_compute_deployments.begin_delete(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+).result()
+```
+
+## Next steps
+
+- Try a model-specific guide for [GLM 5.2 FP8](../large-language-models/glm-5-2-fp8) or [DeepSeek V4 Flash 0731](../large-language-models/deepseek-v4-flash-0731).
+- Connect a Responses-compatible deployment to [Codex](../harness/codex) or another supported harness.
+- See the [Managed compute documentation](https://learn.microsoft.com/azure/foundry/how-to/deploy-models-managed) for quota, monitoring, scaling, and troubleshooting.
diff --git a/docs/source/harness/codex.mdx b/docs/source/harness/codex.mdx
index 98c05cc..9edd34b 100644
--- a/docs/source/harness/codex.mdx
+++ b/docs/source/harness/codex.mdx
@@ -23,7 +23,7 @@ You can also install Codex with [npm or Homebrew](https://github.com/openai/code
## Connect the model
- This guide assumes that you already have a model running on Microsoft Foundry. If you do not, deploy one [with Python](../get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx) or [from the UI](../get-started/deploy-open-models-on-microsoft-foundry.mdx) first.
+ This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
Codex allows you to [define custom profiles to connect to custom model providers](https://learn.chatgpt.com/docs/config-file/config-advanced) through the Responses API.
diff --git a/docs/source/harness/hermes-agent.mdx b/docs/source/harness/hermes-agent.mdx
index 9d7ff87..875b2aa 100644
--- a/docs/source/harness/hermes-agent.mdx
+++ b/docs/source/harness/hermes-agent.mdx
@@ -21,7 +21,7 @@ irm https://hermes-agent.nousresearch.com/install.ps1 | iex
## Connect the model
- Here we assume that you already have a running model on Microsoft Foundry, if you don't, deploy it either [programmatically with Python](../get-started/deploy-open-models-on-microsoft-foundry-with-python.mdx) or [from the UI](../get-started/deploy-open-models-on-microsoft-foundry.mdx).
+ This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index e4cd4c7..6964bc3 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -44,7 +44,7 @@ Before deploying a model from Microsoft Foundry, you will usually need:
Follow this path:
-1. [Deploy from the Foundry UI](./get-started/deploy-open-models-on-microsoft-foundry) or [deploy with Python](./get-started/deploy-open-models-on-microsoft-foundry-with-python).
+1. Follow the [quickstart](./get-started/quickstart) to deploy from the Foundry portal or with Python.
2. Start with [GLM 5.2 FP8](./large-language-models/glm-5-2-fp8) or [DeepSeek V4 Flash 0731](./large-language-models/deepseek-v4-flash-0731).
3. Verify the deployment through its OpenAI-compatible endpoint.
-4. Connect it to an [agent harness](./agents/introduction), such as [Codex](./agents/harness-integrations/codex).
+4. Connect it to an agent harness, such as [Codex](./harness/codex) or [Hermes Agent](./harness/hermes-agent).
From 224b91a772b687e19cc3b67c2fe4db59fd402f3c Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Mon, 17 Aug 2026 14:54:55 +0200
Subject: [PATCH 10/17] Add `harness/overview.mdx` (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 2 +
docs/source/harness/index.mdx | 71 +++++++++++++++++++++++++++++++++++
2 files changed, 73 insertions(+)
create mode 100644 docs/source/harness/index.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index c2075c1..7b6be11 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -15,6 +15,8 @@
title: Qwen3.8 27B
title: Large Language Models
- sections:
+ - local: harness/index
+ title: Overview
- local: harness/claude-code
title: Claude Code (Coming soon)
- local: harness/codex
diff --git a/docs/source/harness/index.mdx b/docs/source/harness/index.mdx
new file mode 100644
index 0000000..a09a746
--- /dev/null
+++ b/docs/source/harness/index.mdx
@@ -0,0 +1,71 @@
+# Harness
+
+An agent harness is the application that drives a model: it holds the conversation, exposes tools such as file edits or shell commands, and decides what to send back to the model on every turn. Any harness that speaks the OpenAI Chat Completions API or the Responses API can point at a model deployed on Microsoft Foundry.
+
+
+ These guides assume that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
+
+
+Pick a harness to connect it to your Foundry deployment:
+
+
From efccbaadf8c1503d47bbe6f6e3a32c3ac185a075 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 19 Aug 2026 12:42:46 +0200
Subject: [PATCH 11/17] Fix `docs/source/harness/index.mdx`
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/harness/index.mdx | 3 ---
1 file changed, 3 deletions(-)
diff --git a/docs/source/harness/index.mdx b/docs/source/harness/index.mdx
index a09a746..dd2b217 100644
--- a/docs/source/harness/index.mdx
+++ b/docs/source/harness/index.mdx
@@ -23,7 +23,6 @@ Pick a harness to connect it to your Foundry deployment:
OpenAI's coding agent for the terminal
-
Nous Research's self-improving agent
-
Coming soon
-
Date: Wed, 19 Aug 2026 12:46:30 +0200
Subject: [PATCH 12/17] Fix `overview` and `harness` index pages
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 6 ++----
.../source/large-language-models/deepseek-v4-flash-0731.mdx | 2 +-
2 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 7b6be11..0612036 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -1,6 +1,5 @@
- sections:
- - local: index
- title: Overview
+ local: index
title: Overview
- sections:
- local: get-started/quickstart
@@ -15,8 +14,6 @@
title: Qwen3.8 27B
title: Large Language Models
- sections:
- - local: harness/index
- title: Overview
- local: harness/claude-code
title: Claude Code (Coming soon)
- local: harness/codex
@@ -25,4 +22,5 @@
title: Hermes Agent
- local: harness/pi
title: Pi (Coming soon)
+ local: harness/index
title: Harness
diff --git a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
index ac23e2d..9ccf596 100644
--- a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
+++ b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
@@ -125,6 +125,6 @@ Use `low` for quick tasks, `high` for most agentic work, and `max` for the harde
## Bonus: Use it in an agent harness
-Connect the deployment to one of the [agent harness integrations](../agents/introduction#harness-integrations). Confirm that the harness supports Chat Completions and the model's reasoning controls.
+Connect the deployment to a compatible harness, such as [Hermes Agent](../harness/hermes-agent). Confirm that the harness supports Chat Completions and the model's reasoning controls.
For more model and serving details, see the [DeepSeek model card](https://huggingface.co/deepseek-ai/DeepSeek-V4-Flash-0731) and the [vLLM recipe](https://recipes.vllm.ai/deepseek-ai/DeepSeek-V4-Flash).
From 248691bc7bacbdf02bea01f7174553c5c2d05255 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 19 Aug 2026 13:18:07 +0200
Subject: [PATCH 13/17] Add more custom HTML (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 16 +-
docs/source/advanced/reasoning.mdx | 64 +++
docs/source/catalog/deepseek-ai.mdx | 30 ++
docs/source/catalog/qwen.mdx | 531 +++++++++++++++++++++++++
docs/source/get-started/quickstart.mdx | 109 +++--
docs/source/index.mdx | 77 ++--
6 files changed, 735 insertions(+), 92 deletions(-)
create mode 100644 docs/source/advanced/reasoning.mdx
create mode 100644 docs/source/catalog/deepseek-ai.mdx
create mode 100644 docs/source/catalog/qwen.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 0612036..4a82cd0 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -1,6 +1,13 @@
- sections:
- local: index
+ - local: index
+ title: Overview
title: Overview
+- sections:
+ - local: catalog/qwen
+ title: Qwen
+ - local: catalog/deepseek-ai
+ title: DeepSeek AI
+ title: Catalog
- sections:
- local: get-started/quickstart
title: Quickstart
@@ -14,6 +21,8 @@
title: Qwen3.8 27B
title: Large Language Models
- sections:
+ - local: harness/index
+ title: Overview
- local: harness/claude-code
title: Claude Code (Coming soon)
- local: harness/codex
@@ -22,5 +31,8 @@
title: Hermes Agent
- local: harness/pi
title: Pi (Coming soon)
- local: harness/index
title: Harness
+- sections:
+ - local: advanced/reasoning
+ title: Enable and disable reasoning
+ title: Advanced
diff --git a/docs/source/advanced/reasoning.mdx b/docs/source/advanced/reasoning.mdx
new file mode 100644
index 0000000..27fed92
--- /dev/null
+++ b/docs/source/advanced/reasoning.mdx
@@ -0,0 +1,64 @@
+# Enable and disable reasoning
+
+Many of the models in the collection are hybrid reasoning models: they can answer directly, or think first and then answer. The mode is chosen per request, so a single deployment covers both, and you do not need to redeploy to switch.
+
+Reasoning costs latency and output tokens, so it is worth turning off for classification, extraction, or short chat turns, and on for planning, coding, and agentic work.
+
+## Chat Completions
+
+The switch lives in the model's chat template, and vLLM exposes the template arguments through `extra_body`:
+
+```python
+from openai import OpenAI
+
+client = OpenAI(
+ base_url="https://.services.ai.azure.com/openai/v1",
+ api_key="",
+)
+
+response = client.chat.completions.create(
+ model="",
+ messages=[{"role": "user", "content": "Sort these tickets by urgency."}],
+ extra_body={"chat_template_kwargs": {"enable_thinking": False}},
+)
+
+print(response.choices[0].message.content)
+```
+
+The argument name is defined by the model, not by the API, so check the model page before using it:
+
+| Model | Argument | Values |
+|---|---|---|
+| Qwen3 and Qwen3.x | `enable_thinking` | `True`, `False` |
+| DeepSeek V4 Flash 0731 | `thinking`, `reasoning_effort` | `True` / `False`, and `low`, `high`, `max` |
+
+When reasoning is enabled and the deployment runs with a reasoning parser, the thinking trace comes back separately from the answer, in `reasoning_content`:
+
+```python
+print(response.choices[0].message.reasoning_content)
+print(response.choices[0].message.content)
+```
+
+Send the `content` of an assistant turn back in the conversation history, but not its `reasoning_content`.
+
+## Responses API
+
+Models served through the Responses API take a reasoning effort instead of a boolean:
+
+```python
+response = client.responses.create(
+ model="",
+ input="Build a small FastAPI health-check endpoint.",
+ reasoning={"effort": "high"},
+)
+
+print(response.output_text)
+```
+
+
+ Agent harnesses usually set the reasoning effort themselves, so configure it there rather than per request. See [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
+
+
+## Models without a switch
+
+Some models are reasoning-only, such as [QwQ-32B](../catalog/qwen) and Qwen3-30B-A3B-Thinking-2507, and others never emit a thinking trace, such as the `Instruct` variants. Passing the argument to those models has no effect on the output.
diff --git a/docs/source/catalog/deepseek-ai.mdx b/docs/source/catalog/deepseek-ai.mdx
new file mode 100644
index 0000000..b535106
--- /dev/null
+++ b/docs/source/catalog/deepseek-ai.mdx
@@ -0,0 +1,30 @@
+# DeepSeek AI
+
+[DeepSeek AI](https://huggingface.co/deepseek-ai) builds open mixture-of-experts models for reasoning, coding, and agentic workloads, with long context windows and efficient inference.
+
+Every card links to the latest version of the model in the `azure-huggingface` registry on Microsoft Foundry, and shows its input and output modalities:
+
+
diff --git a/docs/source/catalog/qwen.mdx b/docs/source/catalog/qwen.mdx
new file mode 100644
index 0000000..50c6630
--- /dev/null
+++ b/docs/source/catalog/qwen.mdx
@@ -0,0 +1,531 @@
+# Qwen
+
+[Qwen](https://huggingface.co/Qwen) is Alibaba Cloud's open model family, spanning dense and mixture-of-experts text models, vision-language models, embeddings, and image generation. It is the largest family in the Hugging Face collection on Microsoft Foundry.
+
+Every card links to the latest version of the model in the `azure-huggingface` registry on Microsoft Foundry, and shows its input and output modalities:
+
+
diff --git a/docs/source/get-started/quickstart.mdx b/docs/source/get-started/quickstart.mdx
index 3897a13..1aefcc2 100644
--- a/docs/source/get-started/quickstart.mdx
+++ b/docs/source/get-started/quickstart.mdx
@@ -1,6 +1,6 @@
# Quickstart
-Deploy a Hugging Face model on Microsoft Foundry, test it in the Playground, and call it from an application. You can use the Foundry portal for a guided setup or the Python SDK for a repeatable deployment.
+Deploy a model from the Hugging Face collection on Microsoft Foundry, then call it from Python.
## Before you begin
@@ -8,67 +8,62 @@ You need:
- An Azure subscription and a Microsoft Foundry project
- `Cognitive Services Contributor` access to create the deployment
-- `Foundry User` access to call it from the Playground
-- Managed compute quota for the accelerator used by your model
+- Managed compute quota for the accelerator that your model requires
-Managed compute is currently in preview and uses dedicated GPU capacity. Delete deployments that you no longer need to stop billing.
+
+ Managed compute runs on dedicated GPU capacity and bills for as long as the deployment exists. Delete the deployments that you no longer need.
+
-## Choose a deployment path
+## Deploy a model
-| Foundry portal | Python SDK |
-|---|---|
-| The quickest path for a first deployment. [Start in the portal](#foundry-portal). | Best for automation and repeatable environments. [Start with Python](#python-sdk). |
+Pick the Foundry portal for a first, guided deployment, or Python for a repeatable one. Both create the same managed compute deployment.
-Both paths create the same type of managed compute deployment. Choose one, then continue to [Test the deployment](#test-the-deployment).
-
-## Foundry portal
+
+
1. Open [Microsoft Foundry](https://ai.azure.com) and select your project.
-2. Go to **Discover → Models**. Filter **Collection** by **Hugging Face** and **Deployment options** by **Managed compute**.
-3. Select a model, choose **Deploy**, and enter a deployment name. Keep one instance for your first deployment, then select a compatible deployment template and accelerator.
-4. Select **Deploy** and wait for the deployment state to become `Succeeded`.
+2. Go to **Discover → Models**, and filter **Collection** by **Hugging Face** and **Deployment options** by **Managed compute**.
+3. Select a model and choose **Deploy**.
+4. Enter a deployment name, pick a deployment template and its accelerator, and select **Deploy**.
-Provisioning often takes 10–20 minutes and can take longer when accelerator capacity is limited.
+The deployment is ready when its state becomes `Succeeded`.
-## Python SDK
+
+
-Install the dependencies and sign in to Azure:
+Install the dependencies and sign in:
```bash
pip install azure-identity "azure-mgmt-cognitiveservices>=15.0.0b2" openai
az login
```
-Open the model's deployment wizard in Foundry and copy its **Model ID**, **Deployment template ID**, and **Accelerator type**. Replace the placeholders below, then run the script:
+Copy the **Model ID**, **Deployment template ID**, and **Accelerator type** from the model's deployment wizard in Foundry, then run:
```python
from azure.identity import DefaultAzureCredential
from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
-SUBSCRIPTION_ID = ""
-RESOURCE_GROUP = ""
-ACCOUNT_NAME = ""
-DEPLOYMENT_NAME = ""
-
-MODEL = ""
-TEMPLATE = ""
-ACCELERATOR_TYPE = ""
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "qwen--qwen3-8-27b"
-management_client = CognitiveServicesManagementClient(
+client = CognitiveServicesManagementClient(
credential=DefaultAzureCredential(),
subscription_id=SUBSCRIPTION_ID,
)
-deployment = management_client.managed_compute_deployments.begin_create_or_update(
+deployment = client.managed_compute_deployments.begin_create_or_update(
resource_group_name=RESOURCE_GROUP,
account_name=ACCOUNT_NAME,
deployment_name=DEPLOYMENT_NAME,
resource={
"sku": {"name": "GlobalManagedCompute", "capacity": 1},
"properties": {
- "model": MODEL,
- "deploymentTemplate": TEMPLATE,
- "acceleratorType": ACCELERATOR_TYPE,
+ "model": "azureml://registries/azure-huggingface/models/qwen--qwen3.8-27b/versions/2",
+ "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/qwen--qwen3-8-27b--256k-nvidia-h100/labels/latest",
+ "acceleratorType": "H100_80GB",
"versionUpgradeOption": "OnceNewDefaultVersionAvailable",
},
},
@@ -77,55 +72,43 @@ deployment = management_client.managed_compute_deployments.begin_create_or_updat
print(deployment.properties.provisioning_state)
```
-The call waits for provisioning to finish. The deployment is ready when it prints `Succeeded`.
-
-## Test the deployment
-
-Open the deployment in Foundry and select **Playground**. Send a simple prompt, such as:
-
-```text
-Explain what this model is best suited for in three short bullet points.
-```
-
-If the model responds, the deployment is ready. Applications must use the **deployment name** in the API's `model` field, not the model name from the catalog.
+The call returns when provisioning finishes, and prints `Succeeded`.
-## Call the model from Python
+
+
-Copy the endpoint and API key from the deployment page, then install the OpenAI client if you did not use the Python deployment path:
+
+ The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
+
-```bash
-pip install openai
-```
+## Call the deployment
-For a model that supports the Responses API:
+Copy the endpoint and key from the deployment page, and use the **deployment name** as the `model`:
```python
from openai import OpenAI
client = OpenAI(
- base_url="https://.services.ai.azure.com/openai/v1",
- api_key="",
+ base_url="https://.services.ai.azure.com/openai/v1",
+ api_key="",
)
-response = client.responses.create(
- model="",
- input="Write a one-sentence hello from Microsoft Foundry.",
+response = client.chat.completions.create(
+ model="",
+ messages=[{"role": "user", "content": "Write a one-sentence hello from Microsoft Foundry."}],
)
-print(response.output_text)
+print(response.choices[0].message.content)
```
-Check the model card or deployment page for its supported API. Some models use Chat Completions instead of Responses.
+Some models are served through the Responses API instead, at `/openai/v1/responses`. Check the model page for the API that it supports.
## Clean up
-Delete deployments that you are not using to release their accelerators and stop billing.
-
-- In Foundry, open the deployments list, select the deployment, and choose **Delete**.
-- If you deployed with Python, use the management client created earlier:
+Delete the deployment to release its accelerators and stop billing, either from its page in Foundry or with:
```python
-management_client.managed_compute_deployments.begin_delete(
+client.managed_compute_deployments.begin_delete(
resource_group_name=RESOURCE_GROUP,
account_name=ACCOUNT_NAME,
deployment_name=DEPLOYMENT_NAME,
@@ -134,6 +117,6 @@ management_client.managed_compute_deployments.begin_delete(
## Next steps
-- Try a model-specific guide for [GLM 5.2 FP8](../large-language-models/glm-5-2-fp8) or [DeepSeek V4 Flash 0731](../large-language-models/deepseek-v4-flash-0731).
-- Connect a Responses-compatible deployment to [Codex](../harness/codex) or another supported harness.
-- See the [Managed compute documentation](https://learn.microsoft.com/azure/foundry/how-to/deploy-models-managed) for quota, monitoring, scaling, and troubleshooting.
+- Browse the [catalog](../catalog/qwen) to pick a model.
+- Turn reasoning on or off per request in [Enable and disable reasoning](../advanced/reasoning).
+- Connect the deployment to a harness such as [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index 6964bc3..acd2a71 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -2,49 +2,72 @@

-Hugging Face and Microsoft work together to make open models easier to discover and deploy on Microsoft Foundry. The Hugging Face collection in Foundry brings a large catalog of open models into the Foundry experience so teams can deploy them from the UI or from Python without building the full serving stack themselves.
+Hugging Face and Microsoft bring a curated collection of open models to Microsoft Foundry. You deploy a model on managed compute from the Foundry portal or from Python, and call it behind an OpenAI-compatible endpoint, without building or maintaining the serving stack yourself.
-With Hugging Face on Microsoft Foundry, you can:
+## Catalog
-- Discover open models from the Hugging Face catalog directly in Microsoft Foundry.
-- Deploy supported models from the UI or programmatically from Python.
-- Use the resulting deployments behind Foundry-managed endpoints.
-- Build applications, agents, and examples on top of those deployments.
+The collection lives in the `azure-huggingface` registry and shows up in the Foundry model catalog, where you can filter by **Collection: Hugging Face** and **Deployment options: Managed compute**.
-## Microsoft Foundry
+
-The Hugging Face collection is available from the Foundry model catalog, where you can filter models by family, modality, task, and deployment option before starting a deployment.
+Each model is published as a versioned asset in the registry, with one or more deployment templates that pin the serving engine, the context window, and the accelerator it runs on. Browse the collection by family in the [catalog](./catalog/qwen), where every entry links to the latest version of the model on Microsoft Foundry.
-
+## Deploy a model
+
+```python
+from azure.identity import DefaultAzureCredential
+from azure.mgmt.cognitiveservices import CognitiveServicesManagementClient
+
+SUBSCRIPTION_ID = ""
+RESOURCE_GROUP = ""
+ACCOUNT_NAME = ""
+DEPLOYMENT_NAME = "qwen--qwen3-8-27b"
+
+client = CognitiveServicesManagementClient(
+ credential=DefaultAzureCredential(),
+ subscription_id=SUBSCRIPTION_ID,
+)
-Once a deployment is ready, you can call it through the Foundry endpoint with a standard OpenAI-compatible client:
+deployment = client.managed_compute_deployments.begin_create_or_update(
+ resource_group_name=RESOURCE_GROUP,
+ account_name=ACCOUNT_NAME,
+ deployment_name=DEPLOYMENT_NAME,
+ resource={
+ "sku": {"name": "GlobalManagedCompute", "capacity": 1},
+ "properties": {
+ "model": "azureml://registries/azure-huggingface/models/qwen--qwen3.8-27b/versions/2",
+ "deploymentTemplate": "azureml://registries/azure-huggingface/deploymenttemplates/qwen--qwen3-8-27b--256k-nvidia-h100/labels/latest",
+ "acceleratorType": "H100_80GB",
+ "versionUpgradeOption": "OnceNewDefaultVersionAvailable",
+ },
+ },
+).result()
+
+print(deployment.properties.provisioning_state)
+```
+
+## Run inference
+
+Once the deployment reports `Succeeded`, call it with the OpenAI SDK. The `model` field takes the **deployment name**, not the model name from the catalog:
```python
from openai import OpenAI
client = OpenAI(
- base_url="https://.services.ai.azure.com/openai/v1/",
- api_key="",
+ base_url=f"https://{ACCOUNT_NAME}.services.ai.azure.com/openai/v1",
+ api_key="",
)
response = client.chat.completions.create(
- model="",
+ model=DEPLOYMENT_NAME,
messages=[{"role": "user", "content": "Hello from Microsoft Foundry."}],
)
-```
-## Get started
-
-Before deploying a model from Microsoft Foundry, you will usually need:
-
-- An Azure subscription
-- A Microsoft Foundry project
-- Permission to create deployments in that project
-- Enough quota in the target region for the hardware you want to use
+print(response.choices[0].message.content)
+```
-Follow this path:
+## Next steps
-1. Follow the [quickstart](./get-started/quickstart) to deploy from the Foundry portal or with Python.
-2. Start with [GLM 5.2 FP8](./large-language-models/glm-5-2-fp8) or [DeepSeek V4 Flash 0731](./large-language-models/deepseek-v4-flash-0731).
-3. Verify the deployment through its OpenAI-compatible endpoint.
-4. Connect it to an agent harness, such as [Codex](./harness/codex) or [Hermes Agent](./harness/hermes-agent).
+- Deploy your first model from the portal or from Python in the [quickstart](./get-started/quickstart).
+- Turn reasoning on or off per request in [Enable and disable reasoning](./advanced/reasoning).
+- Connect a deployment to an agent harness such as [Codex](./harness/codex) or [Hermes Agent](./harness/hermes-agent).
From d3bc69bfedc7fd14746edea985bb6b87983d528b Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 19 Aug 2026 13:34:54 +0200
Subject: [PATCH 14/17] Extend catalog, use GitHub-like tips, and more (WIP)
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 4 +
docs/source/advanced/reasoning.mdx | 5 +-
docs/source/catalog/deepseek-ai.mdx | 32 +-
docs/source/catalog/microsoft.mdx | 112 +++
docs/source/catalog/nvidia.mdx | 453 ++++++++++++
docs/source/catalog/qwen.mdx | 653 ++++++++++++------
docs/source/get-started/quickstart.mdx | 14 +-
docs/source/harness/codex.mdx | 15 +-
docs/source/harness/hermes-agent.mdx | 18 +-
docs/source/harness/index.mdx | 47 +-
docs/source/index.mdx | 2 +-
.../deepseek-v4-flash-0731.mdx | 9 +-
.../large-language-models/glm-5-2-fp8.mdx | 7 +-
13 files changed, 1067 insertions(+), 304 deletions(-)
create mode 100644 docs/source/catalog/microsoft.mdx
create mode 100644 docs/source/catalog/nvidia.mdx
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 4a82cd0..960b3e9 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -7,6 +7,10 @@
title: Qwen
- local: catalog/deepseek-ai
title: DeepSeek AI
+ - local: catalog/nvidia
+ title: NVIDIA
+ - local: catalog/microsoft
+ title: Microsoft
title: Catalog
- sections:
- local: get-started/quickstart
diff --git a/docs/source/advanced/reasoning.mdx b/docs/source/advanced/reasoning.mdx
index 27fed92..8b63cc7 100644
--- a/docs/source/advanced/reasoning.mdx
+++ b/docs/source/advanced/reasoning.mdx
@@ -55,9 +55,8 @@ response = client.responses.create(
print(response.output_text)
```
-
- Agent harnesses usually set the reasoning effort themselves, so configure it there rather than per request. See [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
-
+> [!TIP]
+> Agent harnesses usually set the reasoning effort themselves, so configure it there rather than per request. See [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
## Models without a switch
diff --git a/docs/source/catalog/deepseek-ai.mdx b/docs/source/catalog/deepseek-ai.mdx
index b535106..d313745 100644
--- a/docs/source/catalog/deepseek-ai.mdx
+++ b/docs/source/catalog/deepseek-ai.mdx
@@ -1,30 +1,38 @@
# DeepSeek AI
-[DeepSeek AI](https://huggingface.co/deepseek-ai) builds open mixture-of-experts models for reasoning, coding, and agentic workloads, with long context windows and efficient inference.
-
-Every card links to the latest version of the model in the `azure-huggingface` registry on Microsoft Foundry, and shows its input and output modalities:
+DeepSeek AI is a Chinese AI research company that releases open mixture-of-experts models built for reasoning, coding, and agentic work over long contexts.
diff --git a/docs/source/catalog/microsoft.mdx b/docs/source/catalog/microsoft.mdx
new file mode 100644
index 0000000..23fea6c
--- /dev/null
+++ b/docs/source/catalog/microsoft.mdx
@@ -0,0 +1,112 @@
+# Microsoft
+
+Microsoft releases the Phi family of small language models, along with domain-tuned variants such as MediPhi for clinical text.
+
+
diff --git a/docs/source/catalog/nvidia.mdx b/docs/source/catalog/nvidia.mdx
new file mode 100644
index 0000000..e99339b
--- /dev/null
+++ b/docs/source/catalog/nvidia.mdx
@@ -0,0 +1,453 @@
+# NVIDIA
+
+NVIDIA releases the Nemotron and Cosmos families, together with FP8 and NVFP4 quantizations of them that lower the accelerator footprint needed to serve each model.
+
+
diff --git a/docs/source/catalog/qwen.mdx b/docs/source/catalog/qwen.mdx
index 50c6630..90f8686 100644
--- a/docs/source/catalog/qwen.mdx
+++ b/docs/source/catalog/qwen.mdx
@@ -1,531 +1,726 @@
# Qwen
-[Qwen](https://huggingface.co/Qwen) is Alibaba Cloud's open model family, spanning dense and mixture-of-experts text models, vision-language models, embeddings, and image generation. It is the largest family in the Hugging Face collection on Microsoft Foundry.
-
-Every card links to the latest version of the model in the `azure-huggingface` registry on Microsoft Foundry, and shows its input and output modalities:
+Qwen is the open model family from Alibaba Cloud, released under permissive licenses and covering text, vision-language, coding, embedding, and image generation models.
- TText
- Image
- Video
- Embeddings
+ TText
+ Image
+ Video
+ Embeddings
diff --git a/docs/source/get-started/quickstart.mdx b/docs/source/get-started/quickstart.mdx
index 1aefcc2..52b0f7f 100644
--- a/docs/source/get-started/quickstart.mdx
+++ b/docs/source/get-started/quickstart.mdx
@@ -10,9 +10,8 @@ You need:
- `Cognitive Services Contributor` access to create the deployment
- Managed compute quota for the accelerator that your model requires
-
- Managed compute runs on dedicated GPU capacity and bills for as long as the deployment exists. Delete the deployments that you no longer need.
-
+> [!WARNING]
+> Managed compute runs on dedicated GPU capacity and bills for as long as the deployment exists. Delete the deployments that you no longer need.
## Deploy a model
@@ -21,7 +20,7 @@ Pick the Foundry portal for a first, guided deployment, or Python for a repeatab
-1. Open [Microsoft Foundry](https://ai.azure.com) and select your project.
+1. Open Microsoft Foundry and select your project.
2. Go to **Discover → Models**, and filter **Collection** by **Hugging Face** and **Deployment options** by **Managed compute**.
3. Select a model and choose **Deploy**.
4. Enter a deployment name, pick a deployment template and its accelerator, and select **Deploy**.
@@ -77,9 +76,8 @@ The call returns when provisioning finishes, and prints `Succeeded`.
-
- The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
-
+> [!TIP]
+> The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
## Call the deployment
@@ -117,6 +115,6 @@ client.managed_compute_deployments.begin_delete(
## Next steps
-- Browse the [catalog](../catalog/qwen) to pick a model.
+- Browse the catalog to pick a model: [Qwen](../catalog/qwen), [DeepSeek AI](../catalog/deepseek-ai), [NVIDIA](../catalog/nvidia), [Microsoft](../catalog/microsoft).
- Turn reasoning on or off per request in [Enable and disable reasoning](../advanced/reasoning).
- Connect the deployment to a harness such as [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
diff --git a/docs/source/harness/codex.mdx b/docs/source/harness/codex.mdx
index 9edd34b..27fb0eb 100644
--- a/docs/source/harness/codex.mdx
+++ b/docs/source/harness/codex.mdx
@@ -1,6 +1,6 @@
# Codex
-[Codex](https://developers.openai.com/codex/cli) is OpenAI's coding agent. The CLI works from your terminal, where it can inspect a repository, edit files, and run commands with your approval.
+Codex is OpenAI's coding agent. The CLI works from your terminal, where it can inspect a repository, edit files, and run commands with your approval.

@@ -18,17 +18,16 @@ On Windows, run:
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"
```
-You can also install Codex with [npm or Homebrew](https://github.com/openai/codex#installing-and-running-codex-cli).
+You can also install Codex with npm or Homebrew.
## Connect the model
-
- This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
-
+> [!TIP]
+> This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
-Codex allows you to [define custom profiles to connect to custom model providers](https://learn.chatgpt.com/docs/config-file/config-advanced) through the Responses API.
+Codex allows you to define custom profiles to connect to custom model providers through the Responses API.
-For example, suppose you [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo`, you can create a custom profile at `~/.codex/microsoft-foundry.config.toml` with:
+For example, suppose you deploy Qwen3.8 27B on Microsoft Foundry in a project named `huggingface-demo`, you can create a custom profile at `~/.codex/microsoft-foundry.config.toml` with:
```toml
model = "qwen--qwen3-8-27b"
@@ -56,7 +55,7 @@ For PowerShell, use:
$env:MICROSOFT_FOUNDRY_API_KEY=""
```
-You can copy the key from [Microsoft Foundry](https://ai.azure.com), or retrieve it with the Azure CLI:
+You can copy the key from Microsoft Foundry, or retrieve it with the Azure CLI:
```bash
az cognitiveservices account keys list \
diff --git a/docs/source/harness/hermes-agent.mdx b/docs/source/harness/hermes-agent.mdx
index 875b2aa..3fca9e5 100644
--- a/docs/source/harness/hermes-agent.mdx
+++ b/docs/source/harness/hermes-agent.mdx
@@ -1,12 +1,12 @@
# Hermes Agent
-[Hermes Agent](https://hermes-agent.nousresearch.com/) is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.
+Hermes Agent is a self-improving AI agent built by Nous Research. It's the only agent with a built-in learning loop, it creates skills from experience, improves them during use, nudges itself to persist knowledge, searches its own past conversations, and builds a deepening model of who you are across sessions.

## Install the harness
-You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
+You can either install the desktop application for macOS from https://hermes-agent.nousresearch.com/ or rather install it programmatically for Linux or macOS as:
```bash
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
@@ -20,15 +20,14 @@ irm https://hermes-agent.nousresearch.com/install.ps1 | iex
## Connect the model
-
- This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
-
+> [!TIP]
+> This guide assumes that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
Once installed, you can connect your OpenAI-compatible models deployed on Microsoft Foundry to it as it supports both Chat Completions API and Responses API (recommended) specifications.
-You need to create or add the following into your Hermes Agent configuration file at `~/.hermes/config.yaml`. More information at [Hermes Agent - Configuring Models](https://hermes-agent.nousresearch.com/docs/user-guide/configuring-models).
+You need to create or add the following into your Hermes Agent configuration file at `~/.hermes/config.yaml`. More information at Hermes Agent - Configuring Models.
-Let's assume that you want to [deploy Qwen3.8 27B on Microsoft Foundry](https://ai.azure.com/nextgen/goto/discover/models/qwen--qwen3.8-27b/version/2/registry/azure-huggingface) in a project named `huggingface-demo` then the `~/.hermes/config.yaml` would look like:
+Let's assume that you want to deploy Qwen3.8 27B on Microsoft Foundry in a project named `huggingface-demo` then the `~/.hermes/config.yaml` would look like:
```yaml
model:
@@ -54,9 +53,8 @@ agent:
qwen--qwen3-8-27b: medium
```
-
- As a reminder, the value for `HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY` is either obtained from [Microsoft Foundry](https://ai.azure.com) or programmatically with the `az` CLI as `az cognitiveservices account keys list --subscription --resource-group --name huggingface-demo -o tsv --query key1`.
-
+> [!TIP]
+> As a reminder, the value for `HERMES_CUSTOM_MICROSOFT_FOUNDRY_API_KEY` is either obtained from Microsoft Foundry or programmatically with the `az` CLI as `az cognitiveservices account keys list --subscription --resource-group --name huggingface-demo -o tsv --query key1`.
Alternatively, from the desktop application you can also open the settings and click on "Providers -> Custom Endpoints" and create the endpoint with the deployed model, then set the following:
diff --git a/docs/source/harness/index.mdx b/docs/source/harness/index.mdx
index dd2b217..ab2a205 100644
--- a/docs/source/harness/index.mdx
+++ b/docs/source/harness/index.mdx
@@ -2,67 +2,66 @@
An agent harness is the application that drives a model: it holds the conversation, exposes tools such as file edits or shell commands, and decides what to send back to the model on every turn. Any harness that speaks the OpenAI Chat Completions API or the Responses API can point at a model deployed on Microsoft Foundry.
-
- These guides assume that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
-
+> [!TIP]
+> These guides assume that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
Pick a harness to connect it to your Foundry deployment:
-
-
- Claude Code
- Coming soon
+
+ Claude Code
+ Coming soon
-
- Pi
- Coming soon
+
+ Pi
+ Coming soon
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index acd2a71..9252409 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -10,7 +10,7 @@ The collection lives in the `azure-huggingface` registry and shows up in the Fou

-Each model is published as a versioned asset in the registry, with one or more deployment templates that pin the serving engine, the context window, and the accelerator it runs on. Browse the collection by family in the [catalog](./catalog/qwen), where every entry links to the latest version of the model on Microsoft Foundry.
+Each model is published as a versioned asset in the registry, with one or more deployment templates that pin the serving engine, the context window, and the accelerator it runs on. Browse the collection by family in the catalog — [Qwen](./catalog/qwen), [DeepSeek AI](./catalog/deepseek-ai), [NVIDIA](./catalog/nvidia), and [Microsoft](./catalog/microsoft) — where every entry links to the latest version of the model on Microsoft Foundry.
## Deploy a model
diff --git a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
index 9ccf596..9e4ad59 100644
--- a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
+++ b/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
@@ -1,6 +1,6 @@
# DeepSeek V4 Flash 0731
-[`deepseek-ai/DeepSeek-V4-Flash-0731`](https://huggingface.co/deepseek-ai/DeepSeek-V4-Flash-0731) is the official DeepSeek V4 Flash release, superseding the preview with stronger coding, tool-use, and agentic capabilities.
+deepseek-ai/DeepSeek-V4-Flash-0731 is the official DeepSeek V4 Flash release, superseding the preview with stronger coding, tool-use, and agentic capabilities.
DeepSeek V4 Flash is a mixture-of-experts model with 284B total parameters and 13B activated per token. It combines DeepSeek's compressed attention architecture with a fused DSpark speculative-decoding module, keeping inference efficient while supporting long-context workloads. The model is released under the MIT license.
@@ -72,9 +72,8 @@ deployment = client.managed_compute_deployments.begin_create_or_update(
print(deployment.properties.provisioning_state)
```
-
- The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
-
+> [!TIP]
+> The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
## Inference
@@ -127,4 +126,4 @@ Use `low` for quick tasks, `high` for most agentic work, and `max` for the harde
Connect the deployment to a compatible harness, such as [Hermes Agent](../harness/hermes-agent). Confirm that the harness supports Chat Completions and the model's reasoning controls.
-For more model and serving details, see the [DeepSeek model card](https://huggingface.co/deepseek-ai/DeepSeek-V4-Flash-0731) and the [vLLM recipe](https://recipes.vllm.ai/deepseek-ai/DeepSeek-V4-Flash).
+For more model and serving details, see the DeepSeek model card and the vLLM recipe.
diff --git a/docs/source/large-language-models/glm-5-2-fp8.mdx b/docs/source/large-language-models/glm-5-2-fp8.mdx
index 9f14a24..6bc8947 100644
--- a/docs/source/large-language-models/glm-5-2-fp8.mdx
+++ b/docs/source/large-language-models/glm-5-2-fp8.mdx
@@ -1,6 +1,6 @@
# GLM 5.2 FP8
-[`zai-org/GLM-5.2-FP8`](https://huggingface.co/zai-org/GLM-5.2-FP8) is an open-weight reasoning model for coding, tool use, and long-running agent tasks.
+zai-org/GLM-5.2-FP8 is an open-weight reasoning model for coding, tool use, and long-running agent tasks.

@@ -61,9 +61,8 @@ deployment = client.managed_compute_deployments.begin_create_or_update(
print(deployment.properties.provisioning_state)
```
-
- The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
-
+> [!TIP]
+> The deployment usually takes 15–20 minutes, but might take up to an hour whilst looking for instances when demand is high.
## Inference
From 218cb1b144d9129706c5021b98ed926fdf950c18 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 19 Aug 2026 14:29:33 +0200
Subject: [PATCH 15/17] Update `_toctree.yml` and `harness/index.mdx`
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 49 ++++++++++++++++++-----------------
docs/source/harness/index.mdx | 2 --
2 files changed, 25 insertions(+), 26 deletions(-)
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index 960b3e9..efab873 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -1,17 +1,16 @@
-- sections:
- - local: index
- title: Overview
+- local: index
title: Overview
-- sections:
- - local: catalog/qwen
- title: Qwen
- - local: catalog/deepseek-ai
- title: DeepSeek AI
- - local: catalog/nvidia
- title: NVIDIA
- - local: catalog/microsoft
- title: Microsoft
+- local: catalog/index
title: Catalog
+ sections:
+ - local: catalog/qwen
+ title: Qwen
+ - local: catalog/deepseek-ai
+ title: DeepSeek AI
+ - local: catalog/nvidia
+ title: NVIDIA
+ - local: catalog/microsoft
+ title: Microsoft
- sections:
- local: get-started/quickstart
title: Quickstart
@@ -22,21 +21,23 @@
- local: large-language-models/deepseek-v4-flash-0731
title: DeepSeek V4 Flash 0731
- local: large-language-models/qwen3-8-27b
- title: Qwen3.8 27B
+ title: Qwen3.8 27B (Coming soon)
title: Large Language Models
-- sections:
- - local: harness/index
- title: Overview
- - local: harness/claude-code
- title: Claude Code (Coming soon)
- - local: harness/codex
- title: Codex
- - local: harness/hermes-agent
- title: Hermes Agent
- - local: harness/pi
- title: Pi (Coming soon)
+- local: harness/index
title: Harness
+ sections:
+ - local: harness/index
+ title: Overview
+ - local: harness/claude-code
+ title: Claude Code (Coming soon)
+ - local: harness/codex
+ title: Codex
+ - local: harness/hermes-agent
+ title: Hermes Agent
+ - local: harness/pi
+ title: Pi (Coming soon)
- sections:
- local: advanced/reasoning
title: Enable and disable reasoning
title: Advanced
+ isExpanded: true
diff --git a/docs/source/harness/index.mdx b/docs/source/harness/index.mdx
index ab2a205..4422709 100644
--- a/docs/source/harness/index.mdx
+++ b/docs/source/harness/index.mdx
@@ -5,8 +5,6 @@ An agent harness is the application that drives a model: it holds the conversati
> [!TIP]
> These guides assume that you already have a model running on Microsoft Foundry. If you do not, follow the [quickstart](../get-started/quickstart) and deploy one from the Foundry portal or with Python first.
-Pick a harness to connect it to your Foundry deployment:
-
+
+## And much more
+
+Those pages cover 50 of the 102 models in the collection. The rest spans many more providers, including:
+
+- **Z.ai** GLM 5.2, and **OpenAI** gpt-oss 20B and 120B, for open frontier-scale chat and reasoning
+- **Google** Gemma 4, **Mistral AI**, **IBM Granite**, and **Cohere Labs** North, for general-purpose chat
+- **OpenAI** Whisper for speech recognition, and **Qwen** and **Tongyi-MAI** models for image generation
+- **Sentence Transformers** all-MiniLM, **Answer.AI** ModernBERT, and **BERT** variants, for embeddings and classification at a fraction of the cost of a chat model
+
+New models land in the collection regularly, so the Foundry catalog is always the complete, current list:
+
+
+
+ Browse the full collection on Microsoft Foundry
+ Filter by Collection: Hugging Face and Deployment options: Managed compute to see all 102
+
+
+
diff --git a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx b/docs/source/examples/deepseek-v4-flash-0731.mdx
similarity index 98%
rename from docs/source/large-language-models/deepseek-v4-flash-0731.mdx
rename to docs/source/examples/deepseek-v4-flash-0731.mdx
index 9e4ad59..34c01e5 100644
--- a/docs/source/large-language-models/deepseek-v4-flash-0731.mdx
+++ b/docs/source/examples/deepseek-v4-flash-0731.mdx
@@ -1,4 +1,4 @@
-# DeepSeek V4 Flash 0731
+# Long-context reasoning and agentic coding with DeepSeek V4 Flash on Foundry
deepseek-ai/DeepSeek-V4-Flash-0731 is the official DeepSeek V4 Flash release, superseding the preview with stronger coding, tool-use, and agentic capabilities.
diff --git a/docs/source/large-language-models/glm-5-2-fp8.mdx b/docs/source/examples/glm-5-2-fp8.mdx
similarity index 98%
rename from docs/source/large-language-models/glm-5-2-fp8.mdx
rename to docs/source/examples/glm-5-2-fp8.mdx
index 6bc8947..a2f6917 100644
--- a/docs/source/large-language-models/glm-5-2-fp8.mdx
+++ b/docs/source/examples/glm-5-2-fp8.mdx
@@ -1,4 +1,4 @@
-# GLM 5.2 FP8
+# Open frontier-scale intelligence with GLM 5.2 and vLLM on Foundry
zai-org/GLM-5.2-FP8 is an open-weight reasoning model for coding, tool use, and long-running agent tasks.
diff --git a/docs/source/examples/qwen3-8-27b.mdx b/docs/source/examples/qwen3-8-27b.mdx
new file mode 100644
index 0000000..18ecea1
--- /dev/null
+++ b/docs/source/examples/qwen3-8-27b.mdx
@@ -0,0 +1,3 @@
+# Multimodal understanding with Qwen3.8 27B on Foundry
+
+Coming soon!
diff --git a/docs/source/get-started/quickstart.mdx b/docs/source/get-started/quickstart.mdx
index 52b0f7f..2237e17 100644
--- a/docs/source/get-started/quickstart.mdx
+++ b/docs/source/get-started/quickstart.mdx
@@ -115,6 +115,6 @@ client.managed_compute_deployments.begin_delete(
## Next steps
-- Browse the catalog to pick a model: [Qwen](../catalog/qwen), [DeepSeek AI](../catalog/deepseek-ai), [NVIDIA](../catalog/nvidia), [Microsoft](../catalog/microsoft).
+- Browse the [catalog](../catalog/index) to pick a model.
- Turn reasoning on or off per request in [Enable and disable reasoning](../advanced/reasoning).
- Connect the deployment to a harness such as [Codex](../harness/codex) or [Hermes Agent](../harness/hermes-agent).
diff --git a/docs/source/harness/index.mdx b/docs/source/harness/index.mdx
index 4422709..da8d1b0 100644
--- a/docs/source/harness/index.mdx
+++ b/docs/source/harness/index.mdx
@@ -8,58 +8,58 @@ An agent harness is the application that drives a model: it holds the conversati
-
- Claude Code
- Coming soon
+
+ Claude Code
+ Coming soon
-
- Pi
- Coming soon
+
+ Pi
+ Coming soon
diff --git a/docs/source/index.mdx b/docs/source/index.mdx
index 9252409..998faf2 100644
--- a/docs/source/index.mdx
+++ b/docs/source/index.mdx
@@ -10,7 +10,7 @@ The collection lives in the `azure-huggingface` registry and shows up in the Fou

-Each model is published as a versioned asset in the registry, with one or more deployment templates that pin the serving engine, the context window, and the accelerator it runs on. Browse the collection by family in the catalog — [Qwen](./catalog/qwen), [DeepSeek AI](./catalog/deepseek-ai), [NVIDIA](./catalog/nvidia), and [Microsoft](./catalog/microsoft) — where every entry links to the latest version of the model on Microsoft Foundry.
+Each model is published as a versioned asset in the registry, with one or more deployment templates that pin the serving engine, the context window, and the accelerator it runs on. Browse it in the [catalog](./catalog/index), where every entry links to the latest version of the model on Microsoft Foundry.
## Deploy a model
diff --git a/docs/source/large-language-models/qwen3-8-27b.mdx b/docs/source/large-language-models/qwen3-8-27b.mdx
deleted file mode 100644
index a6cabf2..0000000
--- a/docs/source/large-language-models/qwen3-8-27b.mdx
+++ /dev/null
@@ -1,3 +0,0 @@
-# Qwen3.8 27B
-
-Coming soon!
From 8148c54a55da34bc6d62066f77204fdeac1d2d96 Mon Sep 17 00:00:00 2001
From: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
Date: Wed, 19 Aug 2026 16:27:49 +0200
Subject: [PATCH 17/17] Update examples and put `get-stated` before catalog
Signed-off-by: Alvaro Bartolome <36760800+alvarobartt@users.noreply.github.com>
---
docs/source/_toctree.yml | 10 ++++----
.../examples/deepseek-v4-flash-0731.mdx | 25 ++++++++++++-------
docs/source/examples/glm-5-2-fp8.mdx | 2 +-
3 files changed, 22 insertions(+), 15 deletions(-)
diff --git a/docs/source/_toctree.yml b/docs/source/_toctree.yml
index d257e84..30251fd 100644
--- a/docs/source/_toctree.yml
+++ b/docs/source/_toctree.yml
@@ -1,6 +1,11 @@
- local: index
title: Overview
+- sections:
+ - local: get-started/quickstart
+ title: Quickstart
+ title: Get started
+
- local: catalog/index
title: Catalog
isExpanded: true
@@ -14,11 +19,6 @@
- local: catalog/microsoft
title: Microsoft
-- sections:
- - local: get-started/quickstart
- title: Quickstart
- title: Get started
-
- sections:
- local: examples/glm-5-2-fp8
title: Open frontier-scale intelligence with GLM 5.2 and vLLM on Foundry
diff --git a/docs/source/examples/deepseek-v4-flash-0731.mdx b/docs/source/examples/deepseek-v4-flash-0731.mdx
index 34c01e5..2d5c749 100644
--- a/docs/source/examples/deepseek-v4-flash-0731.mdx
+++ b/docs/source/examples/deepseek-v4-flash-0731.mdx
@@ -1,17 +1,24 @@
-# Long-context reasoning and agentic coding with DeepSeek V4 Flash on Foundry
+# Long-context reasoning and agentic coding with DeepSeek V4 Flash
deepseek-ai/DeepSeek-V4-Flash-0731 is the official DeepSeek V4 Flash release, superseding the preview with stronger coding, tool-use, and agentic capabilities.
DeepSeek V4 Flash is a mixture-of-experts model with 284B total parameters and 13B activated per token. It combines DeepSeek's compressed attention architecture with a fused DSpark speculative-decoding module, keeping inference efficient while supporting long-context workloads. The model is released under the MIT license.
-DeepSeek reports the following results for the `0731` release:
-
-| Benchmark | Score |
-|---|---:|
-| Terminal Bench 2.1 | 82.7 |
-| DeepSWE | 54.4 |
-| Toolathlon-Verified | 70.3 |
-| Agents' Last Exam | 25.2 |
+
On Microsoft Foundry, it runs with vLLM using:
diff --git a/docs/source/examples/glm-5-2-fp8.mdx b/docs/source/examples/glm-5-2-fp8.mdx
index a2f6917..233bdfb 100644
--- a/docs/source/examples/glm-5-2-fp8.mdx
+++ b/docs/source/examples/glm-5-2-fp8.mdx
@@ -1,4 +1,4 @@
-# Open frontier-scale intelligence with GLM 5.2 and vLLM on Foundry
+# Open frontier-scale intelligence with GLM 5.2
zai-org/GLM-5.2-FP8 is an open-weight reasoning model for coding, tool use, and long-running agent tasks.