Improve the process for allowing OMS agents communicate with OMS Gateway
Currently if you have a server to be monitored by SCOM/OMS, you can configure the monitoring agent to forward event data via an OMS Gateway - to act as your conduit out to your OMS workspace.
Part of this process requires you run a powershell script, for each host you add to the Windows OMS gateway. You have to run the powershell:
"Add-OMSGatewayAllowedHost -host <your_new_host>"
If you have a lot of systems, then you have a lot of manual 'touch-points' needed to do these on a one-by-one basis on the gateway server.
It would be great if you could have an option to 'whitelist' hosts, for example, which are already being managed by SCOM. If the Gateway could validate that the host is managed by SCOM, this should be sufficient to validate that agent is 'allowed' to send data via the OMS gateway.