We recently built our Exchange 2016 environment. We are seeing the Microsoft Exchange Notifications broker service is set to Automatic, but is not started. According to the Release notes for Exchange 2016 in this article:

That service will start at reboot or when it has something to do. Our issue is that we have SCOM for monitoring our server environment and it will continue to trip alerts for this service being stopped.

My question is this: Does this service have to maintain the startup type as Automatic, or can we set it to Manual. If we set it to manual, what are the side effects or what might we miss. Just looking for a direction here before I ask my SCOM admin to put in an override that ignores that particular service.

I think you should keep the start type to automatic and create an Override rule in SCOM to ignore any alerts caused due to this service

Keeping the start type to manual Wont trigger it to start and stop during any config changes as recommended by MS in above article

I think you should keep the start type to automatic and create an Override rule in SCOM to ignore any alerts caused due to this service

Keeping the start type to manual Wont trigger it to start and stop during any config changes as recommended by MS in above article

Keeping the start type to automatic is recommended by MS, it willperform a configuration check on each time the server starts and avoid missing any unknown changes occurred. Ignore the alertscaused bythis service would be a wise choice.