andy33 Nope. CVE-2023-23397 is an Outlook vulnerability, not Exchange. Note, though, that Extended Protection is a related feature that can help with possible abuse of tokens if they were to be taken. In other words - it s a great idea to enable Extended Protection but EP is not a direct solution for CVE-2023-23397. For that, you should be installing Outlook updates.
Nick_Mantia It has been mentioned before that an additional reboot made the Search work after Feb issues. We did not have a fix for this specifically in March SU, no. I am not aware of the CRM issue (was this related to add-ins?) We know that some customers had their issues with add-ins resolved with March SU; we do have a code change in March for this but it was not 100% solved so we removed it from "Issues Resolved" and this is still under investigation.
Dobongsoon See this page: https://learn.microsoft.com/en-us/officeupdates/microsoft365-apps-security-updates - apologies, though, I am not totally up to speed with all the flavors of Outlook and Office and where to get the updates but I hope that helps.
Tseeker99 If there are old messages with this property set but set to "blank" then you might see this. This is not an indication of a problem. The only time you need to worry about this property is if it points to what is (hopefully) obviously unknown location. We have seen cases where the property is not "not set" but is instead "set" but blank. Unclear why this happened, but as you said - it has been a while ago...