UShort Error with the Exchange Module

Just as an update, as of today I was able to issue Rotate-DkimSigningConfig from within Powershell 5.1 using ExchangeOnlineManagement 3.7.0. While the command is loaded remotely it seems Microsoft has done some fixes on their end?

However the support experience has been really bad IMO:

Github was not the right place. Microsoft Support when contacted as indicated in their documentation, wanted to register a screen recording given the exact steps on how to reproduce the issue. They tried nudging me into sending a "feedback" on their documentation pages instead of acknowledging the issue and wanted me to accept closing the ticket several times while the issue wasn't fixed.

balaclava 

I had the same problem and just wanted you and everyone else who finds this article know that if you run the cmdlets in Powershell 7 it works.

balaclava 

This is just an aside to point out what is impacted by this bug - and it is a bug:

• New-DkimSigningConfig
• Rotate-DkimSigningConfig

In both cases, they are incorrectly declaring the KeySize parameter as follows, where [ushort] is invalid:

    [ValidateSet('1024','2048')]
    [ushort]
    ${KeySize}

Cheers,

Lain

balaclava 

same here on all tenants.

i hope this bug will be resolved soon.

balaclava 

That seems like an Exchange bug.

ushort only pertains to Visual Basic, whereas PowerShell is aligned to C# and the Common Language specification, in which there is no ushort.

• UShort Data Type - Visual Basic | Microsoft Learn
• Integral numeric types | Microsoft Learn

If you have premier field support (PFS) or some other channel to report it directly to Microsoft, you should probably do so.

To get by in the interim - assuming this is occurring on the latest release, you might want to try removing the version you have installed and backdate to a previous version. Conversely, if you're on an older version, try updating to the latest.

If this fails, then the issue is within the dynamic module that the installed module pulls down during the call made with Connect-ExchangeOnline, in which case perhaps there is no workaround and you just have to wait for the fix, which is why lodging a bug via PFS is important.

You might also want to ask this question in the Exchange forum, as this isn't strictly a PowerShell issue and more people there would work with Exchange (you'd hope, anyway).

Edited to add the following:

I've just given the commandlet a quick try and the bug is unfortunately in the dynamically-loaded code as evidenced below. So, you'd have to go via PFS for this one.

Perhaps a dependency was missed or something in a recent update - no idea, but there's nothing you can do to fix this one, I suspect.

Edited again to correct myself:

[ushort] exists in C# but it's correct that it's not in the CLS, and certainly not natively in PowerShell as a result.

Cheers,

Lain