Microsoft Agent Framework .NET 1.27.0 adds breaking AgentServer and redirect changes

The release adds a .NET consumer skill for building with Agent Framework and a script to bump the .NET release version. It also updates the Aspire dependency group and includes workflow fixes, including consistent handling of parse-value conversion failures and preservation of pending Magentic plan review.

In Foundry hosted applications, builder.Services.AddFoundryResponses(...) should be replaced with builder.AddFoundryResponses(...) so response and task storage share one configuration-bound identity and endpoint. The changelog also aligns several Azure SDK packages to specific beta and stable versions. Responses beta.9 moves local durable response state to a new location, and existing pre-upgrade local response files are not read after upgrading, with no migration procedure provided.

A second breaking change rejects redirect client changes. DefaultHttpRequestHandler client-provider callbacks must now return null for allowed redirect destinations or throw to reject one, because returning a client for a redirect raises HttpRequestException before the redirected request is sent. Supplying a client for the initial request remains supported.

Projects that pin Azure SDK packages directly will need to realign versions before upgrading to avoid mismatches. Code that returns a client from redirect callbacks will fail before the redirected request is sent and needs updating. Local response state written before the upgrade will not be read afterward, so agents relying on it should plan for that.