Nov 21 2017 01:46 PM
I do not understand how the new home is made accessible to users.
I see all possible mixes of home and launcher experiences.
I am first release and have classic home and new launcher in Chrome but new launcher and new home in IE;
Some users have new home and new launcher in IE even though they are NOT first release.
Others have the classic app launcher but the new home.
It is really hard to manage change if regular users have updates before first release group.
Nov 21 2017 02:10 PM
Yeap, I have seen this and I agree is very inconsistent how the launcher and new home page are being rolled put @Anne Michels can you point us to the right person to talk about this?
Nov 21 2017 02:47 PM
Agreed! We have been talking about some of these things here as well. I've got the app gallery, new app launcher and the old office home experience on selective FR. Changing web browsers for me doesn't make a difference.
The new web experiences shouldn't be crossing over to standard users as I understand it. The Office 365 App launcher is designated as a major update and has 16 days to go (at least) before it goes into general release, according to the Message center.
Just tagging @Brian Levenson in case there is anything we are missing!
Nov 21 2017 05:29 PM
Adding @Tom Batcheler and @Bindu Pillai to help with this.
Nov 22 2017 06:15 AM
Could not agree more, on my Surface I see all new and on my Windows 10 Desktop I see a mix of the new App Launcher and the old home page. The disconnect in consistency make it difficult to let others know what the changes are or when the are coming. Even if you are using your "First Release Group" in your tenant.
Nov 22 2017 07:27 AM
Nov 23 2017 12:49 PM
The same in our tenant. We use a first release tenant. Most users have the new app launcher, but the appearance of the office.com home-page is 50/50 I would say. And that is the case for more than a week now.
Nov 27 2017 12:24 PM
Now that Thanksgiving is over, I was expecting a reaction from MSFT. From what I read here, I am not the only one affected by this strange behavior.
Is it a bug or it is working as expected? It's not the ideal situation when updates are visible outside of first release users before official availability date.
Thanks
Nov 28 2017 04:50 AM - edited Nov 28 2017 04:50 AM
I wonder if @Mark Kashman or @Chris McNulty have any thoughts or updates on this? We are seeing some pretty big inconsistencies across the board with the new app launcher and portal page regardless of location or Operating System. My tenant has even experienced the same person on different machines seeing different experiences.
Nov 28 2017 11:13 AM
It's best if you set expectations by telling your users that Microsoft is consistently inconsistent with everything. Expect nothing intuitive. That way, the one time they do something right, people will be happy. Same behavior here. Thanks again microsoft.
Nov 28 2017 12:44 PM
We’re seeing the same thing happen, so at least they’re consistent in that regard. Perhaps this is a kind of A/B testing scheme?
Nov 28 2017 12:52 PM
Then, it's A/B/C/D testing. We have all possible combinations ;)
Nov 28 2017 02:39 PM
Terrible situation made worse by no response from Microsoft.
Nov 28 2017 02:50 PM
If and when they do, they'll say sorry and they'll pinky swear that they'll do better in the future.
Yeah right, hasn't been the case for years.
Nov 28 2017 03:06 PM
It is strange that we are left guessing when just a bit of clarity would easily set thing right. I've used this example and a couple of others in a new post on what could improve situations like this - More precision with Message center.
One of the points I've made is that this is a 'major update' and now with 9 days to go until potential GA but we haven't got all the components in place to properly evaluate this change. This countdown should only begin once everything is ready, not while parts of it are still rolling out to FR or are glitchy.
Hope we hear what's going on soon!
Nov 29 2017 12:53 PM
So sorry for the delay in responding to this thread.
While the new Office 365 launcher, Office 365 gallery and the new Office.com are complementary experiences, the gallery and Office.com roll out changes faster than the launcher due to fact that they are stand-alone experiences vs. being integrated across Office 365.
The new Office 365 app launcher is in First Release, which began on 11/7 (see MC 124492). Users in First Release tenants will see the new launcher, regardless of browser and/or OS. We plan to progress exposure to a small % of production before the end of this calendar year. We will notify on the Message Center accordingly when we do. There is an FAQ for the new launcher that we update according to feedback and questions available at this location (an update will be published with additional FAQs early next week).
The new Office 365 gallery is currently available to all users in production. The new Office.com is currently rolling out to a % of the overall user base and is expected to be exposed to 100% of users within a few weeks. For Office.com, all users will have the same new experience by mid-December.
Nov 29 2017 01:13 PM
This is not what we experience.
SAME user will see different Office Home depending on browser (IE vs Chrome).
SOME users no mater if they are first release or not will see the new launcher. Others won't.
All that started a few days / weeks ago. We are rolling out Office 365 and try to prepare introduction / training content and we cannot.
We will tell users that it is a dynamic application and that it will constantly change but some stability or predictability would help.
Thanks
Nov 29 2017 01:18 PM
I can confirm that something is not well at all with the home page in Office 365. I have identified at least a customer tenant where they see the old App Launcher, but they see a home page that has nothing to see with expected experience
And customer is not in First Release....
Nov 29 2017 01:20 PM
SolutionI've learned that the flighting for Office.com has some cookie context, so an individual user experience could vary based on machine/browser. We are working to change this mechanism to a true user - based flight moving forward, so the experience for an individual user does not vary.
From the O365 app launcher perspective, a user outside of First Release should NOT be seeing the new experience. If you could message me directly with tenant information I am happy to investigate. This is unexpected behavior as the new launcher is only exposed to First Release.
Nov 29 2017 01:26 PM
First Release is only applicable to the O365 App Launcher exposure. So the above picture with the old / current launcher is expected as this user is not in First Release.
As far as the Office.com version in the picture, this user is part of the % of users that have been flighted to receive the new experience. All users will have the new Office.com by the end of this year, whereas the new launcher will roll out slower, and only enter a small % of production by the end of this year and finish to 100% exposure early next year.
Nov 29 2017 01:20 PM
SolutionI've learned that the flighting for Office.com has some cookie context, so an individual user experience could vary based on machine/browser. We are working to change this mechanism to a true user - based flight moving forward, so the experience for an individual user does not vary.
From the O365 app launcher perspective, a user outside of First Release should NOT be seeing the new experience. If you could message me directly with tenant information I am happy to investigate. This is unexpected behavior as the new launcher is only exposed to First Release.