Mandatory AccessKey parameter for Import-WACConnection Powershell cmdlet in 2410

To quote Shakespere: "Something is rotten in the state of Denmark."

Seriously, who at Microsoft is overseeing Windows Admin Center anymore? Import-WACConnection was a key cmdlet in our environment; we had a scheduled task to do a daily 'scrape' of our computers' OUs, export that to a .csv file, and then use that cmdlet to import into WAC. Now all of a sudden we need an "access key" - but where's Microsoft's documentation on this?

Here's the page on using that cmdlet, from Microsoft today , Feb 20, 2026: 

https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/use-powershell

Absolutely ZERO mention of a mandatory Access Key parameter is mentioned here. if you try to search the internet for "Access Key" you get LLMs musing that hmm, this does make things a challenge, doesn't it.

In our environment, we literally don't even have the option to generate an Access key. Including a screenshot here:

This is on version 2.6.4

What gives, Microsoft? The Server Manager, which pops up by default on every new install of Windows Server we do, is constantly harping about how we should all be using Windows Admin Center. But yet... no one at Microsoft seems to be taking ownership of the software!

To say nothing about the fact that the .psm1 file has conflicting text in the example, vs the functions. What is it; Import-WACConnection, or Import-Connection, Microsoft?!?

Look for yourself folks; this is the key module file that contains all the cmdlets for the program: 

"C:\Program Files\WindowsAdminCenter\PowerShellModules\Microsoft.WindowsAdminCenter.ConnectionTools\Microsoft.WindowsAdminCenter.ConnectionTools.psm1"