Unable to find log analytics workspace key

Question

Unable to find log analytics workspace key

Mike 45

The Logic App send data action requires the Log Analytics workspace key. Workspace keys are no longer visible in the Azure portal. I found this information, The “Primary Key” and “Secondary Key” fields were part of the older Log Analytics Agent (MMA) configuration model. With the introduction of the Azure Monitor Agent (AMA), the authentication mechanism has changed: but it doesn't address what to do in this case.

I tried using the Get-AzOperationalInsightWorkspaceSharedKeys command in Cloud Shell, but it failed stating that it couldn't find the Resource Group, even though I used the same Resource Group name that was returned with the command Get-AZOperationalInsightsWorkspace.

Any suggestions?

Mike 45 Reputation points

2025-12-09T20:55:22.5933333+00:00

The AI agent suggested using the command Update-AzOperationalInsightsWOrkspaceSharedKey to regenerate the keys. That command resulted in the following error.

Update-AzOperationalInsightsWorkspaceSharedKey: HTTP Status Code: BadRequest

Error Message: keyType value must equal primarySharedKey or secondarySharedKey. Operation Id: 'a7f24848fe97cf6f3631c1836eb12c49'
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-09T23:08:52.87+00:00

Hi Mike,

Following up to see if you had a chance to check my answer and if it was helpful, If this answers your query, do click Accept Answer and Yes, if you have any further queries do let us know.

2 answers

Your answer

Mike 45 Reputation points

2025-12-09T20:55:22.5933333+00:00

The AI agent suggested using the command Update-AzOperationalInsightsWOrkspaceSharedKey to regenerate the keys. That command resulted in the following error.

Update-AzOperationalInsightsWorkspaceSharedKey: HTTP Status Code: BadRequest

Error Message: keyType value must equal primarySharedKey or secondarySharedKey. Operation Id: 'a7f24848fe97cf6f3631c1836eb12c49'
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-09T23:08:52.87+00:00

Hi Mike,

Following up to see if you had a chance to check my answer and if it was helpful, If this answers your query, do click Accept Answer and Yes, if you have any further queries do let us know.

Answer 1

Pravallika KV 3,565 Microsoft External Staff Moderator

Hi Mike,

Thanks for reaching out to Microsoft Q&A.

I have tested the same in Portal(Azure Bash/Azure Powershell) and got the same error.

As discussed over offline, you need to run below PowerShell command in local Terminal to fetch Log Analytics workspace shared keys:

Get-AzOperationalInsightsWorkspaceSharedKey -ResourceGroupName "ResourceGroup" -Name "Workspace"

Or you can also use below command to fetch Log Analytics workspace keys in azure cli locally:

az monitor log-analytics workspace get-shared-keys --resource-group <ResourceGroup> --workspace-name <loganalyticsname> --query "{primaryKey: primarySharedKey, secondaryKey: secondarySharedKey}"

I tried the same and able to fetch both Primary Key and Secondary Key of log analytics workspace as below:

Hope it helps!

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

User's image

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Mike 45 Reputation points

2025-12-10T12:56:53.8866667+00:00

Thank you, Pravallika KV. I expect that will work. I'm getting a different error that the Resource Group name is not being recognized (Resource group 'xxxx' could not be found, despite the fact that the same Resource Group name is returned by the command 'Get-AzOperationalInsightsWorkspace.'
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-10T17:38:49.6633333+00:00
Hi Mike,

The error Resource group 'xxxx' could not be found usually happens when the context or subscription in your PowerShell session is not the one where the resource group exists, even if Get-AzOperationalInsightsWorkspace returns it.

Check below steps:

Verify the current subscription

Get-AzContext

Make sure the Subscription matches the subscription where the resource group actually exists, if it doesn't, switch to the correct subscription:

Set-AzContext -Subscription "Your-Subscription-Name-or-ID"

Azure resource group names are case-insensitive, but sometimes extra spaces or invisible characters i.e., copy-paste can cause issues. Ensure you are using exactly the same name.

Sometimes there may be a workspace with the same name in another subscription, so specify both resource group and subscription:

Get-AzOperationalInsightsWorkspace -ResourceGroupName "xxxx" -Name "workspace-name"

If using Update-AzOperationalInsightsWorkspaceSharedKey, make sure your PowerShell session is using the same subscription and context as the one returned by Get-AzOperationalInsightsWorkspace.

Example:

Set-AzContext -Subscription "Your-Subscription-ID" Update-AzOperationalInsightsWorkspaceSharedKey -ResourceGroupName "xxxx" -Name "YourWorkspaceName"
Mike 45 Reputation points

2025-12-10T19:20:16.21+00:00

Thank you. I was aware of that and first verified that I was in the correct context.
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-12-10T22:52:06.6166667+00:00

Hi Mike, I have reached out to you over private message, please check and provide requested details.

Answer 2

Mike 45

Running the following commands (provided by Pravallika KV) in local Terminal displayed the shared keys.

install-module -name Az -AllowClobber -Force

Connect-AzAccount

Get-AzOperationalInsightsWorkspaceSharedKey -ResourceGroupName "ResourceGroupName" -Name "WorkspaceName"

Share via

Unable to find log analytics workspace key

2 answers

Your answer