What permissions are required to attach the Snapshot debugger to AKS?

Wouter de Kort 21

I'm trying to attach the Snapshot debugger to my .NET 5 app running on AKS. I'm following these instructions: https://learn.microsoft.com/en-us/visualstudio/debugger/debug-live-azure-kubernetes?view=vs-2022 but I keep getting the following error:

Error: Failed to get response from URL: https://management.azure.com//subscriptions/<..>/resourceGroups/devtest-aks/providers/Microsoft.ContainerService/managedClusters/<...>/accessProfiles/clusterUser?api-version=2017-08-31  
Error: Unable to Start Snapshot Debugger - Attach Snapshot Debugger failed: System.Net.WebException: The remote server returned an error: (403) Forbidden.

What permissions do I need to make this work?

kobulloc-MSFT 23,416 Reputation points Microsoft Employee

2022-02-01T19:39:38.6+00:00
Hello, @Wouter de Kort !

There are quite a few AKS permissions to sift through so I reached out to the AKS product group. I'll update you when I know more.

Additionally, this may be specific to the app and not AKS. There are some troubleshooting steps included in the Azure Snapshot Debugging documentation:
https://learn.microsoft.com/en-us/visualstudio/debugger/debug-live-azure-apps-troubleshooting?view=vs-2022#403-forbidden

Verify that your Visual Studio account has a valid Azure subscription with the necessary Role-Based Access Control (RBAC) permissions for the resource. For AppService, check if you have permissions to query the App Service Plan hosting your app.

Verify the timestamp of your client machine is correct and up-to-date. Servers with timestamps off by more than 15 minutes of the request timestamp usually produce this error.

I'd also try the Visual Studio community as they may know more about the Snapshot Debugger:
https://developercommunity.visualstudio.com/spaces/8/index.html
kobulloc-MSFT 23,416 Reputation points Microsoft Employee

2022-02-08T03:17:21.127+00:00

Hello, @Wouter de Kort !

Quick update: I haven't heard back from the AKS product group yet (it's been a very busy month) but it sounds like it may be a good idea to reach out to the Visual Studio community:

https://developercommunity.visualstudio.com/spaces/8/index.html