#Office key free work 2016 365 product activation key#

Upon signing in to the Office app with the Microsoft account of my choice, the license seems to be active and properly tied to my Microsoft account. Once I was totally signed out and inside of a local user account, the preinstalled Office apps recognized that a valid license was available. The Office key seems to be tied to the computer itself but for some reason I was not able to see it until I was signed out of all Microsoft accounts. I signed in to my primary Microsoft account (not the one supposedly tied to the email I used at the time of purchase) and the license now seems to be properly tied to my account. Upon signing into this local user account (with no ties to any Microsoft account), the preinstalled Office apps notified me that a license for Office 2019 was available and could be activated by signing into a Microsoft account. The Dell tech support rep had an excellent idea to create a local account not tied to any Microsoft account. Either way, this did not fix the problem and the apps still showed no sign of an activation key. A complication to this is that I actually already had a Microsoft account under that email. I signed out of my primary Microsoft account and into the account corresponding to the email I used during the purchase. Any Dell rep reading this, please pass this feedback along to avoid confusion in the future. There seems to be some conflicting information about how this process is handled. The documentation presented to me at the time of order suggested that the key would be emailed to me.

This is a very poor policy and should be changed if true.

#Office key free work 2016 365 product activation key#

A Dell rep informed me that Dell issues the Office activation key to a Microsoft account based on the email address that I used to place the order. I was prompted to begin an Office 365 trial. When signing in to any of the preinstalled Office apps with my Microsoft account, no evidence of a valid key was presented. I was able to resolve the issue though I've been unable to confirm exactly why it was fixed: