Announcing New DMARC Policy Handling Defaults for Enhanced Email Security

This policy change does seem to have caused a huge problems for email forwarding, as others have noted, even between Outlook accounts. Previously the Anti-Phishing rules would randomly bursts of sending a whole heap of legitimate emails into junk (sometimes just one or two from the same regular sender) - annoying but retrievable if you remember to regularly check junk and hopefully 'train' the system. Now, however, a random (but sizeable) selection of legitimate emails forwarded from other accounts are being rejected entirely sometimes without even being identifiable to see what they are (helpfully, the rejection message on my phone app includes an attachment which lets me read the rejected message but not reinstate or reply to it, which at least has saved me from missing several crucial messages - the desktop version doesn't even allow this).  My forwarded emails come from a large institutional address which has a pretty good security system anyway. As a sole trader I've had to go to great lengths to find out the cause of this problem - which seems to be the upgrade of the dmarc settings - and even more work to try and locate where to change this in the Microsoft 365 Defender/Policies&Rules/Threat policies/Anti-phishing settings. Currently it seems to be giving me a 24-48 hour 'cooling off' period before deciding whether it will let me change the settings for both p=reject and p=quarantine to Quarantine rather than Reject? Super unhelpful for microbusinesses - seems to be no clear response to the forwarding error and no advice on how to set a 'safe forwarding domain' to override this highly disruptive error. (Note: so far it has not rejected ANY actual spam - and still lets through the usual small amount of spam as usual so I'm not sure how this is an improvement). Any thoughts or suggestions appreciated. Danielle