Rebrand Sees Microsoft Office Become Microsoft 365

Microsoft Office 365 rebranding
(Image credit: Microsoft)

Microsoft is preparing to retire or at least deemphasize its decades old Office brand in favor of Microsoft 365 branded cloud productivity tools. Users should expect to see the changes permeate throughout the Microsoft cloud ecosystem in the next few weeks. Meanwhile, PC stalwarts using offline standalone Office suites and applications will probably not notice any difference.

(Image credit: Microsoft)
Latest Videos FromTom's Hardware
Mark Tyson
News Editor

Mark Tyson is a news editor at Tom's Hardware. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.

  • USAFRet
    Rebranded, still works the same.
    Buttons in different places.
    Meh....


    But DO verify your old Office vs new Office and 32bit vs 64bit.

    We upgraded to O365 64bit at work.
    Our previous Office 2016/2013 was 32bit.
    Some functions within MS Access broke, and had to be "fixed".
    Reply
  • USAFRet said:
    Rebranded, still works the same.
    Buttons in different places.
    Meh....


    But DO verify your old Office vs new Office and 32bit vs 64bit.

    We upgraded to O365 64bit at work.
    Our previous Office 2016/2013 was 32bit.
    Some functions within MS Access broke, and had to be "fixed".
    It's not just Access. Excel is a cause of incompatibility between 32-bit and 64-bit. If using 64-bit Excel and you use any of the extended numeric types (64-bit Long Int for example) that spreadsheet will not in any way be loadable by 32-bit Excel.
    Reply
  • Eximo
    That has been a problem for as long as Office 64-bit has been around. You would be surprised how many people will ask for Office 64-bit and then complain when none of their 32-bit plug-ins work. I had one guy who insisted on Office 64 so he could pull down large datasets from a database, but then needed a separate computer running 32-bit to deal with the output.

    I had to implicitly ask for Office 32-bit to work with an old Access based application. Hasn't burned me yet.
    Reply
  • USAFRet
    Yes, Excel as well.

    I'm in the process of fixing 2 Access applications where this failed. 1 just compelted testing after the rebuild, and the other is in progress.
    The fix was rather easy...a couple lines of code in each api or dll call it failed.

    Thousands of offices have small homegrown Access or Excel applications where this fails.

    Interesting, or not so interestingly, none of the Access/Excel things that "I've" built have failed.
    I wonder why...lol
    Reply
  • KyaraM
    Eximo said:
    That has been a problem for as long as Office 64-bit has been around. You would be surprised how many people will ask for Office 64-bit and then complain when none of their 32-bit plug-ins work. I had one guy who insisted on Office 64 so he could pull down large datasets from a database, but then needed a separate computer running 32-bit to deal with the output.

    I had to implicitly ask for Office 32-bit to work with an old Access based application. Hasn't burned me yet.
    I had to deal with that bs at work last year or so... so annoying. And we didn't even switch to 365 yet -.-
    Reply
  • digitalgriffin
    I experienced the same problems as you guys. We were calling specific 32 bit functions in vba for excel. I had to install 32 bit office to get the vba code to run. (Extracted excel formulations written by engineers and the vba turned them into C++ code)
    Reply