Check Microsoft Office Version Using Terminal Key
Check Microsoft Office Version Using Terminal Commands

Apr 02, 2021 If you're using a Microsoft 365 product, see View Microsoft 365 licenses and services with PowerShell. Follow the steps to find your license type and other details about your version of Office. Office 2019 and Office 2016 Press Windows logo key+X on your keyboard to open the quick action menu. The steps to start using WPS Office include downloading the package from the website, installing it, & finally starting to use it. Let’s find out how to download & install WPS office on Ubuntu via command terminal. Note: the steps of installing WPS office on Ubuntu is same for Ubuntu 18.04 LTS, 17.10, 16.04 LTS, 14.04. In the File or Office menu that opens, look for an entry called Account. Click or tap on it. If you have Microsoft Office 2019, 2016, or Office 365, you can see what edition you use on the right side of the Account page, just like in the image below. The Product version in Microsoft Office Professional Plus 2019. MS Office Professional Plus (2016, for example) is a traditional version of Microsoft Office that is licensed on a perpetual basis (a device-based model) but is updated until the support period ends. Office 365 uses a subscription licensing method (a user-based model) and is updated until you pay for subscription.

-->

This article shows how to assign Microsoft 365 Apps licenses to users and how to activate installations of Microsoft 365 Apps.

Check Microsoft Office Version Using Terminal Key

Note

The information in this article also applies to Project Online Desktop Client and Visio Online Plan 2 (previously named Visio Pro for Office 365), which are licensed separately from Microsoft 365 Apps.

Before deploying Microsoft 365 Apps to users in your organization, you must first assign licenses to those users. Each license allows a user to install Microsoft 365 Apps on up to five desktops, five tablets, and five mobile devices. Each installation is activated and kept activated automatically by cloud-based services associated with Office 365 (or Microsoft 365). This automatic activation means you don’t have to keep track of product keys and you don’t have to figure out how to use other activation methods such as Key Management Service (KMS) or Multiple Activation Key (MAK). All you have to do is purchase enough licenses, keep your Office 365 (or Microsoft 365) subscription current, and make sure your users can connect to the Office Licensing Service via the internet at least once every 30 days. When single sign-on is enabled, Microsoft 365 Apps detects the user’s credentials and is activated automatically.

If you remove a user's license (for example, if the user leaves your organization), any installations of Microsoft 365 Apps that the user had go into reduced functionality mode. The Office Licensing Service, a part of Microsoft 365, keeps track of which users are licensed and how many computers they've installed Office on.

Note

To activate Microsoft 365 Apps, TLS 1.2 must be enabled by default on the operating system. Some older operating systems, such as Windows 7 Service Pack 1 (SP1) and Windows Server 2012, need an update applied to enable TLS 1.2 by default. For more information, see Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows. But, running Microsoft 365 Apps on these older operating systems isn't supported. For more information, see End of support resources for Office.

Assign and manage licenses

To use Microsoft 365 Apps, your users will need the appropriate license. To assign licenses, do one of the following:

Assign a license to a user directly in the Office 365 portal by selecting a check box on the licenses page for the user’s account.
Use Office 365 PowerShell. For more information, see Assign Microsoft 365 licenses to user accounts with PowerShell.
If you have a subscription for Azure AD Premium P1 and above, or an edition of Office 365 Enterprise E3 or Office 365 A3 or Office 365 GCC G3 and above, you can use group-based licensing with Azure AD. You can assign one or more product licenses to a group, and Azure AD ensures that the licenses are assigned to all members of the group. Any new members who join the group are assigned the appropriate licenses. When they leave the group, those licenses are removed. For more information, see Group-based licensing in Azure Active Directory.

After a user is assigned a license, you can deploy Office to your users or your users can install Office directly from the Office 365 portal. If the user hasn't been assigned a license, the user can't install Office from the Office 365 portal. We recommend assigning the license 24 hours prior to the deployment so you can ensure that the license is provisioned.

Licensing Modes

There are various licensing modes that can be used with a supported version of Microsoft 365 Apps.

Check Microsoft Office Version Using Terminal Commands

Subscription User Based Licensing

This is the default licensing mode for Microsoft 365 Apps. In this mode, the license is carried within the user’s profile. With a single license, users can install and activate Microsoft 365 Apps on up to 5 desktops/laptops, 5 tablets, and 5 mobile devices. Subscription User Based Licensing requires user level activation and requires user sign-in with an Azure Active Directory account.
It is recommended for most scenarios where the user has defined computers and don’t often share them.

Shared Computer Activation

This licensing mode lets you deploy Microsoft 365 Apps to a single computer that is shared by multiple users and where those users are logging in with their own account.
This mode is typically used in scenarios with multiple licensed users connecting to the same device. It is the preferred configuration of Microsoft 365 Apps when used with Remote Desktop Services (RDS) and Virtual Desktop Infrastructure (VDI). It is ideal for shift workers, bank tellers, and users that need to roam across devices.

Device Based Licensing

The Device Based License is designed to simplify management of Microsoft 365 Apps for Enterprise on devices shared by many users. Anyone that signs in and uses that device can use Microsoft 365 Apps for Enterprise to create and edit documents. Device Based Licensing does not require user level activation and does not require the user to have an Azure Active Directory account. There is no limit to the number of sign-ins and anyone with device access can use Microsoft 365 Apps for Enterprise applications.
It is applicable in shared and open access device scenarios where users work across multiple shared devices or where users need occasional access. This is an ideal mode for healthcare and education customers that do not sync generic accounts to Azure Active Directory.

Note

The device must be synced to Azure Active Directory for a Device Based License to be assigned.

Unattended License

Organizations use an array of tools to connect applications and processes together, including frameworks automating other applications. These automation processes may be unattended in their operation and leveraging traditional user accounts is not best practice.
The Unattended License allows for the use of Office with service accounts or other non-user accounts, typically common for automation process execution.

Note

Office applications are not specifically designed for large scale unattended usage scenarios. For more information, see Considerations for Unattended Automation of Office in the Microsoft 365 for Unattended RPA Environment

Viewer Mode

This mode can be used when your organization has users that only need view/print capabilities instead of full create or edit capabilities. This allows unlicensed users of Microsoft 365 Apps to view and print Office files without being prompted to activate Office. When Word, Excel, or PowerPoint are opened, users see a banner message underneath the ribbon in their Office apps that informs them that Office is in Viewer Mode.
This is an ideal mode when the users have an Office for the Web license but not a Microsoft 365 Apps license.

Activating Microsoft 365 Apps

As part of the installation process, Microsoft 365 Apps communicates with the Office Licensing Service and the A