Outlook client no longer showing "Coming Soon" or the "Use Tighter Spacing" buttons

Anonymous
2019-07-11T13:05:20+00:00

Split from this thread.

Hello,

I have the same problem since a few weeks.

The checkbox "coming soon" has disappeared on my three PC which were connected to my Office 365 account.

And the "Tighter Spacing" has also disappeared.

For all after a Microsoft Office update of the Office Insider channel.

The display of the Outlook window returned to the old Office 2016 theme.

I think it's an update who accidently delete the "coming soon" function (and I don't know why the "Tighter Spacing" is reserved to the "Coming soon" function ...).

Microsoft must restore this fonctionnality to get back the "Tighter Spacing".

I have tried to update manually Office but the last updates have not reactivated the "Coming Soon" ...

Microsoft 365 Insider | Outlook | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

12 answers

Sort by: Oldest
  1. Anonymous
    2019-09-16T16:52:01+00:00

    Where did this leave off?  I have the same problem starting yesterday.  Got the new simplified ribbon and the Use Tighter Spacing option, got used to it and like it, and now it seems to be gone.   What's even stranger is that it still shows in the Customize the Ribbon section in Options.  But it doesn't show up in the Ribbon, which is now behaving as it was before, prior to these new features being deployed.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-09-17T11:45:33+00:00

    So, I had to park this, as I was travelling a lot for work, and barely using the PC that had this issue.

    I have since returned, and still had the problem. However, I noticed on my account details under Excel that it had my wrong Office365 subscription (it was an old one that I had more than 2 years ago upgraded!).

    I upgraded the sub, and so far since, it has all worked as supposed to. 

    So that has worked for me - might be worth checking (if you are on Office365), but I suspect this won't be the issues for many people, and that there is therefore still a problem somewhere that ideally MS needs to take a look at!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments