Open Adobe PDF in client application
Office 365 / SharePoint online needs to support opening PDF documents in SharePoint directly to client application (Adobe Acrobat Pro/DC).
As of this request, technical support has stated the only way to open PDF files in Acrobat is to download/save them.
SharePoint On Premise has supported this feature for some time.
Adobe PDF files are as common and Microsoft Office Suite documents and must be editable directly to/from SharePoint Online without the need to down/save edit, and upload which adds user overhead and lowers productivity.
Thank you everyone for your feedback on this item. We recognize this is a valuable feature and are looking at ways we can address it. We do not have a timeline to share at this point.
Four years on and still no solution - come on Microsoft, this would be much more useful than all the 'major change updates' you keep putting out!
I vote for this
+1 on this. Both for desktop Adobe App and for BlueBeam PDF App.
D. Jäger commented
Conclusion after more than 4 years: Microsoft is not interested in the concerns of users.
Even if I could, I would never allow myself to do it to my customers.
Make Microsoft great again ... but they don't listen.
Tomasz Szałaj commented
Microsoft - you are so arogant with your "no timeline to share at this point". It was easy to cut your competition and it's soo hard to step back when your customers ask you for better solution from your competitor. Shame on you.
i vote for this
Crazy that this hasn't been fixed. We are currently going through the process of considering whether to move on to sharepoint, but as a company that relies heavily on PDF documents, being able to use the functionality of Acrobat, this could tip the balance away from SP
I cannot believe this problem has not been fixed yet.
As an admin, if I choose to configure my sites to allow a document to be opened in its associated client application, then when a user clicks on that PDF, I expect it to open in Adobe Reader. There's no warning on that configuration setting in SharePoint that says "ha ha, don't bother choosing this - it doesn't work."
One of the biggest problems I find with this feature being broken is that the only way for the user to be able to open these PDFs in Adobe Reader is for the user to download the file. This completely negates the whole purpose of a shared library where the only true copy of a file resides in the SharePoint library. Now all of my users will have that file downloaded on their workstations, and if I need to update that file in the library, they most likely won't know about it and will continue to use the outdated copy on their workstation. This is just plain stupid inefficient document management.
George Mack commented
PowerPhotos 2017 Mac app to organize photos on your Mac, PowerPhotos allows you to break your photos up among multiple Photos libraries, rather than having to store all of your photos in one giant library. You can easily switch between libraries, or just browse the photos in your libraries directly from PowerPhotos, without having to open each library in Photos. PowerPhotos also supports searching across all your libraries at once to help track down a particular photo.
These filter stages are non-linear saturation incorporated that are used to evaluate the warmth and drive off an analogue filter. These controls can be turned up to a level that makes it possible for the filters to scream. These filters sound warm,rock-solid and roll. It’s modulation options let you do is sculpture the sound the way you like. It’s 2ADSR envelopes, and it’s 2 LFOS can be used to modulate the whole set of different parameters. Next, it can handle two extra amplitude envelopes, keyboard track, velocity all modulation wheel as a source of modulation.
Have there been any updates? It's been 7mo's since you posted and nothing
Lance Aughey commented
@will - does doing so allow for your users to sign and save the document back to the same or another location within SharePoint or are you simply providing a PDF "template" in which to simplify your process(es)?
I may be way (totally) off base with this, but the desirement of those commenting here are wanting (a) to open PDF in native client and (b) have a means in which to save the edits back to the original location. Maybe the title of this recommendation needs to be updated to reflect both?
All I know is this suggestion was posted over 4 years ago and, 49 months later, we get a glimmer of hope that someone at Microsoft is paying attention to UserVoice. What's irritating, to say the least, is some suggestions with few votes get implemented in short order, yet those with much higher tallies get ignored (for 49 months).
Thought i would share my workaround, we have a modern library for forms in which we need to launch directly to adobe client for fill and sign capability. If i use the document library web part instead of browsing the document library i can launch directly to adobe reader client. Just need to set "Open files in client" in SharePoint settings and set chrome settings to "download files instead of opening them in the browser".
I usually try and avoid document library web parts, but this is the only way i could get this to work :(
Still not implemented !?
So we must choose between "Classic Experience" disabling OneDrive sync and "Modern Experience" disabling opening PDF in Client application.
Please MS, refocus on core business features. Stop convoluting workflow by forcing web use. What's the point? My user don't want to view word of PDf on their tablets and phone, they want to edit and sign INTO the client applications, NOT the brower. How can we sign or edit PDF with a simple workflow?
This back and forth of functionality is frustrating to say the least.
Erik Gunnheden commented
Please! Please! Please!
Hans Persson commented
Please fix this!
Lance Aughey commented
@bubba - I'm curious (and extremely interested), other than the Adobe Cloud, what other content management systems are out there that are KNOWN to work hand-in-hand with Adobe and all of its "pieces" (workflows, sign, etc.)?
We use Adobe and Bluebeam for PDF handlers. Adobe has always been problematic, but there is one known workaround that continues to function (it's comical that Microsoft wants everyone to stop using IE, but it's needed for certain things, like this, to work). Bluebeam has been rock solid, however it uses the same methods (token) as Adobe in terms of authenticating to SharePoint.
As I stated a few comments back, given the lack of effort on Microsoft's part, I'm inclined to believe this has less to do with Microsoft and more to do with Adobe.
Remember how long it took Microsoft to include PDF creation in Office? All that litigation with seemingly no end in site and then...BAM! Licensing and relationships...good and bad.
ABSOLUTLEY REDICULOUS !!!!!!!!!!!!@!@!@!@!@!!!!! CORRECT THIS ISSUE NOW!!!
It has been nearly 5 years since this NEED was shared. 5 MS Ignite conferences have been held, many new products developed.
Microsoft, your users are asking for something that should be fairly simple to implement. Allow PDF documents to open in the desktop app. You are doing this with Word documents, Excel documents, PowerPoint documents.... why not add this same functionality that you already have developed for your Office products and modify it slightly to allow PDFs to open in the default client app for PDFs? Your enterprise customers have tens of thousands of PDF documents that they are working with.
As a SharePoint professional, I have had business units asking me for SharePoint alternatives to work with PDFs. It is so important to our business units, that they are considering other content management solutions. BU's are getting to the point where they are willing to abandon SharePoint (even though it is already paid for as part of the E5 licenses) and purchase a different system that works well with PDFs.
If someone at Microsoft could add this to the roadmap and give us a potential release date, say end of Q2 2021... I think I can keep our BU's on track... but if all you can give us in 5 years is "Thinking about it", I'm not sure if BU's will continue to wait.
Etienne Groulx commented
SharePoint documents cannot be opened in Acrobat, Unfortunately, it is the reality and it needs to be adressed and corrected rfn. Thanks