diff --git a/DMARC-how-to.md b/DMARC-how-to.md
index b81139f..0831a3d 100644
--- a/DMARC-how-to.md
+++ b/DMARC-how-to.md
@@ -21,6 +21,7 @@ DMARC addresses this problem and enables the owner of a domain to take explicit
 * RFC 7489 [states](https://tools.ietf.org/html/rfc7489#section-6.4) that the tags dmarc-version ("v=") and dmarc-request ("p=") should be on the first and second position of the DMARC record. The order of the other tags does not matter: "components other than dmarc-version and dmarc-request may appear in any order".
 * [Errata 5440 of RFC 7489](https://www.rfc-editor.org/errata_search.php?rfc=7489) states that a semicolon should be included in the DMARC version tag. Correct: "v=DMARC1;". Incorrect: "v=DMARC1". 
 * When using office 365, the forwarding of calendar appointments from a DMARC projected domain fails. This is a known issue. Read more on the [Office 365 UserVoice forum](https://office365.uservoice.com/forums/264636-general/suggestions/34012756-forwarding-of-calendar-appointments-from-a-dmarc-p) and don't forget to submit your vote! 
+  * There is a workaround: Forward the appointment as an "iCalendar file" or as an attachment. 
 
 # Creating a DMARC record
 The DMARC policy is published by means of DNS TXT record.