Security Policy Errors

Fix DKIM TXT Record Configuration Error in Microsoft 365

John Wilson Oct 15, 2026 868 views

Question details

Users encounter a "Configuration Was Not Created" error preventing the rotation or modification of DKIM TXT records.

How to Fix DKIM TXT Record "Configuration Was Not Created" Error in Microsoft 365

Product: Microsoft 365
Device & OS: not provided
Scenario: Attempting to rotate Microsoft 365 DKIM records via PowerShell or the web interface, or trying to upgrade keys to 2048 bits.
Observed behavior: The system displays unusual selector names and fails to rotate or upgrade the DKIM keys, returning a configuration error.

Before you start

Verify that you have Global Administrator or Exchange Administrator permissions in Microsoft 365 before attempting to manage DKIM records or open a support request.

Solution 1Recommended

Open a Service Request in the Microsoft 365 Admin Center

Since this DKIM rotation failure involves backend service anomalies, Microsoft Support must investigate the issue directly with the required permissions.

When PowerShell commands and web interface actions fail with configuration errors and display unusual selector names, the issue is rooted in the Microsoft 365 backend. Standard administrative tools cannot override this block.

Microsoft support engineers need to collect service logs and manually clear the anomalous configurations from their end before you can successfully rotate your DKIM keys to 2048 bits.

Sign in to the Admin Center

Navigate to admin.microsoft.com and sign in using your Microsoft 365 administrator credentials.

Access Help & Support

Click on the 'Help & support' icon located at the bottom right corner of the admin center dashboard.

Describe the Error

Type 'DKIM TXT Record Error: Configuration Was Not Created' into the search bar. Review any automated solutions, then select 'Contact Support' if the issue remains unresolved.

Submit the Request

Provide the exact error message, mention the unusual selector names you observed, fill in your contact details, and submit the ticket for backend investigation.

Open a Service Request in the Microsoft 365 Admin Center

Investigation Time: Backend investigations may take 24-48 hours. Ensure you provide clear screenshots of the error and your PowerShell output to expedite the process.

Free Microsoft Office alternative

Manage Your Documents Efficiently with WPS Office

While waiting for Microsoft 365 support to resolve your backend domain and DKIM configuration issues, you can continue working on your essential business documents smoothly. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the software.
3. Open Your Office Files: Launch WPS Office and directly open your existing Microsoft Office files to continue your work without formatting loss.

Maintain business productivity while experiencing Microsoft 365 administrative or backend domain issues.Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Lightweight design ensures fast installation and smooth operation on older or lower-spec devices.Familiar tabbed user interface allows for an immediate transition with zero learning curve.

microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 show unusual selector names for DKIM?

Unusual selector names usually occur due to backend synchronization issues or conflicts between legacy configurations and new key rotation attempts. Microsoft support must clear these anomalies directly from their backend.

Can I manually fix the 'Configuration Was Not Created' error using PowerShell?

No. If the standard Exchange Online PowerShell commands for rotating DKIM fail and return this specific error, it indicates a service-level blockage that cannot be resolved through client-side administrative commands.

How long does it take for DKIM changes to propagate in Microsoft 365?

Once the backend error is resolved and you successfully rotate or upgrade your keys, DNS and DKIM changes typically take anywhere from a few minutes up to 48 hours to fully propagate across the internet.

Microsoft Office Security Issues