This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 64%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
I would like to upgrade the DKIM keys to 2048-bit for about 120 domains using PowerShell. I have all the DKIM Guids in a csv. It will be tedious to work on each.
I have this command for individuals but I need to tweak it to do the same action for the imported csv file with all the 120 domains.
Rotate-DkimSigningConfig -KeySize 2048 -Identity {Guid of the existing Signing Config}
Any guidance is appreciated.
Assume the column name is "Identity" in your csv
Example:
$DKIM = Import-csv DKIM.csv
$DKIM |% {Rotate-DkimSigningConfig -KeySize 2048 -Identity $_.Identity}
Thanks Andy,
That worked.
On the same token, Is it best practice to rotate again as soon as the current rotation is applied to make sure both selectors are upgraded to 2048? Most of the domains had both selectors on 1024, and after running the above command, only one selector is upgraded, which am assuming is the expected behavior. Not sure if that will be the best approach to make sure I have all domains with 2048 on both Selector1KeySize and Selector2KeySize.
I would:
If you want to rotate to the second selector, your options are a) let the Microsoft 365 service rotate the selector and upgrade to 2048-bitness within the next 6 months, or b) after 4 days and confirming that 2048-bitness is in use, manually rotate the second selector key by using the appropriate cmdlet listed above.
Ok, perfect. Thanks for confirming with documentation.