<![CDATA[Day 544. When querying #Azure Log Analytics logs over the Azure CLI, if you use the workspace name the CLI will tell you "PathNotFound" which is not really helpful.]]>

<![CDATA[Day 544. When querying #Azure Log Analytics logs over the Azure CLI, if you use the workspace name the CLI will tell you "PathNotFound" which is not really helpful.]]>Day 544. When querying #Azure Log Analytics logs over the Azure CLI, if you use the workspace name the CLI will tell you "PathNotFound" which is not really helpful. You need to use the workspace ID instead of the workspace name, which of course is a totally different thing.

Link Preview Image

Link Preview Image

]]>https://board.circlewithadot.net/topic/49d9b9ca-f4f9-481d-8961-0b491bf2cdd8/day-544.-when-querying-azure-log-analytics-logs-over-the-azure-cli-if-you-use-the-workspace-name-the-cli-will-tell-you-pathnotfound-which-is-not-really-helpful.RSS for NodeMon, 25 May 2026 07:40:08 GMTWed, 29 Apr 2026 08:19:07 GMT60<![CDATA[Reply to Day 544. When querying #Azure Log Analytics logs over the Azure CLI, if you use the workspace name the CLI will tell you "PathNotFound" which is not really helpful. on Wed, 29 Apr 2026 10:29:30 GMT]]>@azureshit
Hey, one that's impacted me!

]]>https://board.circlewithadot.net/post/https://infosec.exchange/users/FritzAdalis/statuses/116487524892980535https://board.circlewithadot.net/post/https://infosec.exchange/users/FritzAdalis/statuses/116487524892980535Wed, 29 Apr 2026 10:29:30 GMT