Office 2016 on Windows 7, 10 or Windows 2012 and 2016 – No Internet connection to sign-in users to Office 365

We had a strange issue on our hosted environment on Azure with Windows 7, 10, Windows 2012 R2 and Windows 2016 RDS / Citrix servers. Users could not sign in to Office Pro with their Office 365 user credentials, to a batch of newly installed servers. They received the message when they start any of the Office applications (in the screenshots below I use Word):

We are unable to connect right now. Please check your network and try again later.


We are unable to connect right now - Office 2016The next message users receive is:

UNLICENSED PRODUCT Most features are turned off because a shared computer license isn’t available.

Unlicensed product - Office 2016

As the message states: most features are turned off 🙂

Shared Computer Licensing on RDS

We have installed Office 2016 with a Shared Computer License model as stated by Microsoft, to enable Office for multiple users simultaneously.

Our configuration.xml file does what it supposed to do, install Office silently, US and NL languages enabled and of course Shared licensing enabled:


  <Add OfficeClientEdition="32" Channel="Monthly">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
      <Language ID="nl-nl" />	
    <Product ID="VisioProRetail">
      <Language ID="en-us" />
      <Language ID="nl-nl" />	

  <Display Level="None" AcceptEULA="True" /> 
  <Property Name="SharedComputerLicensing" Value="1" />


So this is not really spectacular and after installation of Office I have confirmed we have the Shared Computer Licensing activated (you can check this via Word – File – Account – About Word):

Shared Computer Activation Office 2016

The solution

Well, in a nutshell, I have tried a lot… and found an issue under Network and Sharing center, I saw the message The service to detect this status is disabled.

Network and Sharing center the service to detect this status is disabled

When clicking the More information… you receive the following message: Do you want to turn on Network List Service. Well yes, turn it on, please…

Do you want to turn on Network List Service

So pressing the Turn this on button I received the following error message: The dependency service or group failed to start.

The dependency service or group failed to start.

Ok, let’s start the Services MMC (WindowsKey + R, services.msc and OK).

Services overview with Network List Service selected

Let’s open the Network List Service and look at the Depedencies. We see two dependent services if you look at the above screenshot you can see that the Network Location Awareness service is disabled! Now open the Network Location Awareness service and set the startup properties to Automatic. After pressing OK, start the Network List Service.

Dependencies of the Network List Service

Now start Word and you can successfully connect to Office 365!

That’s all for today.


Daniel Nikolic

15 replies
  1. Vikalp
    Vikalp says:

    Many thanks Daniel Nikolic. It was very helpful. Have been struggling for several weeks with this issue but you blog did it all.

  2. Miguel
    Miguel says:

    I can’t “like” this post enough, wow. So many suggestions out there on the internet that are completely useless. Thank you for your hard work and for sharing your solution… OneNote works like a charm now.

  3. Tim
    Tim says:

    Thank you, Daniel! This helped me too, and I’m very grateful to you for it. From my research while trying to solve this problem, it looks to me like you are the only one who posted the solution.

    For anyone who’s curious, I have Office 2016 in Windows 7.

  4. Steven Halbert
    Steven Halbert says:

    For some reason I very rarely post on these sorts of things, but this problem has been plaguing me for several days . . . but I’ve been limping along. Today I started trying to resolve in earnest. My entire Office Suite was then made “unlicensed.” Your solution worked for me, and I am very grateful. Back up and running now! Thanks!

  5. Seema
    Seema says:

    Many Thanks Daniel.
    I was struggling quite hard to fix this issue and Finally your post brought new year smile 🙂


Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *