In my opinion we were not expecting this kind of bugs/changes crashing the product. Microsoft states: "Product functionality and feature availability may vary on older systems" and "....quality of your Microsoft 365 experience may diminish over time." I did understand in the way, that we were not receiving any additional functionality and may not receive security updates. That's fine. But essentially behind this marketing sentense above, its says in reality: "We can do whatever we want. If you don't update to the newest version, be prepared to loose any service at any time and don't call support for help because we are not going to do anything about it".
This would be more truthful and transparent towards us as paying customers.
I have around 65 Macs which could have the same problem at any time.... not funny at all! Troubleshooting identifying the problematic calendar entry is a nightmare due to poor logging mechanism within Outlook. So I have to discover it by trial/error.
I hope Microsoft decides to do one of the 3 possible things:
- Release a 16.43 Version with the fix in order that Office doesn't crash anymore
- Revert your changes on the Office365 plattform
- provide a detailed description of the bug so we can train our employees not to use that specific feature in Office365 which creates the bug