Skip to content

Change hostingMode value to 'Default'#562

Closed
joelwebb1991 wants to merge 1163 commits intomicrosoft-foundry:mainfrom
joelwebb1991:patch-1
Closed

Change hostingMode value to 'Default'#562
joelwebb1991 wants to merge 1163 commits intomicrosoft-foundry:mainfrom
joelwebb1991:patch-1

Conversation

@joelwebb1991
Copy link
Copy Markdown


│ Error: Invalid configuration

│ with azapi_resource.ai_search,
│ on main.tf line 130, in resource "azapi_resource" "ai_search": │ 130: resource "azapi_resource" "ai_search" {

│ embedded schema validation failed: the argument "body" is invalid: │ properties.hostingMode's value default is invalid. The supported values are [Default, HighDensity]. Do you mean │ Default?
│ You can try to update azapi provider to the latest version or disable the validation using the feature flag schema_validation_enabled = false within the resource block ╵

sdgilley and others added 30 commits May 19, 2025 13:06
Add CODEOWNERS for files used in docs
Update to me (for now), team not available here yet.
…r/fix-role-assignment

Fixed Workspace GUID and References
…-1rp

Adapting Semantic Kernel agents to use Foundry project endpoint
Tweaked readme and comments in config files
…ve-update

update voice live agent sample for FDP projects
…amples

Update C# samples to use latest SDK
xue-cai and others added 28 commits January 23, 2026 14:14
* fix: web-search-agent local development setup

- Fix AzureAIAgentClient parameter names (project_endpoint, credential)
- Update README with local development instructions

* fix: add load_dotenv and clarify .env is for local dev only

* fix: revise README to match standard template

* fix: address PR review comments from melionel

---------

Co-authored-by: Xue Cai <xuecai@microsoft.com>
* [Hosted Agents] fix the dependency version

* misc: bump version
* Automatic fixes

* Mengla/add af foundry tools sample (microsoft-foundry#1)

* Bump hosted agents version to 1.0.0b8

* remove agent_framework dependency in requrements.txt

* add a sample for agentframework with foundry tool

* align naming convention

---------

Co-authored-by: junanchen <junanchen@microsoft.com>

* use latest from_agent_framework signature (microsoft-foundry#2)

* use latest from_agent_framework signature

* remove keyword

* lg tools (microsoft-foundry#3)

* add lg tools sample, bump agentserver version to 1.0.0b9

* rename FoundryToolsReactAgent

* add desc FoundryToolsReactAgent

* remove unused file

---------

Co-authored-by: foundry-samples automation <foundry-samples@noreply.github.com>
Co-authored-by: junanchen <junanchen@microsoft.com>
Co-authored-by: Jun'an Chen <cja.china@gmail.com>
…undry#491)

* Automatic fixes

* Mengla/add af foundry tools sample (microsoft-foundry#1)

* Bump hosted agents version to 1.0.0b8

* remove agent_framework dependency in requrements.txt

* add a sample for agentframework with foundry tool

* align naming convention

---------

Co-authored-by: junanchen <junanchen@microsoft.com>

* use latest from_agent_framework signature (microsoft-foundry#2)

* use latest from_agent_framework signature

* remove keyword

* lg tools (microsoft-foundry#3)

* add lg tools sample, bump agentserver version to 1.0.0b9

* rename FoundryToolsReactAgent

* add desc FoundryToolsReactAgent

* remove unused file

* restore the correct readme

---------

Co-authored-by: foundry-samples automation <foundry-samples@noreply.github.com>
Co-authored-by: junanchen <junanchen@microsoft.com>
Co-authored-by: Jun'an Chen <cja.china@gmail.com>
… version pinning. Change to use Acr image build, to not require local docker. (microsoft-foundry#494)
…osoft-foundry#496)

* Initial plan

* Update FoundryA365 README to clarify agent blueprint approval workflow

Co-authored-by: fosteramanda <29870948+fosteramanda@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: fosteramanda <29870948+fosteramanda@users.noreply.github.com>
…tandard-agent-setup (microsoft-foundry#503)

- Added dnsZonesSubscriptionId parameter to allow DNS zones from different subscriptions
- Updated all DNS zone references in private-endpoint-and-dns.bicep to support cross-subscription scope
- Added comprehensive documentation in README.md about cross-subscription requirements
- Updated main.bicepparam with clear usage examples and warnings
- Maintains backward compatibility (empty parameter uses current subscription)

This enables users to reference existing private DNS zones located in a different Azure subscription than the deployment subscription, which is useful in enterprise environments with centralized DNS management.
* update agent usage detail

* add use agent in response

---------

Co-authored-by: bobogogo1990 <bobobupt2014@163.com>
* Automatic fixes

* Mengla/add af foundry tools sample (microsoft-foundry#1)

* Bump hosted agents version to 1.0.0b8

* remove agent_framework dependency in requrements.txt

* add a sample for agentframework with foundry tool

* align naming convention

---------

Co-authored-by: junanchen <junanchen@microsoft.com>

* use latest from_agent_framework signature (microsoft-foundry#2)

* use latest from_agent_framework signature

* remove keyword

* lg tools (microsoft-foundry#3)

* add lg tools sample, bump agentserver version to 1.0.0b9

* rename FoundryToolsReactAgent

* add desc FoundryToolsReactAgent

* LG HITL example

* remove unused file

* validated HITL

* af ai-function based HITL

* af workflow hitl

* workflow hitl

* restore the correct readme

* add workflow for python sample test

* modify triggering condition

* fix requirements.txt

* add missing env

* fix workflow

* fix type checking issue

* Fix workflow hitl issue

* fix requirements.txt

* fix sample

* fix sample

* chore:  Add C# hosted agent testing to CI/CD pipeline

* minor fix for samples

* Automatic fixes

* fix: SystemUtilityAgent sample

* chore: improve C# build error reporting in CI workflow

* test: ci error details

* Revert "test: ci error details"

This reverts commit e48fe24.

* misc: increate error message limit

* Reapply "test: ci error details"

This reverts commit 7c6e1ed.

* Revert "Reapply "test: ci error details""

This reverts commit d416fd5.

* bump to 1.0.0b10 (microsoft-foundry#8)

* exclude CI related changes

* sync latest manually

---------

Co-authored-by: foundry-samples automation <foundry-samples@noreply.github.com>
Co-authored-by: junanchen <junanchen@microsoft.com>
Co-authored-by: Jun'an Chen <cja.china@gmail.com>
Co-authored-by: Declan <478528180@qq.com>
Co-authored-by: lixiaoli <lixiaoli@microsoft.com>
…oundry#500)

* Fixes requirements.txt

* Fixes evaluation implementation

* Corrected C# Evaluations implementation

* Correct lost section tags
* Add RFT sample for score_model grader, delete the old incorrect sample

* Add RFT samples for python grader

* Add RFT sample for string_check grader

* Add RFT sample for text similarity grader

* Add RFT sample for multi grader

* Update README

* Fix for reasoning model doesn't support temperature

* Remove multi-grader sample as the support is not there in CLI yet

* Refatoring, update datasets, and fix errors

* Update medmcq dataset to match the file formats - reference_answer was missing
Merging on behalf of hosted agent PM + eng reviewers
* Sample for local tool calls in agent

* Remove image since it is not relevant.
…ies when calling tools (microsoft-foundry#514)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls
…oyment. Include sample launch.json if using VS Code (microsoft-foundry#516)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls

* -Align PROJECT_ENDPOINT and MODEL_DEPLOYMENT_NAME with azd conventions for agents
and add VS Code launch.json for easier local debugging
Removed the questions.jsonl file from CODEOWNERS and updated the CLI fine-tuning ownership.
… substitution (microsoft-foundry#518)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls

* -Align PROJECT_ENDPOINT and MODEL_DEPLOYMENT_NAME with azd conventions for agents
and add VS Code launch.json for easier local debugging

* Updating model to use chat reference from resources
…y#519)

- Move C# samples into AgentFramework/ subfolder
- Update .gitignore

Note: python/hosted-agents/agent-framework/agent-with-local-tools/ and python/hosted-agents/code-interpreter-custom/ unchanged (foundry-samples is source of truth)
…ry#520)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls

* -Align PROJECT_ENDPOINT and MODEL_DEPLOYMENT_NAME with azd conventions for agents
and add VS Code launch.json for easier local debugging

* Updating model to use chat reference from resources

* Adding AgentWithLocalTools csharp sample

* Updating default model

* Moving to AgentFramework folder
…required. (microsoft-foundry#524)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls

* -Align PROJECT_ENDPOINT and MODEL_DEPLOYMENT_NAME with azd conventions for agents
and add VS Code launch.json for easier local debugging

* Updating model to use chat reference from resources

* Adding AgentWithLocalTools csharp sample

* Updating default model

* Moving to AgentFramework folder

* Remove credential for agent framework as it is not required.
…foundry#525)

* Update Python enterprise agent tutorial to v2 SDK

Migrate from azure-ai-agents (v1) to azure-ai-projects 2.0.0b3 (v2):

main.py:
- Replace AgentsClient with AIProjectClient + openai_client
- Replace create_agent() with agents.create_version() + PromptAgentDefinition
- Replace SharepointTool with SharepointPreviewTool + SharepointGroundingToolParameters
- Replace McpTool with MCPTool (require_approval='always')
- Replace thread/message/run pattern with Responses API
- Replace RunHandler/ToolApproval with McpApprovalResponse
- Use context manager pattern for client lifecycle

evaluate.py:
- Standardize env vars: AZURE_AI_PROJECT_ENDPOINT -> PROJECT_ENDPOINT
- Standardize env vars: AZURE_AI_MODEL_DEPLOYMENT_NAME -> MODEL_DEPLOYMENT_NAME
- Update usage comment to reference azure-ai-projects==2.0.0b3

requirements.txt:
- Remove azure-ai-agents==1.2.0b6
- Update azure-ai-projects from 1.0.0 to 2.0.0b3
- Add openai dependency

* Address review: output name/version, rename chat_with_assistant to create_agent_response

* Use context managers for credential, project client, and openai client

* chore: migrate C# ModernWorkplaceAssistant to v2 SDK (Azure.AI.Projects + Responses API)

- Replace PersistentAgentsClient with AIProjectClient + PromptAgentDefinition
- Replace threads/runs with Responses API (ProjectResponsesClient)
- Replace SharepointToolDefinition with SharepointPreviewTool + SharePointGroundingToolOptions
- Replace MCPToolDefinition with McpTool from OpenAI.Responses
- Replace SubmitToolApprovalAction with McpToolCallApprovalRequestItem pattern
- Update csproj: Azure.AI.Projects 2.0.0-beta.1 + Azure.AI.Projects.OpenAI 1.0.0-beta.5
- Remove Azure.AI.Agents.Persistent dependency
- Preserve all snippet ID tags for doc system

* fix: use correct v2 SDK type names and package versions for C# sample

- SharepointPreviewTool -> SharepointAgentTool (actual type in Azure.AI.Projects.OpenAI)
- GetProjectOpenAIClient() -> .OpenAI property accessor
- Azure.AI.Projects 2.0.0-beta.1 -> 1.2.0-beta.5 (available on azure-sdk-dev feed)
- Azure.Identity 1.13.1 -> 1.17.1 (required by Azure.AI.Projects 1.2.0-beta.5)
- Add NoWarn OPENAI001 to csproj (preview API suppression)
- GetConnectionAsync now includes required includeCredentials parameter
- Build verified: dotnet build succeeds with azure-sdk-dev feed packages

---------

Co-authored-by: Jon Burchel <jonburchel@microsoft.com>
…t-foundry#526)

* Sample for local tool calls in agent

* Remove image since it is not relevant.

* Updating sample to use hotels instead of date and time for local tool calls

* -Align PROJECT_ENDPOINT and MODEL_DEPLOYMENT_NAME with azd conventions for agents
and add VS Code launch.json for easier local debugging

* Updating model to use chat reference from resources

* Adding AgentWithLocalTools csharp sample

* Updating default model

* Moving to AgentFramework folder

* Remove credential for agent framework as it is not required.

* Pin azure-ai-agentserver-agentframework to 1.0.0b10
Co-authored-by: foundry-samples-repo-sync[bot] <foundry-samples-repo-sync[bot]@users.noreply.github.com>
* CMK private standard agent setup

* Update README with features of private network setup

Expanded features section to include details about the encryption configuration and its relation to other templates.

* Updated API version to 2025-09-01

---------

Co-authored-by: Ibrahim Abedalghafer <ibabedal@outlook.com>
Co-authored-by: foundry-samples-repo-sync[bot] <foundry-samples-repo-sync[bot]@users.noreply.github.com>
…#450)

* changed bicep params and added testing guide

* updated testing guide

* removed sub id from test guide

* MCP server deployed as ACA and not as ACI

* added mcp subnet

* fixes in main.bicep and network-agent-vnet.bicep

* updated testing guide to account for the MCP server container app

* Revert template 15 to upstream and add template 19 (hybrid private resources)

- Reverted 15-private-network-standard-agent-setup to match upstream/main exactly
- Added 19-hybrid-private-resources-agent-setup: hybrid architecture with public
  AI Services endpoint and private backend resources (AI Search, Cosmos DB, Storage)
- Template 19 enables portal-based agent testing while keeping data resources private
- Includes TESTING-GUIDE.md, test scripts, and architecture diagrams in template 19

* Update template 19 testing guide and add MCP HTTP server

Updates based on actual testing:
- Fixed SDK usage: use AzureAISearchTool class, not dict format
- Added note about portal limitation with network injection
- Added correct API version (2025-05-15-preview) for REST API
- Added MCP HTTP server implementation (Streamable HTTP transport)
- Updated MCP deployment instructions with proper HTTP-based server
- Added connection name lookup command
- Fixed test script to use AzureAISearchTool class

MCP Server:
- Added mcp-http-server/server.py - Flask-based MCP server
- Added mcp-http-server/Dockerfile for containerization
- Implements JSON-RPC over HTTP as required by Azure AI Agents

* updated mcp server and tests

* added PNA disabled for Foundry in bicep + test cleanup

* Automatic fixes

---------

Co-authored-by: Meera Kurup <meerakurup@microsoft.com>
Co-authored-by: foundry-samples automation <foundry-samples@noreply.github.com>
…crosoft-foundry#560)

When deploying AI projects with connections (CosmosDB, Azure Storage, AI Search),
the deployment was failing with a 409 Conflict error because all 3 connection
resources were being created in parallel by default, and the backend service
doesn't support concurrent connection creation on the same project.

This change serializes the connection creation so they deploy one after another:
1. CosmosDB connection deploys first (no dependencies)
2. Azure Storage connection waits for CosmosDB connection to complete
3. AI Search connection waits for Azure Storage connection to complete

Changes:
- ai-project-identity.bicep: Added dependsOn chains between connection resources
- azuredeploy.json: Added corresponding dependencies in ARM template

Co-authored-by: jiyan2 <jiyan@microsoft.com>
╷  
│ Error: Invalid configuration  
│  
│ with azapi_resource.ai_search,  
│ on main.tf line 130, in resource "azapi_resource" "ai_search":  
│ 130: resource "azapi_resource" "ai_search" {  
│  
│ embedded schema validation failed: the argument "body" is invalid:  
│ `properties.hostingMode`'s value `default` is invalid. The supported values are [Default, HighDensity]. Do you mean  
│ `Default`?  
│ You can try to update `azapi` provider to the latest version or disable the validation using the feature flag `schema_validation_enabled = false` within the resource block  
╵
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.