Rearm a volume licensed version of Office

that's included in an operating system

image
Article • 04/25/2025

Applies to: Volume licensed versions of Office Long Term Service Channel (LTSC) 2024, Office
LTSC 2021, Office 2019, and Office 2016 (including Project and Visio)

） Important

Microsoft Office 2016 and Office 2019 will reach end of support on October 14, 2025. After
this date, Microsoft will no longer provide security patches, bug fixes, or technical support
for this version. Users are recommended to migrate to the subscription-based Microsoft
365 service to avoid security risks.

For steps to migrate to a subscription-based Microsoft 365 service, see Plan an upgrade
from older versions of Office to Microsoft 365 Apps

There's a 25-day grace period from the time of installation of Key Management Service (KMS)
clients before notifications to activate are displayed to the user. The 25-day grace period gives
ample time for a KMS host computer to be found and activation to succeed. If activation is
successful, users don't see notifications to activate.

If you want to deploy a volume licensed version of Office, Project, or Visio, as part of an
operating system image, you must rearm your Office installation before you capture the image.
If you don't rearm, users might see notification dialog boxes at the time that the image is
deployed, instead of 25 days after deployment.

Rearming does the following important tasks:

Resets the grace timer to 30 days.

Freezes the grace timer until either an Office application is run, or the ospp.vbs script is
run.
Resets the client computer ID (CMID). The KMS host computer uses the CMID to
determine the number of unique clients. You can use the ospp.vbs script to check the
CMID.

For more information about the ospp.vbs script, see Tools to manage volume activation of
Office.
You can rearm five times, unless you activate Office by using a KMS host computer. If you run
out of rearms, activating by using a KMS host computer lets you rearm once.

７ Note

Rearming is also recommended if you're activating a volume licensed version of Office,

including Project and Visio, by using Multiple Activation Key (MAK). If you're activating by
using MAK and you don't remotely activate for end-users by using the Volume Activation
Management Tool (VAMT) or ospp.vbs, users see an activation dialog box the first time
that an Office application starts. The activation dialog box is slightly different 25 days after
installation. Also, users might immediately see a red title bar warning them of activation
issues if Office wasn't rearmed before the image was captured.

Use the ospprearm command to rearm an Office

installation
1. Verify that the user account that is performing this procedure is a member of the
Administrators group on the KMS host computer.

2. Close all Office applications.

3. Open an elevated command prompt and go to the Program Files\Microsoft

Office\Office16 folder. If you installed the 32-bit version of Office on a 64-bit operating
system, go to the Program Files (x86)\Microsoft Office\Office16 folder.

4. Type ospprearm.exe and then press Enter. If rearm succeeds, the following message
displays: "Microsoft Office rearm successful."

5. Capture the image.

） Important

Do not open an Office application or run ospp.vbs, or do anything else related to

Office while the image is being captured. Otherwise, the grace timer starts.

Related articles
Overview of volume activation of Office
Tools to manage volume activation of Office
Volume Activation Management Tool (VAMT) Technical Reference
Tools to manage volume activation of
Office
Article • 04/25/2025

Applies to: Volume licensed versions of Office Long Term Service Channel (LTSC) 2024, Office
LTSC 2021, Office 2019, and Office 2016 (including Project and Visio)

） Important

Microsoft Office 2016 and Office 2019 will reach end of support on October 14, 2025. After
this date, Microsoft will no longer provide security patches, bug fixes, or technical support
for this version. Users are recommended to migrate to the subscription-based Microsoft
365 service to avoid security risks.

For steps to migrate to a subscription-based Microsoft 365 service, see Plan an upgrade
from older versions of Office to Microsoft 365 Apps

The Office Software Protection Platform script (ospp.vbs), the Software License Manager script
(slmgr.vbs), and the Volume Activation Management Tool (VAMT) help you configure and test
volume licensed versions of Office, including Project and Visio. Before reading this article,
review the following articles:

Overview of volume activation of Office

Activate volume licensed versions of Office by using MAK
Activate volume licensed versions of Office by using Active Directory.

The ospp.vbs script

The Office Software Protection Platform script (ospp.vbs) lets you configure volume licensed
versions of Office products, including Project and Visio. You can find the ospp.vbs script in the
Program Files\Microsoft Office\Office16 folder. If you installed the 32-bit version of Office on

a 64-bit operating system, go to the Program Files (x86)\Microsoft Office\Office16 folder.

７ Note

The ospp.vbs script doesn't work for Microsoft 365 Apps or subscription versions of
Project and Visio. Instead, you can use a PowerShell script named vnextdiag.ps1. For more
information, see Check the license and activation status for Microsoft 365 Apps.
Running ospp.vbs requires the cscript.exe script engine. To see the Help file, type the following
command and press ENTER:

Console

cscript ospp.vbs /?

The general syntax is as follows:

Console

cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]

Option
Specifies the option and value to activate a product, install or uninstall a product key, install
and display license information, set the Key Management Service (KMS) host name and port,
and remove the KMS host name and port. The options and values appear in the tables in this
section.

ComputerName
Name of the remote computer. If you don't provide a computer name, the command uses the
local computer.

User
Account that has the required permission on the remote computer.

Password
Password for the account. If you don't provide a user account and password, the command
uses your current credentials.

） Important

Before you run ospp.vbs, ensure that:

If you run the script on a remote computer, confirm that the Windows Firewall allows
Windows Management Instrumentation (WMI) traffic on that computer.
Use a user account that belongs to the Administrators group on the computer where
you run the script.
Run the ospp.vbs script from an elevated command prompt.

Global options for ospp.vbs

 ﾉ Expand table

Global option Description

/act Activates installed Office product keys.

/inpkey:value Installs a product key (replaces existing key) with a user-provided product key. A value is
required.

/unpkey:value Uninstalls an installed product key using the last five digits of the product key to
uninstall (as displayed by the /dstatus option). A value is required.

/inslic:value Installs a license using the path of the user-provided .xrm-ms license. A value is required.

/dstatus Displays license information for installed product keys.

/dstatusall Displays license information for all installed licenses.

/dhistoryacterr Displays the failure history for MAK/retail activation.

/dinstid Displays the Installation ID for offline activation.

/actcid:value Activates a product using a user-provided Confirmation ID. A value is required.

/rearm Resets the licensing status for all installed Office product keys.

/rearm:value Resets the licensing status for an Office license using a user-provided SKU ID value. A
value is required.

Use this option with the SKU ID specified by the /dstatus option if you run out of rearms
and activated Office through KMS or Active Directory-based activation to gain another
rearm.

/ddescr:value Displays the description for a user-provided error code. A value is required.

The following table describes the ospp.vbs options for configuring the KMS client.

KMS client options for ospp.vbs

ﾉ Expand table

KMS client Description

option

/dhistorykms Displays KMS client activation history.

/dcmid Displays the KMS client computer ID (CMID).

/sethst:value Sets a KMS host name using a user-provided host name. A value is required.
 KMS client Description
option

This command sets

HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName
(REG_SZ).

/setprt:value Sets a KMS port using a user-provided port number. The default port number is 1688. A
value is required.

This command sets

HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServicePort
(REG_SZ).

/remhst Removes the KMS host name and resets the port to the default (1688).

/cachst:value Allows or denies KMS host caching. A value is required (TRUE or FALSE).

/actype:value (Windows 8.1 and later versions only) Sets the volume activation type. A value is required.

Values: 1 (for Active Directory-based), 2 (for KMS), 0 (for both).

/skms- (Windows 8.1 and later versions only) Sets the specific DNS domain in which all KMS
domain:value Service (SRV) records appear. This setting doesn't affect auto-discovery if a single KMS
host name is set using the /sethst option. The value must be the Fully Qualified Domain
Name (FQDN).

/ckms- (Windows 8.1 and later versions only) Clears the specific DNS domain in which all KMS
domain SRV records appear. If no single KMS host name is set using /sethst, auto-discovery finds
the KMS host.

Scenarios that use ospp.vbs

These scenarios assume that you run ospp.vbs from an elevated command prompt.

７ Note

Any changes you make affect only Office client products. Configure the Windows client
separately by using the slmgr.vbs script.

To change the product key to a MAK key on a remote computer

1. If the remote computer is named contoso1, run the following command to enter the
product key. This command assumes you have administrator credentials on the remote
computer. If your credentials differ from your sign in name and password, type your sign
in name and password at the command line and press ENTER:
 Console

cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx contoso1

2. To activate the remote computer, type the following command and press ENTER:

Console

cscript ospp.vbs /act contoso1

To diagnose KMS activation errors

1. If the computer has the KMS client key installed, check the licensing status by typing the
following command and pressing ENTER:

Console

cscript ospp.vbs /dstatusall

2. To view the KMS activation history, type the following command and press ENTER:

Console

cscript ospp.vbs /dhistorykms

3. To trigger activation, type the following command and press ENTER:

Console

cscript ospp.vbs /act

4. Check the error message for error code 0xC004F042. If you see an error code in the
notification dialog boxes, use that code to check the error message. To do so, type the
following command and press ENTER:

Console

cscript ospp.vbs /ddescr:0xC004F042

To turn on or off KMS host caching on the KMS client

 1. On the KMS client computer, to turn on caching, type the following command and press
ENTER:

Console

cscript ospp.vbs /cachst:TRUE

2. On the KMS client computer, to turn off caching, type the following command and press
ENTER:

Console

cscript ospp.vbs /cachst:FALSE

To test a KMS host name and then set auto-discovery

1. If you test a KMS host named kmstest.contoso.com and want to specify it in the KMS
client, type the following command and press ENTER:

Console

cscript ospp.vbs /sethst:kmstest.contoso.com

７ Note

If you change the default port on the KMS host computer, run ospp.vbs with the /setprt
option. For example: cscript ospp.vbs /setprt:1750

2. To trigger activation, type the following command and press ENTER:

Console

cscript ospp.vbs /act

3. To check the KMS activation history and confirm the host contacted successfully, type the
following command and press ENTER:

Console

cscript ospp.vbs /dhistorykms

 4. To enable auto-discovery of the production KMS host using Domain Name System (DNS),
remove the specified KMS host name by typing the following command and pressing
ENTER:

Console

cscript ospp.vbs /remhst

The slmgr.vbs script

The Software License Manager (slmgr.vbs) script, located in the Windows\system32 folder,
configures and retrieves volume activation details for the Office KMS host and the Windows
host. For more information, see Configuring KMS Hosts for Windows.

You can run the script locally on the target computer or remotely from another computer. You
must use an administrator account to run the script. If a standard user runs slmgr.vbs, some
license data might be missing or incorrect, and many operations become prohibited.

The slmgr.vbs script uses either the Windows-based script host ( wscript.exe ) or the
command-based script host ( cscript.exe ). Administrators can specify the script engine. If you
don't specify a script engine, slmgr.vbs uses the default, wscript.exe . Use the cscript.exe
script engine.

You must restart the Software Licensing Service for any changes to take effect. To restart the
Software Licensing Service, use the Microsoft Management Console (MMC) Services snap-in or
type the following command:

Console

net stop sppsvc && net start sppsvc

Run slmgr.vbs with at least one parameter. Running the script without any parameters displays
Help information. The following table lists slmgr.vbs command-line options and describes each
one. Most parameters configure the KMS host computer. However, the parameters /sai and
/sri pass to KMS clients after they contact the KMS host computer. The general syntax of

slmgr.vbs is as follows (assuming you use the cscript.exe script engine):

Console

cscript slmgr.vbs [ComputerName] [User] [Password] [Option]

ComputerName
Name of the remote computer. If you don't provide a computer name, the command uses the
local computer.

User
Account with required permission on the remote computer.

Password
Password for the account. If you don't provide a user account and password, the command
uses your current credentials.

Option
Options appear in the following table.

Slmgr.vbs command options

ﾉ Expand table

Option Description

/ipk ProductKey Installs the product key for Windows (default) or another application identified by
the product key.

/ato ActivationID Activates the KMS host for Windows (default) or the application identified by the
provided Activation ID.

/dti ActivationID Displays the Installation ID used for telephone activation of the KMS host
computer for Windows (default) or the application identified by the provided
Activation ID. Enter the Installation ID into the telephone to receive the
Confirmation ID, which activates the KMS host computer using the /atp
parameter.

/atp ConfirmationID After you receive the Confirmation ID, activate the KMS host for Windows (default)
ActivationID or the application identified by the provided Activation ID.

/dlv ActivationID Displays detailed license information for Windows (default) or the application
identified by the provided Activation ID.

For example, run the following command at an elevated command prompt in the
Windows\system32 folder to get the status of the Office KMS host:

cscript slmgr.vbs /dlv 70512334-47B4-44DB-A233-BE5EA33B914C

/dli ActivationID Displays license information for Windows (default) or the application identified by
the provided Activation ID.

/upk ActivationID Uninstalls the product key for Windows (default) or the application identified by
the provided Activation ID.
 Option Description

CAUTION: If you intend to uninstall the product key for Office and omit the
Activation ID, the command uninstalls all installed product keys, including the
Windows product key.

/xpr ActivationID Displays the expiration date for the current license state.

/sprt PortNumber Sets the TCP communications port on a KMS host computer. Replace PortNumber
with the TCP port number to use. The default is 1688.

/cdns Disables automatic DNS publishing by a KMS host computer.

/sdns Enables automatic DNS publishing by the KMS host computer.

/cpri Lowers the priority of KMS host computer processes.

/sai Changes how often a KMS client tries to activate itself when it can't find a KMS
ActivationInterval host computer. Replace ActivationInterval with a value expressed in minutes. The
default is 120 minutes.

/sri RenewalInterval Changes how often a KMS client tries to renew its activation by contacting a KMS
host computer. Replace RenewalInterval with a value expressed in minutes. The
default is 10080 minutes (seven days). This setting overrides the local KMS client
settings.

７ Note

Activation ID for Office LTSC 2024: F3D89BBF-C0EC-47CE-A8FA-E5A5F97E447F

Activation ID for Office LTSC 2021: 47F3B983-7C53-4D45-ABC6-BCD91E2DD90A
Activation ID for Office 2019: 70512334-47B4-44DB-A233-BE5EA33B914C
Activation ID for Office 2016: 98EBFE73-2084-4C97-932C-C0CD1643BEA7

Slmgr.vbs command options (Active Directory–based

activation)
The following table shows the command options for activating an Active Directory Domain
Services (AD DS) forest using Active Directory–based activation.

ﾉ Expand table

Option Description

/ad-activation-online ProductKey Activates an AD DS forest using the user-provided product

 Option Description

key.

/ad-activation-apply-get-iid ProductKey Displays the installation ID for an AD DS forest.

/ad-activation-apply-cid ProductKey Activates an AD DS forest using the user-provided product key

ConfirmationID and Confirmation ID.

Volume Activation Management Tool (VAMT)

Volume Activation Management Tool (VAMT) gives you a graphical interface to manage
volume activation. For more information, see Volume Activation Management Tool (VAMT)
technical reference.

７ Note

Office LTSC 2024, Office LTSC 2021, and Office 2019 require at least VAMT 3.1.

Manage volume activation for Office LTSC 2024 using VAMT

To manage volume activation for Office LTSC 2024 using VAMT, follow these steps:

1. Identify the installation folder for VAMT—for example, C:\Program Files (x86)\Windows
Kits\10\Assessment and Deployment Kit\VAMT3 .

2. Download Office LTSC 2024 support files from the Office VAMT download link .
3. Copy the pkeyconfig-office24-client.xrm-ms , pkeyconfig-office24-kmshost.xrm-ms , and
Office24.cilx files to the appropriate VAMT directories:

Copy the .xrm-ms files into the VAMT3\pkconfig folder.

Copy the .cilx file to a location where you can easily access it for import.

To import Office LTSC 2024 data into VAMT:

1. Open VAMT.
2. In the Actions pane, choose Import list to open the Import List dialog box.
3. In the Import List dialog box, navigate to the location of the Office24.cilx file, select the
file, and choose Open.
4. In the Volume Activation Management Tool dialog box, select OK to begin the import.
VAMT shows a progress message while it imports the file. Select OK when a confirmation
message appears that the import completed successfully.
Related articles
Overview of volume activation of Office
Activate volume licensed versions of Office by using MAK
Activate volume licensed versions of Office by using Active Directory
Deployment guide for Project
Article • 05/19/2025

How you deploy Project to the users in your organization depends on which version of Project
you purchase. A common purchase option for organizations is one of the following versions of
Project:

Project Online Desktop Client, available as a subscription with Planner and Project Plan 3
or Planner and Project Plan 5.
Project Professional 2024 or Project Standard 2024, available as a one-time purchase
through a volume licensing agreement.
Project Professional 2021 or Project Standard 2021, available as a one-time purchase
through a volume licensing agreement.
Project Professional 2019 or Project Standard 2019, available as a one-time purchase
through a volume licensing agreement.
Project Professional 2016 or Project Standard 2016, available as a one-time purchase
through a volume licensing agreement.

Before you deploy, be sure to review the system requirements for the version of Project that
you plan to deploy to the users in your organization.

） Important

There are some combinations of Office, Visio, and Project that can't be installed together
on the same device. For more information, see Supported scenarios for installing
different versions of Office, Visio, and Project on the same computer.

Deploy Project
The following sections provide guidance on how to deploy different versions of Project.

Deploy Project Online Desktop Client

Here are the general steps to deploy Project Online Desktop Client to users in your
organization:

1. Purchase either Planner and Project Plan 3 or Planner and Project Plan 5, which includes
Project Online Desktop Client and the Planner app, with enough licenses for all of your
Project users.
2. Sign in to the Microsoft 365 admin center and assign licenses for Project Online Desktop
Client to those users.
 3. Have your users sign in to Office.com , select Apps from the navigation menu, and then
select Install apps > Microsoft 365 apps. In the installation pop-up, users can select
Project and install it on their device. Users must be local administrators on their devices
to complete the installation.

If you want to have more control over how Project is deployed to your users, you can do the
following instead:

1. Download the Office Deployment Tool from the Microsoft Download Center.
2. Create a configuration.xml file to use with the Office Deployment Tool to install Project
Online Desktop Client.

We recommend using the Office Customization Tool in the Microsoft 365 Apps
admin center to create the configuration file. Leave the Office Suite field empty
and choose your version in the Project dropdown.
We also recommend reviewing the Build dynamic, lean, and universal packages for
Microsoft 365 Apps article on how to optimize your configuration file. This step is
optional.

3. Use the Office Deployment Tool to deploy Project Online Desktop Client on your users'
devices.

We recommend installing Project without downloading the source files beforehand.

This reduces the overall network utilization and removes the need to maintain the
source files.

If you already use other tools to deploy software to your users, such as Microsoft Configuration
Manager, you can use the Office Deployment Tool along with those tools to deploy Project.

Deploy a volume licensed version of Project 2024

To deploy a volume licensed version of Project Professional 2024 or Project Standard 2024 to
users in your organization, follow these general steps:

1. Purchase Project 2024 as part of a volume licensing agreement.

2. Use the Office Deployment Tool and a configuration.xml file to install Project 2024 from
the Office Content Delivery Network (CDN) on the internet. For more information, see
Deploy Office LTSC 2024

It's recommended to use the Office Customization Tool in the Microsoft 365 Apps
admin center to create the configuration file. Leave the Office Suite field empty
and choose your version in the Project dropdown.
 It’s recommended to install Project directly without downloading the source files
beforehand. This approach reduces overall network utilization and eliminates the
need to maintain the source files.

If you use other tools, such as Microsoft Configuration Manager, to deploy software to your
users, you can integrate the Office Deployment Tool with those tools to deploy volume
licensed versions of Project.

７ Note

Volume licensed versions of Project 2024 are available directly from the Office CDN.
Volume licensed versions of Project 2024 are installed using Click-to-Run rather than
Windows Installer (MSI).
The Office Customization Tool (OCT) used for Windows Installer (MSI) versions of
Project isn't applicable for volume licensed versions of Project 2024.

Deploy a volume licensed version of Project 2021

Here are the general steps to deploy a volume licensed version of Project Professional 2021 or
Project Standard 2021 to users in your organization:

1. Purchase Project 2021 as part of a volume licensing agreement.

2. Use the Office Deployment Tool and a configuration.xml file to install Project 2021 from
the Office Content Delivery Network (CDN) on the internet. For more information, see
Deploy Office LTSC 2021.

We recommend using the Office Customization Tool in the Microsoft 365 Apps
admin center to create the configuration file. Leave the Office Suite field empty
and choose your version in the Project dropdown.
We recommend installing Project without downloading the source files beforehand.
This reduces the overall network utilization and removes the need to maintain the
source files.

If you already use other tools to deploy software to your users, such as Microsoft Configuration
Manager, you can use the Office Deployment Tool along with those tools to deploy volume
licensed versions of Project.

７ Note

Volume licensed versions of Project 2021 are available directly from the Office CDN.
 Volume licensed versions of Project 2021 are installed by using Click-to-Run instead
of by using Windows Installer (MSI).
The Office Customization Tool (OCT) that's used for Windows Installer (MSI) versions
of Project isn't used with volume licensed versions of Project 2021.

Deploy a volume licensed version of Project 2019

Here are the general steps to deploy a volume licensed version of Project Professional 2019 or
Project Standard 2019 to users in your organization:

1. Purchase Project 2019 as part of a volume licensing agreement.

2. Use the Office Deployment Tool and a configuration.xml file to install Project 2019 from
the Office Content Delivery Network (CDN) on the internet. For more information, see
Deploy Office 2019 (for IT Pros).

We recommend using the Office Customization Tool in the Microsoft 365 Apps
admin center to create the configuration file. Leave the Office Suite field empty
and choose your version in the Project dropdown.
We recommend installing Project without downloading the source files beforehand.
This reduces the overall network utilization and removes the need to maintain the
source files.

If you already use other tools to deploy software to your users, such as Microsoft Configuration
Manager, you can use the Office Deployment Tool along with those tools to deploy volume
licensed versions of Project.

７ Note

Volume licensed versions of Project 2019 are available directly from the Office CDN.
Volume licensed versions of Project 2019 are installed by using Click-to-Run instead
of by using Windows Installer (MSI).
The Office Customization Tool (OCT) that's used for Windows Installer (MSI) versions
of Project isn't used with volume licensed versions of Project 2019.

Deploy a volume licensed version of Project 2016

Here are the general steps to deploy a volume licensed version of Project Professional 2016 or
Project Standard 2016 to users in your organization:
 1. Purchase Project 2016 as part of a volume licensing agreement.
2. To download your version of Project 2016, go to Microsoft 365 admin center > Billing
> Your products > Volume licensing > Download and keys.
3. If you want to configure user settings for when Project is installed, you can use the Office
Customization Tool (OCT).
4. Deploy Project 2016 to your users. For example, you can send your users a script to run
that installs Project from a network share on your local network.

If you already use other tools to deploy software to your users, such as Microsoft Configuration
Manager, you can use the Office Customization Tool (OCT) along with those tools to deploy
Project.

７ Note

The Office Customization Tool (OCT) is only available for versions of Project 2016 that are
purchased as part of a volume licensing agreement. The OCT can't be used for retail
versions of Project 2016, such as versions bought at a retail store or online.

Configure user settings for Project by using Group

Policy
If you want to specify and maintain certain user settings for your Project installations, you can
download the Group Policy Administrative Template files (ADMX/ADML) for Office and use
them to configure Group Policy settings. Group Policy can be used only with devices joined to a
domain.

The same Group Policy settings work for Project Online Desktop Client, and volume licensed
versions of Project.

End user resources for Project

To help your users get started with Project, here are some resources to share with them:

Project help & learning

Get started with Project

Related articles
Documentation to help you plan, deploy, and manage Project Server and Project Online
Plans and pricing information
Deployment guide for Visio
Article • 05/19/2025

How you deploy Visio to the users in your organization depends on which version of Visio you
purchase. A common purchase option for organizations is one of the following versions of
Visio:

Visio desktop app that comes with a Visio Plan 2 subscription.

Visio LTSC Professional 2024 or Visio LTSC Standard 2024, available as a one-time
purchase through a volume licensing agreement.
Visio LTSC Professional 2021 or Visio LTSC Standard 2021, available as a one-time
purchase through a volume licensing agreement.
Visio Professional 2019 or Visio Standard 2019, available as a one-time purchase through
a volume licensing agreement.
Visio Professional 2016 or Visio Standard 2016, available as a one-time purchase through
a volume licensing agreement.

Before you deploy, be sure to review the system requirements for the version of Visio that
you plan to deploy to the users in your organization.

） Important

There are some combinations of Office, Visio, and Project that can't be installed together
on the same device. For more information, see Supported scenarios for installing
different versions of Office, Visio, and Project on the same computer.

Deploy Visio
The following sections provide guidance on how to deploy different versions of Visio.

Deploy a subscription version of Visio

Here are the general steps to deploy a subscription version of Visio to users in your
organization:

1. Purchase Visio Plan 2, with enough licenses for all of your Visio users.
2. Sign in to the Microsoft 365 admin center and assign licenses for Visio to those users.
3. Have your users sign in to Office.com , select Apps from the navigation menu, and then
select Install apps > Microsoft 365 apps. In the installation pop-up, users can select Visio
and install it on their device. Users must be local administrators on their devices to
complete the installation.