← All speakers

Bio, Work & Ideas

Amy Boyd

Conference affiliation: Microsoft · 2026

Amy Boyd leads Microsoft Foundry Developer Relations, helping developers build AI agents whose behavior remains visible, reliable, and safe after deployment. A principal cloud advocate at Microsoft, she combines developer education with practical expertise in agent observability and evaluation.

Boyd studied computer science at the University of Sheffield, focusing on natural language processing and machine learning. A placement working on Microsoft’s Bing search engine preceded experience across data visualization, machine learning, large-scale data, and connected devices; she subsequently advanced into AI advocacy and developer-relations leadership.

Her public projects include AI Nights workshop resources, an Azure Machine Learning fashion demonstration, and a Love Island data-science project. She also coauthored an introductory generative-AI workshop with Carlotta Castelluccio in Microsoft’s workshop library, taught Microsoft Fabric data pipelines, and helped troubleshoot agent deployment and search integration.

What dependable agents require

  • Observability from the beginning: Instrument agents during development and continue monitoring them as models, customer behavior, and requirements change.
  • Workflow-level agent evaluation: Assess whether an agent understood the request, selected appropriate tools, stayed grounded, completed its task, and met quality and safety requirements—not simply whether its final answer looked persuasive.
  • OpenTelemetry-based agent tracing: Capture model interactions, tool calls, and execution steps using shared standards that connect Foundry with Azure Monitor and Application Insights across different frameworks.
  • Fleet-wide agent monitoring: Give developers and administrators centralized visibility across multiple agents and interconnected systems while integrating with existing operational infrastructure.

In her AI Engineer Europe workshop with Nitya Narasimhan, Boyd illustrated these principles through a travel assistant equipped with web search, execution traces, and built-in evaluation. Her focus is practical: help developers understand where an agent’s actual behavior diverges from its intended job, then use that evidence to improve it.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Build a travel agent from a portal prototype to a specialist workflow, then connect traces, evaluations, adversarial tests, and human-guided optimization.

  • The train changes; the platform still has requirements
    1:06 ↗
  • Evaluate, monitor, and optimize
    3:54 ↗
  • Evaluate the decisions inside the workflow
    7:33 ↗
  • Start Contoso Travel with an environment you can reproduce
    14:23 ↗
  • Create the agent, then connect its telemetry
    23:22 ↗
  • Move from a failed evaluation to the responsible step
    31:45 ↗
  • Build the same capabilities in code
    35:39 ↗
  • Optimize cost without losing quality
    48:16 ↗
  • Add the context you will need when debugging
    51:11 ↗
  • Inspect why an evaluation failed
    54:52 ↗
  • Test whether users can get around the guardrails
    58:17 ↗
  • Let a coding agent establish the baseline
    1:04:07 ↗
  • Keep the best version, not the newest version
    1:08:13 ↗
  • Use assistance at the code, project, and log layers
    1:13:35 ↗
  • Keep the loop running as the application changes
    1:16:16 ↗

References