Okay, so how can we work around this? Basically, by using psexec to launch Revit using another Windows user. This allows us to have SSO running in one 'Windows user' and SSO logged out in the other.
- Ensure you have psexec available
- Make a CMD with this text (for Revit 2015):
psexec -u OtherWindowsUsername -p OtherWindowsUserPassword -d -i "C:\Program Files\Autodesk\Revit 2015\Revit.exe" /language ENU
- Open Revit in current user and sign out of A360
- Run this CMD file, and in the new instance of Revit you can sign back into A360
As usual, there may be complications with this method (such as access to different network resources etc), so please use at your own risk :)