If you're running the Confluence 6.13 Enterprise release, a fix for this issue is now available in Confluence 6.13.6, which you can find in the Download Archives

An update for this issue is available to Server and Data Center customers in Confluence 6.15.6.
Upgrade now or check out the Release Notes to see what other issues are resolved.

We've had to withdraw 6.15.5, and will release 6.15.6 soon. We'll update this issue once the new version is available. You can find out more about the related issue here: CONFSERVER-58490

I also noticed that when the Office Connector add-on is disabled, the Import Word Document option is no longer available on pages.

I have recommended this option to my users for years, as it allows users to import requirements into a confluence page.

Oftentimes PMs that send me a word document with the 'updated requirements' without telling whet the updates are. Using Track Changes in word is nearly impossible when there are many changes.

IMO Confluence Page history is much more usable in this instance - as you can compare page history.

We would like to see the previous "Edit" link back. This is impacting a large audience which is in thousands. We cannot afford to let them know that they will need to download the app to their local machines.

Our customers are not happy with it.

Can you please bring it back?

Companion App has increased our workload and confusion. As with other users, there is also the problem of users being able to download an exe locally. Previously our editors selected Edit in Office for multiple Excel Spreadsheets (in this case, Rosters for each state), made their changes, and saved. They could keep the file open and continue saving them throughout the day.
Now, editor can only open and edit one file at a time, save, upload, close, repeat. They are spending the whole day opening, saving, uploading and closing files. The steps for each update have doubled, and now they have to do it one at a time.
Also, I can't seem to get Companion App working with IE (in a download loop) but it works with Chrome, but we are forced to use IE. It's counter-intuitive, has made our work extremely inefficient and now we can't access previous versions of the file. So far Companion App has made our lives miserable. Sure, some people don't like change, and it can get a bit of getting used to, but downgrading functionality is not a change.

Remus, the trouble with rolling back is that the Tomcat embedded in earlier versions is deprecated, would be a security concern for most of us.

Actually, this is also a problem with recent Atlassian app releases, given how critical CVEs have aleady rendered risky or obsolete Tomcat versions that are now shipping - 8.5.32 in Jira 7.13.1, 9.0.12 in Confluence 6.15.2 - but there are not nearly as many vulnerabilities in these recent Tomcat versions as in older versions.

One could independently upgrade Tomcat with old or new app releases, but Atlassian did not test against versions of Tomcat not shipped in their products, won't support such configurations, and most organizations are not in a position to test all use cases.

We are jumping through many organizational hoops to hopefully make the Companion self-installable by some of our 10,000+ end users across many teams. We cannot realistically get it packaged into standard desktop images, nor install it for users, nor ask them to because desktop admin rights are a rarity here. Beyond getting this app authorized by company authorities, put into channels, and made available to some or all clients, we also have to modify proxy controls to allow it to talk to multiple instances of Confluence.

Anything that establishes a more traditional client/server dependency becomes something between a hassle and a nightmare for large organizations in which controls like these are managed by different groups, and in which the Companion will never be made part of the standard desktop config. It is hard enough to keep all the in-app features compatible with PAC-restricted Internet Explorer and Edge clients. Use of Chrome can solve some problems, but most of our users won't be authorized to use Chrome.

So yes, once again, this was not a welcome change.

Same here, very disappointed by the terrible architecture decision that Atlassian made. We are seriously considering a rollback to a version (6.10.x) that is Companion-free until Atlassian shows interest in addressing this issue properly.

We strongly recommend that the Office Connector is put back in work or at least let users to choose between  Companion App and Office Connector. In order to get more and more users in our organization to use Confluence as the primary collaboration platform/tool we need to offer a seamless integration between Confluence pages and Office documents. This is  is more or less bread and butter functionality for us and was working well before the introduction of the Companion App. Our operations can not get Applocker to work with Companion App on the Windows clients.