You’re right, that’s why I worded it as “if your code may be called from a synchronization context”. That said, the overhead is probably negligible (just a struct allocation and a few checks).

In our case, we still have some applications running on the old ASP.NET, so most of our shared libraries must keep using ConfigureAwait.