'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Microsoft Forms Reminder Bounces (NDR Error 550 5.1.10)
Question details
Administrators need to resolve NDR error 550 5.1.10 caused by Microsoft Forms sending automated reminders to former employees.
- Product
- Microsoft Forms and Exchange Online
- Device & OS
- not provided
- Scenario
- Automated reminders from a Microsoft Form are being sent to a Teams group or mailing list that still contains former employees, triggering bouncebacks.
- Observed behavior
- The sender receives an NDR (Non-Delivery Report) error 550 5.1.10 because former employees still have lingering onmicrosoft.com aliases or have not been fully removed from the synchronized directory.
Ensure you have global administrator or Exchange administrator privileges in your Microsoft 365 tenant, as well as administrative access to your on-premises Active Directory server.
Complete the Hybrid Offboarding Process
Properly offboarding users in both on-premises AD and Exchange Online prevents ghost accounts from receiving automated form reminders.
In a hybrid environment, deleting a user in the cloud or simply removing their Microsoft 365 license is often insufficient. Stale onmicrosoft.com addresses can remain in distribution lists or Teams groups.
Log in to your on-premises Active Directory Users and Computers (ADUC) server and locate the former employee's account.
Disable the user account and manually remove them from all synchronized distribution lists and security groups associated with the form.
Open PowerShell on your Azure AD Connect server and run a delta synchronization to immediately replicate the changes to Microsoft 365.
Check the Microsoft 365 Admin Center to ensure the user is completely removed from the targeted Teams connected to the Microsoft Form.
Modify Form Sharing and Teams Group Settings
Remove stale users directly from the specific Microsoft Teams group or form notification list.
Investigate Mail-Flow Logs and Contact Support
If stale objects persist after offboarding, analyze mail-flow logs and escalate the backend synchronization issue to Microsoft Support.
Boost Your Productivity with WPS Office
Complex backend synchronization issues in Exchange environments can be highly time-consuming. For your everyday document, spreadsheet, and presentation tasks, consider WPS Office. It offers a powerful, lightweight, and completely free alternative that works seamlessly without complicated directory setups.
- 1. Download the Installer: Visit the official WPS Office website to download the free installation package tailored for your operating system.
- 2. Install the Suite: Run the setup file and follow the simple on-screen instructions to complete the installation.
- 3. Start Creating: Launch WPS Office and immediately start opening, editing, and saving your existing Microsoft Office files.
Frequently Asked Questions
What causes the NDR error 550 5.1.10 in Microsoft 365?
This Non-Delivery Report (NDR) error occurs when an email is sent to a recipient address that does not exist or cannot be found in the directory. In hybrid environments, it frequently happens when an employee departs and their account is partially deleted, but hidden aliases or group memberships remain active.
Why do Forms reminders bounce even after I remove a user's license?
Removing a Microsoft 365 license restricts the user's access but does not automatically remove their account from Microsoft 365 Groups, Teams, or distribution lists. When the Form attempts to send a reminder to the entire group, it includes the unassigned user account, triggering a bounce.
How long does it take for Active Directory changes to sync to Microsoft 365?
By default, Azure AD Connect synchronizes on-premises Active Directory changes to Microsoft 365 every 30 minutes. If immediate updates are required to stop form bouncebacks, administrators can manually force a delta sync using PowerShell.
