MicrosoftHi Petri-X,
I'm glad you have it working, when you see the SSO and caa10001 errors it is normally conditional access or sometimes ADFS issues.
You may also need to set a system proxy on the device itself, I would normally use an elevated command prompt and enter netsh winhttp set proxy <proxyserver>:<port> "<local>;<other bypasses>"
That way the windows updates and the windows store can access their relevant services through the proxy without failing.
The idea of the local Skype account is that is doesn't have access to anything at all on the corporate network, whereas a local domain account has access to AD which will technically weaken the security score of the device.
As these are meant to be treated as a drop in appliance just like a CISCO or Polycom device, where you just configure the required accounts to access a specific service rather than a desktop (albeit it is running Windows 10 like the other desktops). I recommend that these devices are put on a seperate VLAN like you would with any other real time voice/video device and completely separate it from your corporate network.
For the inner workings of the software, the application works as two separate applications so one will log into Skype and one will log into Teams, they each will do their own discovery so work perfectly for hybrid situations. The calendaring is done on the overlay level and that will log into your Exchange mailbox, which will also do its own discovery to reach. For the end user they act as one seamless experience.
I hope this helps.
Thanks,
Dan
