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
Azure Arc Configuration - The given key was not present in the dictonary (GUI only)
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"
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
5 answers
Sort by: Most helpful
-
Karl Wester-Ebbinghaus 41 Reputation points MVP
2024-05-11T01:53:39.3766667+00:00 -
Andreas Hartig 15 Reputation points MVP
2024-05-23T09:52:13.2466667+00:00 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.“
-
David Broggy 5,906 Reputation points MVP
2024-10-01T01:07:45.1733333+00:00 still broken. gets stuck at Azure Region with a spinny thing.
-
Daniel Casota 46 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:18:23.61+00:00 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
For more information you can also run the azcmagent connect command using --verbose.