← All speakers

Bio, Work & Ideas

Julia Kasper

Conference affiliation: Microsoft · 2025

Julia Kasper is a Microsoft product manager working on Visual Studio Code and GitHub Copilot, where she helps shape how coding agents access tools, understand developer context, and interact securely with enterprise systems.

Her earlier work connected conventional software development with low-code platforms. In 2023, she showed developers how to turn ASP.NET Core APIs into Power Apps connectors directly from Visual Studio and co-authored guidance on securing enterprise integrations through API keys, OAuth, and Azure API Management. She subsequently worked on Azure API Center, extending that focus to API discovery and governance.

By 2025, Kasper was applying those foundations to protected remote MCP servers on the Azure API Management team. Microsoft credited her with an Azure Developer CLI template for deploying secured MCP infrastructure. At AI Engineer World’s Fair, she demonstrated how Microsoft Entra ID, OAuth consent, and an API gateway could preserve user identity while making protected tools available inside VS Code and GitHub Copilot.

  • Enterprise identity should govern agent access. Kasper favors established OAuth providers and API gateways over requiring MCP developers to build authorization servers themselves. Her critique of early MCP authorization requirements emphasizes retaining existing consent, permissions, and token-validation controls.
  • Coding-agent quality depends on the harness. In a co-authored analysis of GitHub Copilot’s coding harness, Kasper describes how workspace context, tool execution, and the agent loop determine whether model capability translates into useful work. Her work on VSC-Bench extends that concern to evaluations grounded in actual editing, terminal, and tool-use workflows.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Follow a protected MCP request from its first HTTP challenge through OAuth discovery, C# token validation, Azure deployment, and authenticated tool use in VS Code.

  • Who should be allowed to call your tools?
    0:34 ↗
  • Local binaries have a different authentication boundary
    2:04 ↗
  • Separate the resource server from the token factory
    3:07 ↗
  • Less security code, with clear responsibilities
    4:32 ↗
  • A 401 response starts discovery
    6:59 ↗
  • Protect an ASP.NET Core MCP server
    9:09 ↗
  • Put a gateway in front of the deployed server
    12:51 ↗
  • Authorize Inspector, then VS Code
    15:33 ↗
  • Expose existing REST operations as tools
    17:52 ↗
  • Build against the specification and security guidance
    19:28 ↗

References