Anyone else using the 'DisableOneAuth' office regi...
# microsoft-365
s
Anyone else using the 'DisableOneAuth' office registry key to help with SSO when launching office products for the first time (and after periods of no use)? Had this in place at the recommendation of Microsoft support, and it worked for a while, but doesn't seem to be working any more, not sure when it stopped working @Nick Panaccio
n
What symptoms are you seeing? It has been working for us in S19 and S25, but we now have a group that is continually told that they need to re-enter their creds for any MS app (Edge, Office, etc.)
s
on net new profiles, first launch of office products prompt...after that hthey are good, unless they don't signin for a while, then they are reprompted again
n
Hmm, I'm not seeing that. If I create a new profile it will SSO the first time like I would expect for Teams and O365
s
blarg, k, could be something enivronmental...ended up opening a ticket on it.
n
MS ticket? Thoughts and prayers, bud
😆 2
💯 1
If you make progress on this please post back. I'm being asked to remove this setting because of an issue a specific group is having.
👍 1
s
will let you know, they asked me to take my dog for a walk and spin in circles 3 times to see if it fixed it...
🤣 1
After some more testing, just removing the DisableOneAuth registry entry makes everything work. Here is what they are saying "Regarding your question about what may have changed based on the evidence collected so far the most likely explanation is that the registry keys previously used to force or influence legacy authentication behavior such as DisableOneAuth, DisableAADWAM, and related Office identity settings are now interfering with the current Microsoft 365 modern authentication flow. These settings were previously helpful in your Windows Server 2025 Citrix VDA environment but they now appear to prevent the modern authentication stack from completing silent sign-in as expected. Microsoft 365 authentication components continue to evolve through Office, Windows, Microsoft Entra ID, Web Account Manager (WAM), and OneAuth updates. Because of that it is possible that a platform update, Office update, Windows Server 2025 update, or authentication service improvement has made the previous registry-based workaround unnecessary in the current environment. In the current state, removing those legacy authentication overrides allows Outlook to use the standard modern authentication flow successfully." I confirmed, just removing the "DisableOneAuth' makes everything work again. However, they are suggesting i remove all the other auth reg keys which i had implemented. Which i have confirmed still works. Over the next week or so i'm going to slowly stairstep the removal of the keys in production and confirm all is well still, aka no prompts.
n
Are those all of the values you will be removing?
s
yes
n
Let me check my environment. We also removed DisableOneAuth which helped. Still need to do some magic with Okta to get it working correctly, but it's moving in the right direction. Amazing how difficult MS makes this entire process.
s
"MS Office Auth is an evolving process", what they mean is it's a moving target
n
lol
They really want you to delete EnableADAL=1? IIRC, that tells O365 to use Modern Auth
That's the only value we're currently using
s
yeah, that's my understanding as well, moving to full modern auth....it does still work with the EnableADAL=1, but at this point if i don't listen to them, with the audience i have, then future issues mnight fall back on me.
n
Gotcha. That'll be my next step if this Okta stuff doesn't work.