Help with installing Azure monitor client on Windows 10 devices

Question

Help with installing Azure monitor client on Windows 10 devices

Robert D. Crane 46 MVP

I have followed the documentation on install the client on Windows devices here:

https://learn.microsoft.com/EN-us/azure/azure-monitor/agents/azure-monitor-agent-windows-client

all goes well until I have to run the PowerShell onboarding script:

https://learn.microsoft.com/EN-us/azure/azure-monitor/agents/azure-monitor-agent-windows-client#using-powershell-for-onboarding

I have updated my PowerShell modules. I'm running as a Global admin on device. I get errors like:

Anyone have any troubleshooting tips for getting this working?

3 answers

Your answer

Answer 1

Sedat SALMAN 14,280 MVP Volunteer Moderator

can you check the available modules for you

Get-Module -ListAvailable -Name Az.Accounts

and also the version

Get-Module -ListAvailable -Name Az.Accounts

Get-AzAccessToken is available in Az.Accounts module version 2.2.0 or later

if it is old please update your module

Update-Module -Name Az.Accounts

also try to import module manually

Import-Module Az.Accounts

Robert D. Crane 46 Reputation points MVP

2023-08-01T07:09:29.01+00:00

See below. Sorry created a new answer thread.

Answer 2

Robert D. Crane 46 MVP

User's image

Robert D. Crane 46 Reputation points MVP

2023-08-01T06:55:52.6066667+00:00

If I import-module az.accounts first and then run script I get:
Robert D. Crane 46 Reputation points MVP

2023-08-01T07:03:54.44+00:00

Deleted the modules from user profile. Re ran PS environment. Did import-module az.accounts. Ran script again as admin and got:

Answer 3

AnuragSingh-MSFT 21,566 Moderator

@Robert D. Crane , Apologies for the inconvenience.

Based on the question and discussion so far, it seems that there are multiple potential issues:

Conflict caused due to version of Az.* powershell modules installed.
The $PATH environment variable not getting resolved correctly.

Also, from the screenshot, I can see that there are multiple versions installed on this machine.

I would suggest doing an uninstall of the Az.* module using the steps mentioned in the link here - Uninstall Azure PowerShell Module

This will serve mainly 2 purposes - remove conflicting modules (if any) and set the environment correctly for the module to be loaded and used.

Hope this helps. Please let us know if you have any questions.

Robert D. Crane 46 Reputation points MVP

2023-08-08T04:30:40.6966667+00:00

The duplicate modules have been resolved. The PS script for Azure monitor still doesn't run as before
Robert D. Crane 46 Reputation points MVP

2023-08-08T04:31:45.4333333+00:00

Same result:
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-08T05:37:51.3266667+00:00

Robert D. Crane, thank you for the reply. Based on the error for New-AzRoleAssignment the role assignment is already in place, therefore this cmdlet need not be run again:

The error points to the following section:

Based on the error reported ("code":"InvalidResource", "message":"Data Collection rule index not found"), it seems that the DCR name is incorrect.

Note the following section in doc:

Note that the "Data collection rule", specified in the script is named "dcr-WindowsClientOS" - ensure that it is already created in the portal and follows the requirement as mentioned above. If your DCR name is something else in the portal, update the variable $DCRName accordingly.

Hope this helps.
Robert D. Crane 46 Reputation points MVP

2023-08-08T05:45:00.5466667+00:00

I have Sentinel with a Log Analytics workspace into which I want the Azure Monitor logs to go. Seems that you can't do that directly? Is this correct??

I created an Azure Monitor workspace and still have same issue as above in that it isn't seen in the drop down??
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-08T05:57:04.1466667+00:00

Robert D. Crane, That should not prevent the workspace from being selected as the destination of DCR. I think you are not creating the DCR in the same location. Change the location of DCR being created to match the LA workspace location.
Robert D. Crane 46 Reputation points MVP

2023-08-08T06:05:22.6866667+00:00

Problem is I can't create an Azure Monitor workspace in Australia East, only Australia South east! The Sentinel LA is in Australia East. Does this mean I have to redo everything and lose all my data?
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-08T06:15:21.3833333+00:00

Robert D. Crane - I am sorry I could not understand the scenario in your last reply.

What I meant with location was that you should create the "Data collection rule" in the same location where your "Log Analytics workspace" is. If the LA workspace is in Australia East, when creating the DCR, select the DCR location also as "Australia East".

Note that "Azure Monitor Workspace" and "LA workspace" are 2 different things. Log Analytics workspaces contain logs and metrics data from multiple Azure resources, whereas Azure Monitor workspaces currently contain only metrics related to Prometheus. For more details, see Azure Monitor workspace

Hope this helps.
Robert D. Crane 46 Reputation points MVP

2023-08-08T06:24:20.75+00:00

Ok. However, now the Azure Monitor Workspace I created to try and get the rule working can't be deleted. I get an error:

azmonsen: The client '******@ciaopsxxx.onmicrosoft.com' with object id '09dabc45-a14b-47a4-a3fd-5f2f7f1dfd2f' has permission to perform action 'Microsoft.Insights/dataCollectionRules/delete' on scope '/subscriptions/c0c148c6-2ed9-4391-9bb8-5bad22c36c9f/resourcegroups/MA_azmonsen_australiasoutheast_managed/providers/Microsoft.Insights/dataCollectionRules/azmonsen'; however, the access is denied because of the deny assignment with name 'Azure Monitor Workspace Managed Resource Group Deny-f2a5b927-3d7f-4adb-86a6-db1f220c717e' and Id 'f2a5b9273d7f4adb86a6db1f220c717e' at scope '/subscriptions/c0c148c6-2ed9-4391-9bb8-5bad22c36c9f/resourceGroups/MA_azmonsen_australiasoutheast_managed'. (Code: DenyAssignmentAuthorizationFailed)

how do I clean this up?
Robert D. Crane 46 Reputation points MVP

2023-08-08T06:38:59.51+00:00

Ok. Rule created

PS script run again. errors again
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-08T09:41:25.5566667+00:00
Robert D. Crane, regarding the failure to delete the Azure Monitor Workspace, this is happening because this workspace is being managed by another resource/resource group. This generally happens when one resource is created as part of another resource creation. In the posted error, it seems that the resource group "MA_azmonsen_australiasoutheast_managed" was created as part of "Azure Monitor Workspace" creation. You can verify that by

Go to the "Azure Monitor Workspace" instance

Select "Properties" in the resource menu

Look for "Default ingestion settings". This will contain resource Id of the DCR and DCE. This Id would be of the following pattern:

............./resourceGroups/MA_azmon-workspace_eastus_managed/...

In this case, the "MA_azmon-workspace_eastus_managed" is the new resource group created as part of "Azure Monitor Workspace Creation", and it is called as 'managed resource group' as it is managed by another resource. To delete anything from that resource group, the Azure Monitor Workspace itself needs to be deleted.

If you have data flowing into this workspace, you can leave the managed resource group and DCRs as is. As mentioned in my reply earlier, if you are not using Prometheus (which requires "Azure Monitor Workspace") and do not have data in this workspace, you can safely delete the workspace which will also delete the managed resource group as well as DCRs that needs to be deleted.

Regarding the new error obtained when running the script, I see that the failure is happening with New-AzRoleAssignment cmdlet which was not happening earlier. I would suggest using Get-AzContext and Remove-AzContext in the PowerShell window to login again to ensure that a fresh session is used.

Hope this helps.
Robert D. Crane 46 Reputation points MVP

2023-08-08T09:56:20.07+00:00

Thanks, I managed to clear the Azure Monitor deletion issue.

I'll try your suggestion with the script and let you know how it goes, probably within 24 hours.
Robert D. Crane 46 Reputation points MVP

2023-08-09T04:57:00.4533333+00:00

Same issue, even after clear-azcontext
Robert D. Crane 46 Reputation points MVP

2023-08-09T04:58:00.08+00:00

Same issue, even after az-clearcontext
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-09T07:08:42.9466667+00:00

Robert D. Crane, As the error suggests, the account being used to login does not have permission to perform this operation:

can you please try using an account which has subscription admin/co-administrator access.

If you are still facing this issue with an admin account, due to the nature of this issue, I would suggest opening a **support ticket **so that it can be investigated 1:1 by one of our support engineers and backend logs can be checked if required.

If you are facing issue opening a support ticket, please let me know.
Robert D. Crane 46 Reputation points MVP

2023-08-09T07:10:24.27+00:00

I am using a Global Administrator and the account that set everything up.
Robert D. Crane 46 Reputation points MVP

2023-08-09T07:13:31.5733333+00:00

The two tenants I have the same issue with have no included Azure support so I can't open a ticket. That's why I'm here.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Robert D. Crane 46 Reputation points MVP

2023-08-11T23:34:51.41+00:00

Done. Thanks.
AnuragSingh-MSFT 21,566 Reputation points Moderator

2023-08-14T04:40:07.2166667+00:00

Robert D. Crane, thank you for sharing the details. I have replied to your email.

Share via

Help with installing Azure monitor client on Windows 10 devices

3 answers

Your answer