LinkBack URL
About LinkBacks
It should work by default. Have you prevented any sign in via group policy?
Morning all,
We currently use Office 2013 but are working on updating our OS to Windows 10 and also updating to Office 2016.
In Office 2013, when a user logs in and accesses Word/Excel etc they are already signed into Office 365 and can access their One Drive etc. In Office 2016 the auto login doesn't seem to work. The user only has to click on "Sign in to get the most out of Office" to login, but i'd like to get rid of this step if possible.
Has anyone any suggestions on how to get past this?
Thanks in advance
Iain
It should work by default. Have you prevented any sign in via group policy?
Iain.Faulkner (28th March 2017)
That's what I thought, we've not changed any policies that impact on Office (the same policies that are set for 2013 are currently being used for 2016 whilst we're in testing)Originally Posted by FN-GM
Are you using ADFS?
You do know that Office 2013 polices won't apply to Office 2016?(the same policies that are set for 2013 are currently being used for 2016 whilst we're in testing)
Yes we do use ADFS.
Apologies on the settings, we have recreated the policy recreating the settings for 2013 in 2016 as best we can but nothing out of the ordinary.
Is ADFS functioning via OWA on these machines?
OWA looks to be working fine on our test PC's
Hi,
We have a similar but slightly different problem with Office 2016 on W10. It does auto sign in but there are no connected services, or file history. The odd thing is if you sign out, then in again to office, it works and doesn't prompt for password. OWA in IE or edge does SSO.
We only have a few office policies
Microsoft Office 2016/Miscellaneous
Block signing into Office Enabled
Block signing into Office Org ID only
Microsoft Office 2016/Privacy/Trust Centerhide
Disable Opt-in Wizard on first run Enabled
This is beginning to drive me round the bend now.....
Office 2013 is deployed through SCCM and on a PC in a test OU with no GPO inheritence, logged on as a user in a test OU with no GPO inheritence connects immediately to office 365 and the user picks up one drive and sharepoint as save locations. With Office 2016 with the same customised deployment settings as we have for 2013 on the same PC and same user, it doesn't automatically connect to Office 365. If I click on "Sign in to get the most out of Office" and enter the email address of the user, it will then connect. But why doesn't it do it automatically? Everything I've read suggests this should be normal behaviour for Office 2013 & 2016.
Anyone had a similar issue?
Have you managed to sort this one out?
I am having the same issue. The settings that worked on Office 2013, don't seem to work correctly with Office 2016.
Trying to sort this out before I deploy Windows 10.
No, we got no further with this :-(
OK, I will continue my search and see what I find
For this to work you need the Click to Run version of Office 2016, the stuff you download from Office 365 rather than the Volume Licensing center. That has it's own caveats which I'm now working on; for instance that then activates the software against that user - which is limited to 5 concurrent activations. So there's shared and/or device activation to deal with, which I'm trying to get my head around now. We're doing SSO with Azure AD Connect, it's working well (Windows 7) on my test machine.
Why did MS have to mess around with these things, makes our lives so much more difficult.
Indeed. I've love the SSO ability in standard 2016 as I don't like the idea of things going a bit sour if there's no internet connection and it's unable to activate. Even with the world's most solid internet connection I don't want that a prerequisite. So will make do with 2016.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
