Hey there @LuDaiMSFT-0289 - Just to confirm, because it is not explicitly documented, when the documentation says to revoke the license, that means clicking the 'Revoke Licenses' button when looking at the device properties right:

But when it says to reassign the app license, what are we expected to do here?
1. Remove the existing assignments targeted to either device or user groups & reassign them?
2. Remove either the device or the user from whatever groups the exiting assignments are targeting then re-add them back?
Asking as it's not clear at all what the recommended approach is for "reassigning the app license"?

If one doesn't remove the user/device from whatever groups the exiting assignments are targeting, and you click 'Revoke Licenses', does it actually do something?

Good Morning @XuDongPeng-MSFT

Thanks again for your earlier reply and follow up. I can confirm that this did indeed fix the issue so thank you for that! However after making the policy change the issue persisted until I restarted Edge. Should these types of changes apply while Edge is running? Is that normal?

On that page many of the settings support "Dynamic Policy Refresh" which to me suggests that Edge will 'see' policy changes like that and apply & enforce them while Edge it's running. I could be very wrong here but I have not found any good documentation on Dynamic Policy Refresh. Can you point me to some documentation that would further explain what Dynamic Policy Refresh is, how it works etc.?

Otherwise thanks again for sorting out the original issue!

Thanks again for following up! I did test this but wasn't seeing a positive change. I will retry again within the next 24 hours and post back.

Hi @ChristyZhang-MSFT - thank you for taking the time to reply.

To answer your questions:

• Account type is Exchange On-Prem & configuration is automatic. (ZeroConfig/AutoDiscover)
  

• All machines are identical: built with the same image, same configuration, same set of add-ins, they're all in the same OU with the same set of GPO's applied.
  

• The Outlook data file is set in the mail profile properties, and exists at the file system level.

What really makes his challenging is that

• It does not happen all the time; seemingly random
  

• It is not user account specific: It happens to brand new user accounts and existing ones
  

• Creating a new mail profile (or a new user profile) resolves the issue.

I still have access to a machine that is in the 'broken' state if there's anything else you'd like for me to try.

Thanks for the reply @ChristyZhang-MSFT !

I can confirm unequivocally that the image and the installation of the Office suite, which was configured using the Office 365 Customization Tool, is sound. This is not something we can reliably reproduce at will indicating it's not the image or the software stack since that's all static. It is not specific to any one user or type of account - it seems to strike randomly. The fact that the fix is to replace the profile seems to really point to an initial profile creation issue.

I feel we're approaching that point of diminishing returns. Happy to be wrong on this but tearing a known good image apart, repairing office, uninstalling/reinstalling Office etc. are not insignificant steps. Combine that with the near impossibility to reproduce or even predict when this issue will occur, going to greater lengths will likely not yield any appreciable results.

Are there no super verbose debug logging features we could enable that would generate a log that would significantly narrow the troubleshooting scope? If not, lets mark this as closed-unresolved. If this becomes a burden we'll open a support case.

Thanks again!

Hey there @ChristyZhang-MSFT - Happy Friday to you!

I understand completely that log analysis via the forums is not supported. Fortunately that is not my objective :)

I am trying to understand what super verbose debug logging options are available that will allow us to generate some logs for further analysis when I eventually open a support case. No doubt the logs will help push that support ticket along. Does that make sense?