Copy meetings from one calendar to another no longer supported

I appreciate your sincere attempt to give a helpful answer. You're doing what you were instructed to do. You may not be understanding that your instructions are tantamount to "keep sweeping this under the rug."
What you are not understanding, and this is coming from a former developer as well as a former manager of development, is that the "risk of the copy function causing corruption on meeting items" is the bug that MS should have fixed from the beginning. THAT BUG is the source of all this angst and probably loss of some of your customers. MS has this 'meeting copy corruption bug' and instead of fixing it they simply stopped 'supporting copy.'

Thanks for offering to share the feedback. It won't matter. Whomever is in charge of development would rather not endure the embarrassment of acknowledging what I just wrote. Or bean counters higher up decided it simply isn't worth the expense of developer labor to fix it. Either way, this is stunningly inept.

Gabriel,

Please add macOS to the list. The registry edit option is only viable on Windows machines. macOS office users have been given NO viable alternative or workaround. I feel completely forgotten about over here!

Please provide a workaround that is viable on macOS, or have the team add back in the feature on macOS specifically. This has become extremely cumbersome and I have to deal with it every week. If there is still fear of corruption, then make it a setting that defaults to OFF or something. Removal of a used feature should be a last resort. This thread is indicative of the consequences.

This is Microsoft being Microsoft... I mean, it seems they purposely evaluate the features users like most to go there and mess up with them... they do it since 90's and this time is not different :(

Very very frustrating.

Dave,

The reason the Outlook Team blocked copy meeting by default is that there is risk of the copy function causing corruption on meeting items. They wanted to discourage people from doing this. For those that have long used it and never had issues they decided to have the registry key to re-enable. I'll share your feedback to team that this is not workable in locked down environments.

Gabriel, Are you a real person? Just curious because the 80% of us who are in corporate America are fatigued with seeing this work-around that we can't even try to use because our systems are locked down.
Even if we could, forcing us to use a manual work instead of fixing your design problem is really, really poor look. I know it's not your fault, it's your management. Let them know many of us are seriously displeased and that them sending you here to keep posting this "fix" makes them look even worse.