Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Hi @Rose
What usually triggers this is a student signing in to the Office 2019 apps with their school account. That account carries a Microsoft 365 license, and Office can detect it and switch the install over. Signing in on the web shouldn't do it on its own, but Office can pick up that account from Windows or the browser session and prompt for it.
The way to prevent it is to stop school/work accounts from signing in to the Office desktop apps. There's a policy for exactly that:
- On one test PC, open the Group Policy Editor with the Office ADMX templates installed and go to User Configuration > Administrative Templates > Microsoft Office 2016 > Miscellaneous. (Office 2019 uses the 2016 templates.)
- Open Block signing into Office, set it to Enabled, and choose Microsoft account only. That still allows a personal Microsoft account (which retail Office 2019 may need for activation) but blocks organization accounts like the school ones.
- If you'd rather set it directly, it's the
SignInOptionsDWORD underHKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\SignIn. Value1= Microsoft account only,4= no sign-in at all. (The reference below was written for Office 2013, but the same setting applies under the 16.0 key.) - Since it's a per-user setting and the PCs are shared, apply it to every user profile, for example through local Group Policy for all users or a logon script.
- Test with a student account for a few days before rolling it out everywhere.
The students can still use their school Microsoft 365 in the browser. They just can't attach it to the installed Office apps.
Is Office 2019 on these PCs a retail version tied to a Microsoft account, or a volume license version?
If this resolved your issue, please consider accepting it as the answer. If Office still switches after the policy is applied, let me know and I'll be happy to keep helping.
Reference: