Can You Downgrade a Microsoft 365 DKIM Key to 1024 Bits?
Question details
The user wants to know whether a Microsoft 365 DKIM key can be downgraded from 2048 to 1024 bits and how to troubleshoot DKIM authentication failures.

- Product
- Microsoft 365 DKIM
- Device & OS
- not provided
- Scenario
- A hosting provider supports only 1024-bit DKIM keys, and the user is investigating DKIM authentication for a Microsoft 365 domain.
- Observed behavior
- DKIM authentication stopped working after previously working for months. The existing key was reported to be 1024 bits, so the failure may not be caused by a 2048-bit key.
Identify the affected email domain, its DNS host, and the administrator account for the Microsoft 365 tenant. Check the current DKIM key size and selector before assuming that a key-size mismatch caused the failure.
Verify Microsoft 365 DKIM Selector CNAME Records
Use this check when DKIM authentication fails or the domain is managed through a reseller.
Microsoft 365 does not generally provide a standard setting to downgrade an existing DKIM key to 1024 bits. A DKIM failure can also result from incorrect DNS records or tenant configuration, even when the key is already 1024 bits.
Sign in to the Microsoft Defender portal and open Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM. Select the affected domain and review the required CNAME records.
Open the domain's DNS management page and compare the selector1._domainkey and selector2._domainkey CNAME records with the Microsoft 365 targets shown for the domain. Correct any mismatched or missing records.
If the tenant is managed through a reseller such as GoDaddy, contact the reseller to confirm the expected DKIM targets and tenant configuration. Make DNS changes at the provider that hosts the domain's DNS.
Allow DNS changes to propagate, then send a test message and inspect its authentication headers for the DKIM result and selector.

Rotate or Re-enable Microsoft 365 DKIM
Try refreshing the DKIM configuration after confirming the DNS records and tenant settings.
Work With Office Files While Managing DKIM Troubleshooting
WPS Office is a free, lightweight alternative for working with documents and spreadsheets in a familiar interface. It supports common Microsoft Office formats for an easy transition, but it does not configure or repair Microsoft 365 DKIM.

Frequently Asked Questions
Is there a standard Microsoft 365 setting to change DKIM from 2048 to 1024 bits?
Microsoft 365 does not generally provide a standard setting to downgrade an existing DKIM key to 1024 bits. Verify the current key size and contact Microsoft or your tenant reseller if you need guidance for your configuration.
Which DNS records should I check for Microsoft 365 DKIM?
Check the selector1._domainkey and selector2._domainkey CNAME records in your domain's DNS management page. Compare their targets with those shown for your domain under DKIM in the Microsoft Defender portal.
Can DKIM fail even if my key is already 1024 bits?
Yes. Incorrect selector CNAME records, DNS propagation, or tenant configuration can cause authentication failures independently of the key size. Inspect the message's authentication headers and verify both selector records.
Will rotating DKIM keys force a 1024-bit key?
No. Rotation may help refresh the DKIM configuration, but it does not guarantee a downgrade to 1024 bits. Check the resulting configuration and allow time for propagation before retesting.
Where should I change DNS if my Microsoft 365 tenant is managed by a reseller?
Make DNS changes at the provider that hosts your domain's DNS, which may be different from your Microsoft 365 reseller. Ask the reseller to confirm the DKIM targets if you are unsure.




