Azure Arc Configuration - The given key was not present in the dictonary (GUI only)

Question

Azure Arc Configuration - The given key was not present in the dictonary (GUI only)

Andreas Hartig 121

Hello Community,

I am trying to join Windows Server 2022 and Windows Server 2025 using the new Azure Arc Configuration GUI.

Using the Azure Arc Configuration GUI always and on both systems gives me "the given key was not present in the dictionary when after choosing the Resource Group and the GUI trying to populate the Azure Region.

Doing the same thing running this script with the same user and settings works perfectly: azcmagent connect --subscription-id "xxxxxxxxxxxxxxx" --resource-group "weu-rg-azurearc" --location "westeurope"
User's image

I already went down the path to try it with the supported Windows Server OS and even re-created an Azure Tenant & Subscriptions and multiple Resource Groups. The result in all scenarios on all Windows Servers using the GUI was the same.

Anyone has an idea on what to try next?

Thanks,
Andreas

Tiemen Jansen 0 Reputation points

2024-05-01T19:32:22.9233333+00:00

Having the same problem
Maxime Rastello 1 Reputation point

2024-05-02T11:09:40.51+00:00

Same here for several weeks now
Mads Moi-Aune 5 Reputation points

2024-05-03T08:54:15.9833333+00:00

I'm having the same problem. Using the Azure Arc Configuration GUI does not work, but the commandline works perfectly.
AJ Copeland 10 Reputation points

2024-05-03T12:05:11.3433333+00:00

Can Confirm, using the CMD worked as expected (configured within Azure portal, Azure Arc --> Azure Arc Resources --> Machines --> 'Add/Create' --> generate script). Re-ran the GUI and received a message stating it was already configured.
David Broggy 6,801 Reputation points MVP

2024-10-01T01:07:45.1733333+00:00

still broken. gets stuck at Azure Region with a spinny thing.
Andreas Hartig 15 Reputation points MVP

2024-10-01T08:13:21.61+00:00

Hi David,

can you provide some more information?
What OS version and what Azure Arc Agent version have you tried? Your error seems not to be related to the one we originally experienced and discussed here.

Have you tried the workaround using the command line as described here: https://hartiga.de/azure/windows-server-2025-part-3-azure-arc/

azcmagent connect --subscription-id "your Azure subscription ID" --resource-group "your Azure resource group" --location "the Azure location"

Also recommend watching the video by Sarah Lean: https://youtu.be/P-eU9laNA7g
Daniel Casota 91 Reputation points

2024-10-01T12:11:27.05+00:00

+1 gets stuck at Azure Region --> "The given key was not present in the dictionary."

Insider Build Windows Server 2025 Datacenter Version 10.0.26040.1000

Using the cmdline gets stuck at 30% as well.
Andreas Hartig 15 Reputation points MVP

2024-10-01T18:01:00.7433333+00:00

10.0.26040.1000 would point to be released back in January. Have you downloaded a current ISO and fully patched it including an update of the Azure Arc Agent to Version 1.46?

Version 26040 should have expired and give you a warning: https://betawiki.net/wiki/Windows_Server_2025_build_26040

If you run the azcmagent command with --verbose we might get additional information.

3 answers

Your answer

Tiemen Jansen 0 Reputation points

2024-05-01T19:32:22.9233333+00:00

Having the same problem
Maxime Rastello 1 Reputation point

2024-05-02T11:09:40.51+00:00

Same here for several weeks now
Mads Moi-Aune 5 Reputation points

2024-05-03T08:54:15.9833333+00:00

I'm having the same problem. Using the Azure Arc Configuration GUI does not work, but the commandline works perfectly.
AJ Copeland 10 Reputation points

2024-05-03T12:05:11.3433333+00:00

Can Confirm, using the CMD worked as expected (configured within Azure portal, Azure Arc --> Azure Arc Resources --> Machines --> 'Add/Create' --> generate script). Re-ran the GUI and received a message stating it was already configured.
David Broggy 6,801 Reputation points MVP

2024-10-01T01:07:45.1733333+00:00

still broken. gets stuck at Azure Region with a spinny thing.
Andreas Hartig 15 Reputation points MVP

2024-10-01T08:13:21.61+00:00

Hi David,

can you provide some more information?
What OS version and what Azure Arc Agent version have you tried? Your error seems not to be related to the one we originally experienced and discussed here.

Have you tried the workaround using the command line as described here: https://hartiga.de/azure/windows-server-2025-part-3-azure-arc/

azcmagent connect --subscription-id "your Azure subscription ID" --resource-group "your Azure resource group" --location "the Azure location"

Also recommend watching the video by Sarah Lean: https://youtu.be/P-eU9laNA7g
Daniel Casota 91 Reputation points

2024-10-01T12:11:27.05+00:00

+1 gets stuck at Azure Region --> "The given key was not present in the dictionary."

Insider Build Windows Server 2025 Datacenter Version 10.0.26040.1000

Using the cmdline gets stuck at 30% as well.
Andreas Hartig 15 Reputation points MVP

2024-10-01T18:01:00.7433333+00:00

10.0.26040.1000 would point to be released back in January. Have you downloaded a current ISO and fully patched it including an update of the Azure Arc Agent to Version 1.46?

Version 26040 should have expired and give you a warning: https://betawiki.net/wiki/Windows_Server_2025_build_26040

If you run the azcmagent command with --verbose we might get additional information.

Answer 1

Andreas Hartig 15 MVP

Official statement from the Support Team: „….the issue you are experiencing is a global issue impacting all Windows Server clients and unfortunately we can't provide a fix at this time.

We are expecting the bug fix to be realized with the next version 1.41. that is scheduled for May.

Kindly be informed that the time provided is an estimate and might take more time than expected.“

Alex Gerulaitis 10 Reputation points

2024-06-19T18:44:30.54+00:00

Azure CMA v.1.42 with the "installed" timestamp of today (June 19, 2024) - same issue.

(Thanks for posting this! Will try the CLI route.)
Andreas Hartig 15 Reputation points MVP

2024-06-22T15:19:54.3066667+00:00

Are you getting the "the given key was not present" error? It has been fixed for everyone I know, that had the issue. If it is another area, please share more details.
Did it work using the CLI route?
Karl Wester-Ebbinghaus 41 Reputation points MVP

2024-06-23T11:45:41.8+00:00

Can confirm it is fixed. However it might appear a new issue that wizard will stuck populating the region. Circling balls forever.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2024-06-25T08:05:24.26+00:00

@Karl Wester-Ebbinghaus Thanks for sharing your experience.

Answer 2

Karl Wester-Ebbinghaus 41 MVP

This issue is confirmed to be a bug. Fix is underway.
reference: This issue is confirmed to be a bug.reference: https://techcommunity.microsoft.com/t5/windows-server-insiders/b26085-two-kind-of-arc-setup-wizard-troubles/m-p/4131358#M3607

Anwar Mahmood 16

occurs 2025-01-21 with

ProductName       : Azure Connected Machine Agent
Comments          :
CompanyName       : Microsoft Corporation
FileName          : C:\Program Files\AzureConnectedMachineAgent\azcmagent.exe
FileVersion       : 1.48.02881.1941
ProductVersion    : 1.48

Answer 3

Andreas Hartig 15 MVP

Weird. Didn't saved my first answer.

Update to the latest Windows Operation System and Azure Arc Agent.

26040 has expired per what I can see: https://betawiki.net/wiki/Windows_Server_2025_build_26040#:~:text=Windows%20Server%202025%20build%2026040%20is%20an

User's image

For more information you can also run the azcmagent connect command using --verbose.

Daniel Casota 91 Reputation points

2024-10-16T09:53:19.3766667+00:00

+1 I think it's a version issue. 26040 has had several issues. Unfortunately, upgrade to 26280 fails, too. Complete reinstall seems to be the only solution.
Daniel Casota 91 Reputation points

2024-10-16T11:46:12.81+00:00

I've reinstalled Windows Server 2025 Datacenter 26280. Now it's not the same issue anymore. Strange.

One tenant has been deactivated recently. Now it seems to have become a permission issue. I will try 26304 as well as permission double checks.
Daniel Casota 91 Reputation points

2024-10-16T13:01:33.4366667+00:00

Upgrading to 26304, Azure Arc functionality is back. Nice!

Share via

Azure Arc Configuration - The given key was not present in the dictonary (GUI only)

3 answers

Your answer