Expose Your Workflow via API Done

dotnet add package Microsoft.Agents.AI.Hosting.AzureFunctions
dotnet add package Microsoft.Agents.AI.OpenAI
dotnet add package Microsoft.Agents.AI.Workflows
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.DurableTask.AzureManaged
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore
dotnet add package OpenAI
dotnet restore

dotnet add package Microsoft.Agents.AI.Hosting.AzureFunctions
dotnet add package Microsoft.Agents.AI.OpenAI
dotnet add package Microsoft.Agents.AI.Workflows
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.DurableTask.AzureManaged
dotnet add package Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore
dotnet add package Azure.AI.OpenAI
dotnet add package Azure.Identity
dotnet restore

using Microsoft.Agents.AI;
using Microsoft.Agents.AI.Hosting.AzureFunctions;
using Microsoft.Agents.AI.Workflows;
using Microsoft.Azure.Functions.Worker.Builder;
using Microsoft.Extensions.AI;
using Microsoft.Extensions.Hosting;
using OpenAI;
using OpenAI.Chat;
using System.ClientModel;
using System.ComponentModel;
using ChatMessage = Microsoft.Extensions.AI.ChatMessage;

// 1. Setup Jordan's Brain
var endpoint = Environment.GetEnvironmentVariable("OPENAI_ENDPOINT") ?? "http://localhost:1234/v1";
var modelName = Environment.GetEnvironmentVariable("OPENAI_MODEL_NAME") ?? "google/gemma-4-e4b";
var chatClient = new OpenAIClient(new ApiKeyCredential("dummy"), new OpenAIClientOptions { Endpoint = new Uri(endpoint) })
    .GetChatClient(modelName);


AIAgent triageAgent = chatClient.AsAIAgent(new ChatClientAgentOptions
{
    Name = "TriageAgent",
    ChatOptions = new()
    {
        Instructions = """
            You are Jordan's on-call assistant. Analyze telemetry and classify incident priority.
            """,
        Tools = [AIFunctionFactory.Create(AssessIncidentPriority, nameof(AssessIncidentPriority))]
    }
});

// 2. Build the Assembly Line (Workflow)
var fetchTelemetry = new FetchTelemetryExecutor();
var triageAdapter = new TriageAdapterExecutor();
var triageSync = new TriageSyncExecutor();
var escalationEngine = new EscalationExecutor();
var triageAgentExecutor = triageAgent.BindAsExecutor(new AIAgentHostOptions { ForwardIncomingMessages = false });

WorkflowBuilder builder = new(fetchTelemetry);
builder.WithName("IncidentTriage");
builder.AddEdge(fetchTelemetry, triageAdapter);
builder.AddEdge(triageAdapter, triageAgentExecutor);
builder.AddEdge(triageAgentExecutor, triageSync);
builder.AddEdge(triageSync, escalationEngine);

var workflow = builder.Build();

// 3. Start the Functions Host
using IHost app = FunctionsApplication
    .CreateBuilder(args)
    .ConfigureFunctionsWebApplication()
    .ConfigureDurableOptions(options =>
    {
        options.Workflows.AddWorkflow(workflow, exposeStatusEndpoint: true);
    })
    .Build();

app.Run();

// --- Logic & Executors ---
[Description("Classifies incident priority from service telemetry.")]
static string AssessIncidentPriority(string serviceName, double errorRatePercent, double latencyMs) => "PRIORITY: P0";

internal sealed class FetchTelemetryExecutor() : Executor<string, string>("FetchTelemetry")
{
    public override ValueTask<string> HandleAsync(string service, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult("[TELEMETRY] Latency: 450ms");
}

[SendsMessage(typeof(ChatMessage))]
internal sealed class TriageAdapterExecutor() : Executor<string>("TriageAdapter")
{
    public override async ValueTask HandleAsync(string message, IWorkflowContext context, CancellationToken ct = default) => await context.SendMessageAsync(new ChatMessage(ChatRole.User, message), ct);
}

internal sealed class TriageSyncExecutor() : Executor<string, string>("TriageSync")
{
    public override ValueTask<string> HandleAsync(string report, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult(report.Trim());
}

internal sealed class EscalationExecutor() : Executor<string, string>("EscalationEngine")
{
    public override ValueTask<string> HandleAsync(string report, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult("ALARM: Paging SRE Team.");
}

using Microsoft.Agents.AI;
using Microsoft.Agents.AI.Hosting.AzureFunctions;
using Microsoft.Azure.Functions.Worker.Builder;
using Microsoft.Extensions.AI;
using Microsoft.Extensions.Hosting;
using Azure.AI.OpenAI;
using Azure.Identity;
using OpenAI.Chat;
using System.ComponentModel;
using ChatMessage = Microsoft.Extensions.AI.ChatMessage;

// 1. Setup Jordan's Brain
var endpoint = Environment.GetEnvironmentVariable("AZURE_OPENAI_ENDPOINT")!;
var deploymentName = Environment.GetEnvironmentVariable("AZURE_OPENAI_DEPLOYMENT_NAME")!;
var chatClient = new AzureOpenAIClient(new Uri(endpoint), new DefaultAzureCredential())
    .GetChatClient(deploymentName);

AIAgent triageAgent = chatClient.AsAIAgent(new ChatClientAgentOptions
{
    Name = "TriageAgent",
    ChatOptions = new()
    {
        Instructions = """
            You are Jordan's on-call assistant. Analyze telemetry and classify incident priority.
            """,
        Tools = [AIFunctionFactory.Create(AssessIncidentPriority, nameof(AssessIncidentPriority))]
    }
});

// 2. Build the Assembly Line (Workflow)
var fetchTelemetry = new FetchTelemetryExecutor();
var triageAdapter = new TriageAdapterExecutor();
var triageSync = new TriageSyncExecutor();
var escalationEngine = new EscalationExecutor();
var triageAgentExecutor = triageAgent.BindAsExecutor(new AIAgentHostOptions { ForwardIncomingMessages = false });

WorkflowBuilder builder = new(fetchTelemetry);
builder.WithName("IncidentTriage");
builder.AddEdge(fetchTelemetry, triageAdapter);
builder.AddEdge(triageAdapter, triageAgentExecutor);
builder.AddEdge(triageAgentExecutor, triageSync);
builder.AddEdge(triageSync, escalationEngine);

var workflow = builder.Build();

// 3. Start the Functions Host
using IHost app = FunctionsApplication
    .CreateBuilder(args)
    .ConfigureFunctionsWebApplication()
    .ConfigureDurableOptions(options =>
    {
        options.Workflows.AddWorkflow(workflow, exposeStatusEndpoint: true);
    })
    .Build();

app.Run();

// --- Logic & Executors ---
[Description("Classifies incident priority from service telemetry.")]
static string AssessIncidentPriority(string serviceName, double errorRatePercent, double latencyMs) => "PRIORITY: P0";

internal sealed class FetchTelemetryExecutor() : Executor<string, string>("FetchTelemetry")
{
    public override ValueTask<string> HandleAsync(string service, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult("[TELEMETRY] Latency: 450ms");
}

[SendsMessage(typeof(ChatMessage))]
internal sealed class TriageAdapterExecutor() : Executor<string>("TriageAdapter")
{
    public override async ValueTask HandleAsync(string message, IWorkflowContext context, CancellationToken ct = default) => await context.SendMessageAsync(new ChatMessage(ChatRole.User, message), ct);
}

internal sealed class TriageSyncExecutor() : Executor<string, string>("TriageSync")
{
    public override ValueTask<string> HandleAsync(string report, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult(report.Trim());
}

internal sealed class EscalationExecutor() : Executor<string, string>("EscalationEngine")
{
    public override ValueTask<string> HandleAsync(string report, IWorkflowContext context, CancellationToken ct = default) => ValueTask.FromResult("ALARM: Paging SRE Team.");
}

“Wait and See”

Force the connection to stay open until the workflow completes. This is the simplest way to test the full pipeline and see the final result immediately.

Invoke-RestMethod -Method Post `
  -Uri "http://localhost:7071/api/workflows/IncidentTriage/run" `
  -Headers @{ 
    "Content-Type" = "text/plain"; 
    "x-ms-wait-for-response" = "true" 
  } `
  -Body "checkout failures in production"

The Goal: Observe the terminal hang for a few seconds as the agent reasons, followed by the direct string response: ALARM: Paging SRE Team.

”Trigger and Poll”

Immediately receive a Run ID and check progress later. This is the recommended pattern for production systems and long-running workflows.

# 1. Trigger the workflow (returns a Run ID)
$run = Invoke-RestMethod -Method Post `
  -Uri "http://localhost:7071/api/workflows/IncidentTriage/run" `
  -Body "checkout failures in production"

$id = $run.runId

# 2. Poll the status endpoint
Invoke-RestMethod -Method Get `
  -Uri "http://localhost:7071/api/workflows/IncidentTriage/status/$id"

The Goal: See the status field move from Running to Completed. The JSON response provides the full audit trail of the orchestration.

Triage Different Payloads

Verify that the agent’s reasoning remains grounded by providing a “Healthy” scenario through the API.

Invoke-RestMethod -Method Post `
  -Uri "http://localhost:7071/api/workflows/IncidentTriage/run" `
  -Headers @{ "x-ms-wait-for-response" = "true" } `
  -Body "The payment service is 100% healthy"

The Goal: Even though you are invoking via HTTP, the underlying Triage Workflow still runs. The agent will analyze your text, see no issues, and return TICKET: Logged for triage.