Hi @Becky Filo ,
What's the version of your Outlook(File>Office account>About Outlook), please ensure that you are working with the latest version of Outlook.
For your issue, I have tried to create a new recurring meeting by New Meeting option and remove an attendee by two ways mentioned above on my Outlook365(Version 2008 Build 13127. 20408 Click-to-Run), then choose only send update to him like below.
But according to my test, everything could work normally(the update only be sent to that removed attendee and others haven't received any notice), which seems to I couldn't reproduce your issue.
Do other users in your organization also have this issue?To further conduct the issue, please try to log in your account to your Web Mail and do the same to check if the issue has any difference.
If it could work normally in your Web Mail, the issue may be related to your Outlook client. Please try to troubleshoot your issue by steps below:
- The interference of add-ins may cause this issue, it's suggested to open your Outlook in safe mode(Windows +R>type"Outlook.exe \safe">click enter) to check if the issue would be reproduced.
- Corrupted data files or profiles also may cause it, please try to create a new profile and readd your account(Control Panel>Mail>Show Profiles>Add>type a name for the profile> Add your account>Finish) to check if it's effective for your issue.
- If the issue still exists, you could try to repair your Outlook client.
Update:
What 365 license is assigned to your domain account?
if selecting Send Updates to all attendees it does work as long as the attendee removed was not an optional attendee
According to your description, the issue seems to happen when you remove the optional attendee, and as I know, there's no optional attendee on Outlook for Mac, so that may be the reason why it could work normally like removing required attendee on Outlook for Windows.
So the issue still may be related to your accounts themselves, according to my research, there's no official document that is related to this issue, and I also have tested a lot on my environment but it still could work normally, so in order to further analyze your issue, please try to create a new test account in your organization and do the same operations mentioned above to test if the issue has any difference.
If you have any updates, please kindly post back, and I would still be researching for your issues in the future.Thanks!
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.