Anyone know how to control this option (Edge, auto...
# microsoft-365
n
Anyone know how to control this option (Edge, automatically sign in with your work account) via GPO/regedit? I have tried every combination of Edge policy settings I can think of, and have not found a way to switch this on outside of manually toggling it.
j
What does ProcMon say when you manually toggle it? Look at Registry Set Value and File Write operations
c
is it this ?
altho that stops all browser sign in so dont think that will work
n
Definitely not that setting. ProcMon shows no registry values being modified, which is a bummer because I was hoping for an easy win. It looks like the Preferences file is being updated, but I'm not sure that I can create a template file for new profiles for this setting. I opened a ticket with MS just in case this is yet another one of those things that they have an unpublished registry value that addresses it. Otherwise, them forcing users to toggle this manually is pure insanity... so par for the course with them, if I'm being honest.
This is the only difference in that file between disabled/enabled:
Yep, you can't pre-stage that file. Edge overwrites it immediately once it logs you in.
j
I remember something similar with Teams. I recall intercepting the first run, editing the file using PowerShell, and restarting the process. I used Ivanti for the trigger handling - could you do something similar with WEM?
n
I could probably use WEM to create a trigger (file creation), then use a PS script to replace that line and save it. Probably a last resort, though.
Or not. I used PowerShell to modify the value after the file is created, and now Edge immediately closes after launching, lol.
j
Glad I don't have to do lots of this stuff any more 🙂
n
Normally I love troubleshooting stuff. But dealing with MS just makes me angry.
⬆️ 1
just want to grab them by the throat and scream at them 'WHY ARE YOU THE WAY THAT YOU ARE'
Hmm, that issue may be due to formatting. Manually adding the value does work. Guess I'll keep that in my back pocket, because I can probably address it with a simple replace and not go the Json formatting route.