Blog Post
FSLogix v3 Release 25.XX is now in Early Access!
Hi cfarrington - Can you please provide more details about this "1001" error. This is not a known issue related to FSLogix that I am aware of. If this is a known issue caused by FSLogix, I would like to better understand it so that we can log a proper bug and prioritize it.
Jason_Parker, Please see the "FIX" in this link. https://answers.microsoft.com/en-us/outlook_com/forum/all/outlook-365-app-error-1001-on-rds-environment/e6ae8598-81a0-4859-846a-d9509b246bf4?page=24
I am in the MSP space and we are also seeing more and more ODFC (office) activation, sign in issues with FSLogix containers. I am currently looking at this issue with a client. It would be fantastic if FSL and Office teams can get together to document actual configuration guidelines for office installs.
The question I have for you and the FSL team is this:
With what MS support provided and what is documented in the "FIX". What should we be setting or best outcome for MS office products in the FSL space? Or is just enabling a default install along with "Roam Identity" sufficent. I read about enabling "Hybrid Join", Single Signon, ADAL, WAM.. so many things to consider.
Please read over the "FIX" from MS support and provide feedback for proper Office Enterprise Apps + FSL best practices for roaming identity and roam activation for office.