Hi @RaGau
Thank you for posting your question in Microsoft Q&A.
Based on the information you described, I understand that:
You are trying to enable DKIM for a custom domain in Microsoft 365, but in the DKIM settings you only see the default onmicrosoft.com domain. Even though the custom domain has been added and set as the default domain in the tenant, it does not appear in the DKIM configuration.
Based on my research, DKIM for Microsoft 365 is only available for custom domains once all required DNS configurations are fully completed. If the custom domain has not finished these prerequisite steps, Microsoft 365 will only display the default onmicrosoft.com domain in the DKIM settings.
As a first step, please check that your custom domain is in a “Healthy” state in the Microsoft 365 Admin Center. The domain must have all required DNS records properly configured, including:
- MX record
- SPF record
- Domain verification record
If the domain has already been verified and shows as healthy, the next step before enabling DKIM is to add the two required DKIM CNAME records at your DNS provider. After creating these records, please allow some time for DNS propagation.
Once the CNAME records are in place, you can enable DKIM by navigating to: Microsoft Defender Portal > Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM and then turning on DKIM for your custom domain.
Please refer the following document: Set up DKIM to sign mail from your cloud domain
Regarding DMARC, you may refer to the following Microsoft documentation for more details:
Set up DMARC for active custom domains in Microsoft 365
I hope this information helps clarify the issue and guides you through the correct configuration steps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.