Microsoft Office 365 Compatability

Follow

Created:
Updated:

NetDocuments Support gets a lot of inquiries on compatibility between the NetDocuments integrations and Microsoft's subscription-based Office 365. The legacy Application Integrations have been tested and are compatible with a local 32-bit version of either Office 2010 or 2013. ndOffice is compatible with 32-bit Office 2010, and both 32-bit and 64-bit Office 2013 and 2016. 

Update: On June 15, 2016, NetDocuments announced that it will soon allow users to edit documents online using Microsoft's Office 365 web apps. The feature will be released pending Microsoft's testing and approval. Learn more

Back to Top

Was this article helpful?
1 out of 1 found this helpful

Comments

  • Avatar

    We are starting to look at Office 365 and would find such an integration extremely useful.  Does Netdocuments have any plans for creating integrations for Office 365 Web apps?  Of course, if the answer is yes, does your crystal ball reveal any kind of time table for such a development? Is the current lack of integration market driven or driven by technical restraints?

  • Avatar

    We have a strong interest in such functionality as well, and I would like to echo the commenter's questions above.  Our "firm" is a law school clinic, and given the consistent turnover in students and their varied computing platforms and capacities, we utilize Office 365 for our email.  The lack of ND/O365 functionality has forced some workflow workarounds that are not particularly satisfying or efficient.

  • Avatar

    I would also like to state that NetDocs integration with Office 365 would be a great benefit.  We are evaluating providing Office 365 for our attorneys for when they travel but without integration it makes things much more difficult. 

  • Avatar

    It is time to upgrade all of our computers and we would prefer to simply subscribe to Office 365, but since ND dosen't integrate, we will have to buy separate Office software and licenses for all the computers. SAAS is the future and hopefully Office 365 and ND will be able to seamlessly integrate in the future. To be truly mobile and efficient, we need integration. On another note, thank you for your continued efforts to continually improve ND's features. We can't imagine being without ND.

  • Avatar

    I suggest you subscribe to Office 365 whether you use the web based version or not.  It comes with the right to install full local versions of Office on your desktops, and is often a more cost effective way of purchasing licenses.  Especially if you are considering the hosted email portion of Office 365, it is usually less expensive to just get the full package and not use the other hosted applications, but install them locally.  My understanding is the local applications with Office 365 are identical to those that you would purchase outside of Office 365.  And, you could easily migrate at no cost at such time NetDocuments becomes more integrated with Office 365.

  • Avatar

    I will jump in here and add that we currently have the ability to edit and create documents using the MS web apps. We recognize that this does not provide a full "integration" with Office 365 as users might be using currently, but it provides a simple, seamless way to edit documents without a local application. 

    http://help.netdocuments.com/online-editor/

  • Avatar

    Pete and Russell - Thank you for the response and information. If Office 365 does come with full local versions of Office, that sounds like a great solution.

  • Avatar

    There is an important restriction on the ability to use the online editors (web apps) with Netdocuments. Microsoft has created a mess with Microsoft accounts and Organizational accounts. For those of us that are syncing AD into Office 365, it does not appear that we can log in to access the online apps. I don't know if there is a way for Netdocs to expose the additional prompt for Organizational Login that Microsoft is now using on many of it's sites.

  • Avatar

    How about if you were to use ADFS or one of the SAML federated identity providers that ND supports? 

  • Avatar

    David,

    If I understand what you are referring to, you are saying Microsoft has two different types of accounts, that are described here: http://www.microsoft.com/en-us/account/faq.aspx. The Microsoft Accounts are currently supported (or integrated) with our Online Editor, but the Organization Accounts (Office 365) is not currently integrated. We would highly suggest you post a feature request on our IdeaBank to allow the Online Editor to integrate with Office 365 accounts in addition to Microsoft Accounts. I am certain other NetDocuments customers may be interested in such an integration. 

  • Avatar

    This is correct. for example, I have a Microsoft ID that that is tied to my work email address. Now that we have converted to Office365, I have an "Organizational" account that is the same email address, but authenticates differently within Microsoft. These are 2 separate accounts.

  • Avatar
  • Avatar

    Another useful thing to know is that Office 365 can also simply be the one-click method of installing Office 2013 on a local PC. That, of course, is fully supported with all of our integrations.

  • Avatar

    I understand that, but that isn't the subject of this discussion? :-)

  • Avatar

    This thread is confusing me. It says that office 365 is not supported, yet some of the comments make it sound like it is supported. Specifically, I think it means that using the web apps is not supported with the integrations, but can you still install ndoffice on the computers that have downloaded and installed office 365 locally? We do not have office 365, but I was led to believe that it also installs to a local computer and you do not have to use the web version, and if that is true then can the ndoffice integration still be installed or would we have to purchase the more expense traditional office 2013 product? Microsoft seems to report that there is no difference between 365 and 2013 other than how you pay for it.

  • Avatar

    365 is both the cloud deployment as well as one click installer for desktop apps. NdOffice supports 365 licensed desktop installs.

  • Avatar

    Then why does the ndoffice requirements say it only supports 2010 and 2013, which has been making me think it did not support an office 365 subscription at all. It would make more sense for my firm to subscribe to office 365 than pay a huge one-time purchase for 2013.

  • Avatar

    Bart is right. This thread is originally about the Office 365 web apps, not the local version of Office 2013. (The local version of Office 365 is one in the same as the local version of Office 2013 - its just a matter of the purchase method). For those here looking to use the online Office 365 web apps, they should vote on the idea in the IdeaBank. 

  • Avatar

    Thanks...I suggest you update the requirements of all the integrations to say they only support local installs of 2010, 2013, or 365, so it is clear.

  • Avatar

    I agree that the subject is confusing. When I purchased an Office 365 license I clicked my way to five instantiations of ndOffice running in 2013. The week before I thought it was only the cloud apps.

    Here's a quote from the ms description:"Office 365" refers to subscription plans that include access to Office applications plus other productivity services that are enabled over the Internet (cloud services), such as Skype for Business web conferencing and Exchange Online hosted email for business, and additional online storage with OneDrive and ...".

    I think that this blurring of the distinction between a product called Office 365 and a deployment method for desktop apps might be important to for Office's future strategy but is here seen to be creating some real confusion.

    Hard to explain quickly.

  • Avatar

    Yes, the concept of Office 365 was very confusing to me at first.  Really "Office 365" is just the subscription.  Once you have a subscription, you can then download Office software locally (2010 or 2013 for example).  We fully Support Office 2010 and 2013 so if you have one of these versions of Office installed locally (whether because you have a 365 subscription or you just bought a license for the software), it is supported by ND.  Office 365 also includes some web apps, we currently do not have any integration with these web apps.  

  • Avatar

    Thanks. This clears it up, but I do recommend you make it more clear in the system requirements sections for the Office and Outlook integrations.

    Now I just need to find out from Microsoft what will happen when Office 2016 comes out this fall if you have a 365 subscription will you be forced to upgrade the local install or if it can be kept at 2013 until netdocs supports office 2016.

  • Avatar

    I'd be surprised if MS can force an update of the 2013 desktop product. The cloud based editor might be another matter.

  • Avatar

    I’m pleased to say that NetDocuments has announced its new integration with Microsoft Office 365 web apps! Learn more here: https://support.netdocuments.com/hc/en-us/articles/209307886-Microsoft-Office-365-for-NetDocuments

  • Avatar

    Wow . . . I was quite confused but think I may have found my way through the jungle. I am installing a new desktop today and was on track to thinking I needed to migrate my old copy of Office 2013 in order to be able to use ndOffice and EMS Profiler. SO TO CONFIRM . . If I subscribe to Office 365, business and fully download the apps to my desktop, then it will be fully compatible with ndOffice and EMS Profiler? Correct?

  • Avatar

    Denis, that is correct. If you have an Office 365 subscription, and you download the local apps, today you will get Office version 2016, which is compatible with ndOffice and Profiler.

  • Avatar

    Russell - Just another couple of quick follow up questions: I had been told that at some point that if subscribed to Office 365, there was a auto-update switch turned on within Office that needed to be turned off possibly to avoid an automatic update that might result in a version update that could result to a new version that might not be compatible with whatever Office plug-ins a user might be dependent on (such as the many ND plug-ins). Have you found that to be the case? SECONDLY - doe I need to be used 32-bit or 64-bit version of Office 2016?

  • Avatar

    Denis, I'm not sure about the auto update switch for Office. I guess in theory it would be good to disable Office auto updates to avoid the potential for this happening, but I imagine it would be a rare occurrence that Microsoft would force an update to Office before ndOffice is able to be supported in it. Although, I believe the default is to prompt for updates, and not force them. I have a PC at home that has Office 2013 (through O365) installed on it, and it asked me if I wanted to upgrade to Office 2016, but didn't force me to. I never changed any defaults.

    ndOffice 1.8+ is supported in both 32-bit and 64-bit Office 2016.

  • Avatar

    I know of no scenario where a local copy of Office would be replaced with a web version.

Have more questions? Submit a request
Powered by Zendesk