Chrome Version: 72 (and probably sooner as well)

What steps will reproduce the problem?
(1) Manually configure a network connection as user/device config
(2) Add a device policy for that network

What is the expected result?
Network configuration should be managed (not changeable and have policy indicators)

What happens instead?
Network remains as user setting (i.e. no policy indicators, user can edit config)

If the new network config comes from user policy, it overrides the user/device config as expected.

The scenario where we add a device network policy for an already configured network is probably not that common, but still this behavior feels wrong to me. It definitely confused me yesterday during investigation for another bug.

@stevenjb: is this working as intended or is this actually a bug?