Forum Discussion
Separating Logs for RBAC
Microsoft
While not immidiately of importance, creating a resource group adds alot of flexbilty. For example if you needed a second connector VM.
~ Ofer
Ofer_Shezaf thanks for this, I've decided we should definitely use Resource Groups otherwise I think we are going to end up with a mess to sort out later.
I've created a resource group for this and added the Collector VM to it and granted my test user Log Analytics Reader and Workbook Contributor to the groups.
Now I have what I hope is a really simple issue to resolve. If I use my test user and go to Azure Arc I can see and search logs for that device. However if I go to Monitor with the same account it prompts me to select a scope, but I can't see anything under the subscription. (I would have thought I would see the resource group and the collector VM under that). Am I just missing a permissions somewhere or have I misunderstood how this will all work?
Thanks in advance.
- SoniaCuff
SimonR Do you also have the standard Log Analytics agent installed on the on prem VM, or just Azure Arc for servers?
"This agent does not deliver any other functionality, and it doesn't replace the Azure Log Analytics agent. The Log Analytics agent for Windows and Linux is required when you want to proactively monitor the OS and workloads running on the machine, manage it using Automation runbooks or solutions like Update Management, or use other Azure services like Azure Security Center."
https://docs.microsoft.com/en-us/azure/azure-arc/servers/overview#supported-scenarios
SoniaCuff I have both the LA agent and the Arc agent installed on both a Windows and Linux box. I've created resource groups to control access to the logs for these servers. When I try and select a scope in Monitor the resource groups do not appear in the selection list, although others do. Each resource group currently only contains the server with the LA and ARC agents on and my (possibly incorrect) assumption what that would allow me to create a boundary for access to the logs each VM is forwarding rather than have everything exposed to the user.
- Ofer_Shezaf
SimonR : Reading your post, I think you are doing thing right and I am not sure why you can't find your VM in the scope selector. Might be worth a support ticket. If they don't help, I can try to have you work with the Azure Arc PM team - this is a new technology and maybe there are some corner cases to understand.
Thanks Ofer_Shezaf Have logged a ticket, I think this is more a Log Analytics RBAC issue than Arc but I'll update here with any resolution. Thanks very much for your help.
