Hello Johan-Kr,
We have been discussing this the past couple of days. It looks like the e-mail notifications that Apple Support Communities sends out are now optimized for Apple devices. The most recent change seems to be targeted at the Apple Watch. Apple is using an unusual e-mail format that will, or at least should, display the abbreviated content you describe only on the Apple Watch. In your case, your Exchange server may be scrambling the e-mail.
Although it is an unusual e-mail format, it is perfectly legal according to the published e-mail standards. The idea is that an e-mail message can contain the same content in various levels of "richness". Email clients are supposed to go down the list of alternative versions of the message and present to the user the best version they can support.
In the old, standard version, e-mail worked like this:
text-only version of e-mail
fancy html version of e-mail
In the new format, ASC notifications now look like this:
text-only version of e-mail
basic, but abbreviated html version of the e-mail
fancy html version of e-mail
Any properly designed e-mail client should render the last version with no problem. But buggy clients might see the abbreviated HTML version and just stop there. This might also apply to servers. Each time an e-mail message passes through a server, it may be broken apart, scanned for viruses, and then reassembled. Sometimes that doesn't work properly. I suspect that is what is happening in your case. This has been an ongoing problem for Apple for many years. Apple e-mail clients have always had the best support of e-mail standards but when people try to use them, the results are sub-standard if the recipient isn't using a full Apple e-mail stack.