I stumbled on an issue (https://github.com/HTBox/allReady/issues/1313) at GitHub where they discussed about taking the ConfigureAwait(false) out of the code, cl
ConfigureAwait(false)
ConfigureAwait only has effects on code running in the context of a SynchronizationContext which ASP.NET Core doesn't have (ASP.NET "Legacy" does).
ConfigureAwait
SynchronizationContext
General purpose code should still use it because it might be running with a SynchronizationContext.
ASP.NET Core SynchronizationContext