Hi Michael & thanks for dropping this question, its a super important one when u wanna keep ur aks clusters safe, really...
So....., u gotta focus on these key permissions to make backup and restore work smoothly in aks. first, ur custom role needs 'microsoft.kubernetes/connectedclusters/read' and 'microsoft.kubernetes/connectedclusters/write' – that’s the bread and butter for accessing and modifying cluster stuff. also, don’t forget 'microsoft.resources/subscriptions/resourcegroups/read' so u can see where everything lives. https://learn.microsoft.com/en-us/azure/backup/azure-kubernetes-service-cluster-backup-concept and 'microsoft.backup/backupvaults/backup/action' is a must-have for actually triggering backups.
now, for the general stuff that’s handy no matter what platform u’re on )) check if ur role has just enough permissions to do the job, no more, no less. this ‘least privilege’ thing is golden for security. also, peek at ur audit logs regularly to spot any weirdness. this might help in other tools too, not just azure.
if u’re juggling multiple clusters, double check the scope of ur permissions. u don’t wanna accidentally give access to stuff that’s off limits. worth looking into how ur backup tool handles scopes, even if u switch platforms later.
hope this clears things up,
rgds,
Alex