Long story short we had a user who needed an Office reinstallation due to crashes/freezes/etc.
Silly me was working late and used the Office 365 installer from the web portal instead of my MDT script so it installed that shiny new Office 2016 that doesn't work with any of our applications yet.
Uninstalled, rebooted, reinstalled 2013 with my regular old MDT script using our local binaries and now it not only insists that Office is no longer activated, but clicking "Activate now" gives the following error as if I had no network connection:
You get the same thing if you click "Change Account" to log in with another MS account, it doesn't let you and throws this error.
I'm assuming there's some registry tomfoolery due to 2016 being installed, has anyone seen this before? I really don't want to play games with yet another uninstall reinstall...