Debugging Azure App Service - Is it really this bad?

Hey all, I'm pretty new to dotnet development, but I'm helping some co-workers with debugging the api out in Azure App Services.
I'm trying to run my debugger via attached process to my staging Azure App Service that is running the api.
I just figured out how to do it this past weekend.
Claude/Google had to help a lot,

I figured out i had to publish from my machine ( vs run our deploy pipeline ) and set the drop down up near the launch profiles to say debug. I'm also checking Just My Code, and I have some project-level property settings that specify non-optimized code, and debug symbols.

But it's so crazy slow!!

We're trying to debug a webhook endpoint that revives a JSON body, hence why I can't run in locally, because I need to see the actual data coming form the POST request.

Any tips on how to make this process less painful? Is my app service the bottle neck? I can tell my computer isn't doing much work so it's not my end. Thanks for any tips!

TLDR;
Running Visual Studio Debugger ( to inspect data on POST endpoint from outside source i.e. kinda rules out localhost) via attaching to process of the API in Azure is crazy slow and near impossible, need tips to make this better.