DKIM CNAME for office 365

You are not giving us much to work with. In general, that's how the records should look like. Have you made sure that they have propagated already, can you resolve the CNAMEs externally and the actual TXT record for the key? Have you enabled it on O365 side, what does Get-DkimSigningConfig show?

ok, i got a little futher but im getting an error with MXTOOLBOX but DMARC Analyzer is ok

The correct syntax is

selector1_domainkey
selector1-abc-com._domainkey.tennantname.onmicrosoft.com

Below is the output for MXTOOLBOX

dkim:abc.com.com:selector1 Find Problems  

Error

v=spf1 ip6:fd1d:f5c3:e7c6::/48 -all

ag       TagValue       Name       Description       Error
v       spf1 ip6:fd1d:f5c3:e7c6::/48 -all       Version       The DKIM record version.       Version MUST have the value of 'DKIM1' (all capitals)
p       Public Key       Public-key data. The syntax and semantics of this tag value before being encoded in base64 are defined by the (k) tag.       Missing from public DNS record

      Test       Result       
      DKIM Syntax Check       The record is not valid        More Info
      DNS Record Published       DNS Record found       
      DKIM Record Published       DKIM Record found       
      DKIM Public Key Check       Public key is present

If i look at the DNS domains in Office 365 tenant i see this

TXT
-
selector1-abc.com._domainkey
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB..

Looks like an issue with the MX toolbox validator to me...

No it is an error in the cname...
Appearantly you have connected the DKIM selector (a TXT record starting with v=DKIM1..."
pointing to the SPF record, (which starts with "v=SPF1...)  which indeed is not a DKIM selector.

Or the wrong test was specified for MXTOOLBOX.... i do known MXTOOLBOX is not the confused toolkit.

it looks like there is a *.com.com TXT records that contains a spf record....

Maybe try again with more valid data. The *.com.com spf records doesn't hold a microsoft entry as well...