Azure-docs: Installing Monitoring Solution

[pho30]

I noticed when running the commands for enabling and installing the monitoring solutions, they do not actually appear in the workspace. When running the above sample script provided, it enables the solutions, the associated saved searches can also be seen in the workspace for the solutions, however, if you look at the resource group it is deployed to, none of these solutions exist. If you look at the workspace -> Solutions, they do not appear either.

If you go to Solutions -> Add -> Add a Solution (in this case I added update management), this can be seen in the resource group and now all the solutions appear under the workspace (all solutions still do not appear in the resource group).

Are there additional commands to run to fully deploy the solutions to the workspace or is this a manual step required to go in and install each one (which would defeat the purpose of doing this via powershell)?

Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: fb75e535-de4f-e730-4dfb-dfc160386f45
• Version Independent ID: 6b355634-913c-65e4-62fa-a51cfeff143a
• Content: Use PowerShell to Create and Configure a Log Analytics Workspace
• Content Source: articles/azure-monitor/platform/powershell-workspace-configuration.md
• Service: log-analytics
• GitHub Login: @richrundmsft
• Microsoft Alias: richrund

[richrundmsft]

@MeirMen and @bwren - can you also follow up on this issue?

[MGoedtel]

@pho30 - I just pulled the logic to add/list solutions and ran a test to see if I could repro your issue and can confirm I am seeing the same behavior. The Activity Log shows that it successfully enabled the solutions in the workspace, but when you validate via portal they don't appear and when you verify via Posh cmdlet Get-AzOperationalInsightsIntelligencePacks to see if they are enabled, it states they are. I tested many times and got inconsistent results where at one point it did actually create them in one of my newly created workspaces for this test, but in 98% of the other tests, it did not. I've escalated this to engineering, but because this isn't a doc issue I am requesting we close this GitHub issue. #please-close. If the follow-up action requires doc changes, I'll track internally. In the meantime, use the ARM template approach to onboard solutions programmatically as I can confirm that method is solid.