diff --git a/dotnet/samples/05-end-to-end/HostedAgents/AgentWithHostedMCP/README.md b/dotnet/samples/05-end-to-end/HostedAgents/AgentWithHostedMCP/README.md index 8d8ddba330..106e08e720 100644 --- a/dotnet/samples/05-end-to-end/HostedAgents/AgentWithHostedMCP/README.md +++ b/dotnet/samples/05-end-to-end/HostedAgents/AgentWithHostedMCP/README.md @@ -18,7 +18,7 @@ Before running this sample, ensure you have: 2. A deployment of a chat model (e.g., gpt-4o-mini) 3. Azure CLI installed and authenticated -**Note**: This sample uses Azure CLI credentials for authentication. Make sure you're logged in with `az login` and have access to the Azure OpenAI resource. +**Note**: This sample uses `DefaultAzureCredential` for authentication, which probes multiple sources automatically. For local development, make sure you're logged in with `az login` and have access to the Azure OpenAI resource. ## Environment Variables diff --git a/dotnet/samples/05-end-to-end/HostedAgents/AgentWithTools/README.md b/dotnet/samples/05-end-to-end/HostedAgents/AgentWithTools/README.md index 5a80ecda9f..55333f9940 100644 --- a/dotnet/samples/05-end-to-end/HostedAgents/AgentWithTools/README.md +++ b/dotnet/samples/05-end-to-end/HostedAgents/AgentWithTools/README.md @@ -6,7 +6,7 @@ Key features: - Configuring Foundry tools using `UseFoundryTools` with MCP and code interpreter - Connecting to an external MCP tool via a Foundry project connection -- Using `AzureCliCredential` for Azure authentication +- Using `DefaultAzureCredential` for Azure authentication - OpenTelemetry instrumentation for both the chat client and agent > For common prerequisites and setup instructions, see the [Hosted Agent Samples README](../README.md). @@ -36,7 +36,7 @@ $env:MCP_TOOL_CONNECTION_ID="SampleMCPTool" ## How It Works -1. An `AzureOpenAIClient` is created with `AzureCliCredential` and used to get a chat client +1. An `AzureOpenAIClient` is created with `DefaultAzureCredential` and used to get a chat client 2. The chat client is wrapped with `UseFoundryTools` which registers two Foundry tool types: - **MCP connection**: Connects to an external MCP server (Microsoft Learn) via the project connection name, providing documentation fetch and search capabilities - **Code interpreter**: Allows the agent to execute code snippets when needed diff --git a/dotnet/samples/05-end-to-end/HostedAgents/AgentsInWorkflows/README.md b/dotnet/samples/05-end-to-end/HostedAgents/AgentsInWorkflows/README.md index 72019bbf22..0f2f188f1b 100644 --- a/dotnet/samples/05-end-to-end/HostedAgents/AgentsInWorkflows/README.md +++ b/dotnet/samples/05-end-to-end/HostedAgents/AgentsInWorkflows/README.md @@ -19,7 +19,7 @@ Before you begin, ensure you have the following prerequisites: - Azure OpenAI service endpoint and deployment configured - Azure CLI installed and authenticated (for Azure credential authentication) -**Note**: This demo uses Azure CLI credentials for authentication. Make sure you're logged in with `az login` and have access to the Azure OpenAI resource. For more information, see the [Azure CLI documentation](https://learn.microsoft.com/cli/azure/authenticate-azure-cli-interactively). +**Note**: This demo uses `DefaultAzureCredential` for authentication, which probes multiple sources automatically. For local development, make sure you're logged in with `az login` and have access to the Azure OpenAI resource. For more information, see the [Azure CLI documentation](https://learn.microsoft.com/cli/azure/authenticate-azure-cli-interactively). Set the following environment variables: diff --git a/dotnet/samples/05-end-to-end/HostedAgents/README.md b/dotnet/samples/05-end-to-end/HostedAgents/README.md index f7a3bdc94b..cf90a97005 100644 --- a/dotnet/samples/05-end-to-end/HostedAgents/README.md +++ b/dotnet/samples/05-end-to-end/HostedAgents/README.md @@ -23,7 +23,7 @@ Before running any sample, ensure you have: ### Authenticate with Azure CLI -All samples use `AzureCliCredential` for authentication. Make sure you're logged in: +All samples use `DefaultAzureCredential` for authentication, which automatically probes multiple credential sources (environment variables, managed identity, Azure CLI, etc.). For local development, the simplest approach is to authenticate via Azure CLI: ```powershell az login