Forum Discussion
New sign-in experience for Office 365, what's it about?
No that's the bad news. Seems like you need to do it per document.
- Simon CurrierAug 07, 2017Copper ContributorFunny enough it is our old Virtual desktops (appV) that will be hit most with the 2010 issue. Its on its way out so should not be a disaster.
- Geoffrey BronnerAug 05, 2017Steel ContributorDefinitely a challenge.... or a good argument for running virtual desktops on those older workstations.
- Scott McGrathAug 05, 2017Copper Contributor
Yeah, I've seen it a couple of times so it seems as though even though cookies are removed it still tries to default to MA.
I was talking to my manager about this very thing. I think MS has kind of handled this badly but at the end of the day, Office 2010 is 7-year-old software. In the future, this won't matter because theoretically, anyone with an O365 License will be running the updated desktop software.
that said the main thing holding us back is the workstation refresh which I would say is a challenge for most of, if not at least a lot of large environments
- Cian AllnerAug 05, 2017Silver Contributor
I'm pleased Microsoft is trying to work this out with you, hopefully, the traces will reveal something.
So the problem is reoccurring randomly, even when reverting to the old sign-in experience after clearing cookies?
There seem to be more customers out there with Office 2010 connecting to Office 365 than I would have thought! I can see from Microsoft's point of view, why they are changing support for just subscription clients or Office perpetual clients within mainstream support, in a few years, to simplify these sorts of support issues.
- Scott McGrathAug 05, 2017Copper ContributorDoesn't seem to be per document but I have seen the following.
1. Had the error after pressing the link.
2. Cleared cookies
3. Worked fine.
4. Error randomly came back on another document. - Simon CurrierAug 04, 2017Copper Contributor
I had an issue in one enviroment where clearing the browser only allowed the doc to be opened. Once it closed it seemed to invoke the new Experience in the background and hence errored. Not fully investigated but may also cache in the Office 2010 application. We will just advise users not to use it.