Question about proper CancellationToken usage within awaitable methods

[WizardBrony]

public Task Method1Async(CancellationToken token)
{
    if (token.IsCancellationRequested)
        return Task.FromCanceled(token);
    // ...
}

public Task Method2Async(CancellationToken token)
{
    token.ThrowIfCancellationRequested();
    // ...
}

Given the following common usage of awaitable methods:

var method2Task = Method2Async(token);
// ...
try
{
    await method2Task;
}
catch (OperationCanceledException)
{
    // ...
}

or since .NET 8.0:

var method2Task = Method2Async(token);
// ...
await method2Task.ConfigureAwait(ConfigureAwaitOptions.SuppressThrowing);

do the .NET design guidelines consider Method2Async as having a bug? I haven't seen any official statements, so links to relevant documentation would be appreciated.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-threading-tasks
See info in area-owners.md if you want to be subscribed.

[stephentoub]

do the .NET design guidelines consider Method2Async as having a bug?

Yes. All exceptions in Task-returning methods, other than argument validation, should emerge asynchronously via the returned Task rather than being propagated out synchronously.

[WizardBrony]

Yes. All exceptions in Task-returning methods, other than argument validation, should emerge asynchronously via the returned Task rather than being propagated out synchronously.

Thank you very much for confirming.