Forum Discussion
SSO in Office 365 ProPlus with SCA (Shared Computer Activation)
Hello,
I find very little information on SSO into Office 365 ProPlus when it is deployed using SCA.
Should it be possible for a user to log into Windows (domain joined, AADSync, no roaming profiles)
and be logged in automatically into Office ProPlus
or will he always have to enter his credentials as well in Office ProPlus (deployed using SCCM with Shared Computer Activation)?
Bart
9 Replies
- Bill HughesCopper Contributor
With Shared Computer Activation the user is always prompted for their username on first launch.
With Federated Authentication (SSO) it is possible to remove the requirement for them to enter their password and only require them to enter their username at which point the authentication dialog will redirect them to your federated sign on page which would automatically sign them in. If however a individual users first use on a machine occurs outside the network this would not happen as most federated authentication deployments present forms based authentication to all external off network devices. (Remote Desktop is generally still inside the network from a federated authentication perspective)
The SCA first time user experience is documented here: https://technet.microsoft.com/en-us/library/dn782860.aspx#How shared computer activation works for Office 365 ProPlus
- Sonia CuffIron Contributor
In addition to Bill's comments, that log in and activation should only appear on first use.
The licensing token system means every time after that, the background process will contact the licensing server and attempt to renew the token in the backgorund, without the need for additional username and password entering by the user.
-Sonia
- Madhu PereraCopper Contributor
Hi Sonia,
We have deployed Office 365 ProPlus on Remote Desktop Servers for few of our clients. All of them are getting prompted to re-authenticate every now and then. One of the clients has no proxy either but they are always prompted to re-authenticate every 30-40 days on their terminal server.
Have you seen or heard about this behaviour before? It is a pain for the clients with a large number of Terminal Server users.
Thanks in advance.
Madhu