This message was deleted.
# microsoft-fslogix
s
This message was deleted.
c
Newer versions of Fslogix has a 0365 modern Auth roaming policy setting to fix O365 sign in issues related to WAM
r
Yea, you are right. that is the include offication activation "Registry Entry: HKLM\SOFTWARE\Policies\FSLogix\ODFC\IncludeOfficeActivation"Correct?
c
Nah this
RoamIdentity Type: DWORD Default Value: 0 Data values and use: 0: Don't roam credentials and tokens within the container. 1: Enables legacy roaming for credentials and tokens created by the Web Account Manager (WAM) system. Important The default setting is to not roam the credentials or tokens which is the preferred setting. While this may not be the ideal configuration for some customers, we created this setting to provide customers a way to roam these items similarly to FSLogix v2201 hotfix 2 (2.9.8228.50276). We continue to work with our Identity teams on a long term solution.
r
Thank you
c
Are you getting sign in prompts or activation issues?
If it's activation issues you can use includeofficeactivation key you mentioned or the SCLcacheoveride setting in a gpo or add it in the office configuration.xml from the ODT
Make sure you use shared computer activation as well In your xml
r
I am getting the details, I had a client reach out and tell me they get activation issues all of a sudden. I need to get the details to be clear
Activation prompts I mean.
Going off Second hand info as well. So I am getting the facts
c
I bet it will be sign in prompts rather than activation issues. The roam identity fslogix policy should fix it if they are not azure ad joined or hybrid joined
🙏 1
a
So to fix the login prompts, you need to configure "RoamIdentity" with the value "1", right?