FSLogix and Microsoft 365 Apps for Enterprise Activation issue remediation

Last week I faced an issue at the client site while getting a Microsoft 365 Apps for Enterprise Activation notification after the user login.

Table of contents

  1. Issue
  2. Video & Download
  3. Conclusion

The user started a random Office app like Word and got represented by the sign-in screen:

In the menu bar in the center top we can see Word [Non-Commercial Use] [Unlicensed Product]

Office has worked for the last couple of months perfectly on WVD, so I had to investigate the issue and obviously, the first thing I’ve tried, is to Sign in again to see the application behavior. Finally, the screen was flickering a few times, but the error message persists and Office was simply unusable for all users on the system.

So first of all I started to analyze the base parameters like:

  • FSLogix version used (it was 2.9.7349.30108 at the time of doc creation)
  • Office version used (shown in the screenshot below)
  • Office update channel in use (shown in the screenshot below)
  • Roaming license token for Microsoft Apps in place

I quickly realized that the client updated the image and changed the Update Channel from Semi-Annual channel to Current Channel.

This is in general not a big issue, but you need to make sure that Office is always in it’s latest version, which was not the case in this scenario!

Tip 1: If you need to choose Current Channel, make sure Office is in it’s latest version!

But this didn’t solve the problem at all, it just brought us to the latest version. So the next thing to check is, what happened with our existing License Token for Microsoft Apps for Enterprise.

Usually, when using FSLogix Profile and Office365 Container, we have the possibility and include the Office Activation Data inside the Office365 Container. This can be defined easily through Group Policies.

If thats the case for you, you’ll find the activation token as if you’re working with local profiles underneath the following location:


And it turned out that no files were present here! This was our starting point. Next, we need to ensure, that all user-related information is removed from the registry and that the Work or School Account settings are reset for the user to be able to renew the activation token.

For that reason, I’ve created a tool, which performs all of these tasks for you automatically and it can be used for one-shot remediation.

Please find the video and the tool download afterwards:

The tool is free usable and can be downloaded from my GitHub repository:

wvdlogix/M365TroubleshooterWVD: Repository for the M365Troubleshooter for WVD (github.com)

Just download the M365Troubleshooter.exe and you’re good to go!


Finally, you can start one of your office apps again and you just need to click on accept license agreement, like it’s your first time starting office. Outlook data and configuration settings won’t be lost!

By checking back the folder, that holds our licensing tokens you can see that two text files have been successfully been created, like it should be:

And this resolves the issue, even on a long term! We have tested the solution while simulating the following months and it was working pretty fine.

(Visited 135 times, 1 visits today)


  1. Pingback: WVD news of the week - Johan Vanneuville

  2. Travis Lamming August 16, 2021 at 2:13 pm

    This really helped me out. Thank you! This AVD environment where we had the issue was before microsoft didnt allow the WVD pool to be joined to AAD as a managed computer when you first activated office 365, so we would run into activation issues all of the time.


Leave A Comment

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