Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Office 365 Enterprise vs Office 2013 Pro

Jun 15, 2015 9:08PM PDT

Hi folks, new here and had a question regarding these two suites. I'm not looking for package or pricing details and differences. What applications come with each and their accessibility are immaterial to what I am seeking. .

What I do want to know is - what are the technical differences between them? For example, we know that Word 2007 is entirely different software than Word 2010. Similarly, is Word 2013 the same software as Word in Office 365?

Is there an actual install version of 365, is it only web-based or is it nothing more than Office 2013 software with a different branding?

The reasoning behind my questions: We support a multitude of clients which use my company's software which is integrated with MS Office. Each client has their own environment. Some use Office 2010 and some use Office 2013. Some clients have said they are moving to Office 365. We want to be able to test our software on a virtual machine running the same software that the client is using to understand where any challenges may arise.

In speaking with our VM team, they've stated that, aside from licensing and available software, there is no difference between Office 2013 Pro and Office 365 Enterprise applications. They've communicated that the office applications are the same for both suites - basically telling me that Word 2013 is the same software as Word in Office 365. Is this an accurate statement?

I've frustrated myself to no end trying to search for these answers. Everywhere I have looked only speaks to the packaging and costs associated with the two.

Any insight/information anyone can provide would be greatly appreciated.

Discussion is locked

- Collapse -
Answer
Re: difference
Jun 16, 2015 2:25PM PDT

If I had to make software that integrated with different versions of Word, I'd test them on all supported versions, even if a Microsoft person told me they are identical now and still will be identical in 2020.

Do I understand correctly your company sells untested software?

Kees

- Collapse -
Re: difference
Jun 16, 2015 6:19PM PDT

Not sure how you gathered that assumption since the objective here revolves around testing.

We provided software to clients who have purchased it for Office 2010 and for Office 2013. Some clients are now wanting to upgrade to Office 365. We have communicated to them that our software is currently not certified for Office 365. To ensure that our software is compatible with 365, we would like to test our software in that environment. It was when we reached out to our VM team that we were told that Excel, Word, etc are the same versions on both 2013 and 365. Before I can argue the point with them, I need to have all the facts yet all of my searches only discuss packages and costs.

- Collapse -
Answer
Wait till your client is running a 64 Bit Office.
Jun 16, 2015 3:00PM PDT
http://superuser.com/questions/903773/ms-office-2013-64-bit-limitations

You didn't touch on the 32/64 bit issue so my guess is you are just beginning to enter the tar pit this is. Sorry but simply no, the versions are slightly different to the point your programmers and support staff better be tuned up to answer a lot of questions. I see Kees already pointed out you must test against them all.
- Collapse -
Fortunate
Jun 16, 2015 6:26PM PDT

Fortunately, at least at this time, all clients looking to upgrade are running a 32-bit OS environment.

Yes, Kees perfectly stated what I am trying to communicate to my company but they aren't budging until I can come back with proof to say THIS or THAT is what is different between the two and gives justification for the purchase of 365. Their perspective is - if they are the same thing, why pay the extra $$?

It's beyond frustrating.

- Collapse -
Here it's the opposite.
Jun 16, 2015 6:34PM PDT

All my clients are on 64 bit OSes so I can't guess if you are in some country where they are back on XP or later.

- Collapse -
(NT) Say, you write upgrade to a 32 bit OS. Are they on W98?
Jun 16, 2015 6:46PM PDT
- Collapse -
Nice catch Bob
Jun 16, 2015 7:12PM PDT

Reading about this here >
https://support.office.com/en-us/article/Office-365-system-requirements-719254C0-2671-4648-9C84-C6A3D4F3BE45

And Office 365 say's this >
Office 365 does not have an operating system requirement, except that the operating system you use must be supported by its manufacturer.

Hmm....
Sounds like XP and prior versions are out of time

Note Windows XP leaves extended support on April 8, 2014. Although Office 365 will not block users from connecting to the service from Windows XP devices after this date, you should expect the user experience to diminish over time. Users with low-memory devices running Windows XP and Internet Explorer 8 will have a substantially diminished browser experience with Office 365.

I guess nothing lasts forever
Digger

- Collapse -
Pre-32 bit OSes.
Jun 16, 2015 7:21PM PDT

Wow, the memories. It seems odd to read anyone writing they are going to upgrade to 32 bit today. I'd like to read what country this is happening in.

- Collapse -
No?
Jun 17, 2015 6:42AM PDT

Hi,

I said they are looking to upgrade to Office 365 and stated that all of the clients taking about upgrading their Office are in a 32-bit OS environment (this was in response to the question about 32-bit or 64-bit).

- Collapse -
Still pretty odd clients.
Jun 17, 2015 8:41AM PDT

Last week I took an impromptu count of the client machines and all were up to 64 bit OSes. These companies pay by the hour so all the machines were 8GB, 64 bit Windows 7 or later.

Anyhow, you don't have to reveal why 32 bit was still in use there.

And as everyone has noted, all you need to do is test before you deploy.

- Collapse -
Re: pay
Jun 17, 2015 2:44AM PDT

Since your company makes such software, I assume they are MSDN and TECHNET member, and as such have free access to the programs for development purposes.

If not, the susbscription costs for the Business version is some $100 a year. That's the cost of 2 manhours, and totally negligible for any software company. Are you really saying your boss wants to take the risk that it's not the same to save $100?
I even see offers for a 1 month free trial.

The time you spent already to find the differences costs him more than $100, not to speak of the support costs if it turns out that it is different or becomes different some moment in the next 5 years.

I'd say that anybody saying there is NO need to test in this case should prove his statement beyond doubt. That involves a few calls to Microsoft tech support.

Kees

- Collapse -
Agreed
Jun 17, 2015 6:45AM PDT

Hi Kees,

Preaching to the choir. This isn't a company policy/philosophy, this is the tech that I am dealing with and having to work through at this point and I simply want to have all of my ducks in a row before jumping over his head or getting my director involved. Common sense dictates if your client uses an AB environment then you should use an AB to test, not AC and hope for the best.