Installation Overview

Review this information for installing the Subscription Billing in your Microsoft Dynamics 365 for Finance and Operations environment. You can get the latest installation files from the Binary Stream Portal ( .

When you install the latest version of the Subscription Billing, you perform the following activity: 

  1. Applying Binary Stream Deployment Packages

To ensure that the Subscription Billing works as expected, perform this activity on a test environment first. When you are ready to use the Subscription Billing in a live environment, perform this activity to install the solution to the production environment.

Applying Binary Stream Deployment Packages

You can apply the Binary Stream deployment packages automatically through Lifecycle Services (LCS) or manually. It is preferred that the deployment packages are applied automatically. However, some situations might arise where it is not possible to apply the deployment packages automatically.

The order in which the deployment packages are applied is important. You must apply the software deployment packages first, and then apply the license deployment package at the end.

Automatic Deployment

To apply the deployment packages automatically, follow these steps: 

  1. Upload the software and license file deployment packages to your asset library.
  2. Open up the environment page on LCS and select Maintain to apply the deployment package.

Manual Deployment

To apply the deployment packages manually, follow these steps: 

  1. Connect remotely to the Dynamics 365 environment.
  2. Copy the deployment packages to the environment.
  3. For each deployment package, do the following: 
    1. Right-click the deployment package, and select Properties.
      The following security message might appear: 
      This file came from another computer and might be blocked to help protect this computer.
    2. If you see the security message, select the Unblock check box to unblock the file.
      If you do not see the security message, continue to the next step.
  4. Extract the deployment packages to separate folders.
    Note icon. Note: Long path names can result in an error during the installation process. To prevent this type of error, it is suggested that you extract the files to a subfolder within C:/Temp, which helps keep the path name shorter.
  5. Run a Command Prompt as administrator.
  6. For each deployment package, do the following: 
    1. Type the command to go to the extraction folder.
    2. When you are in the folder, type the following command: 
      axupdateinstaller quickinstallall

Note icon. Note: Once you start the manual deployment, you must complete it. Do not stop part way through the process. During the process, the command prompt text might not change for an extended period of time, which is normal. So while it may seem like nothing is happening, the deployment is processing.