Install Viva Sales

Article
04/11/2023

You need to be a Microsoft 365 administrator to deploy and install the Viva Sales add-in for Outlook. You need to be a Teams administrator to deploy and install Viva Sales for Teams.

You can install Viva Sales as an integrated app on multiple platforms or as an individual add-in on a single platform. Whichever method you choose, you can start from either the Microsoft 365 admin center or Microsoft AppSource to install it in Outlook and assign users. If you start from AppSource, you'll finish installation in the Microsoft 365 admin center. Either way, we recommend an administrator installs it for best performance and usability.

The add-in is enabled in Teams but not installed. You need to go to the Microsoft Teams admin center and create setup policies to install the app and assign users. If you install the Viva Sales app for Teams from AppSource, you'll install it to your personal scope only, not for your users.

Note

If your users are using Salesforce, ensure that Microsoft Power Platform is not blocked. You can check its status on the Connected Apps OAuth Usage page in Salesforce.
It can take up to 24 hours for the add-in to show up for your users.

Privileges required to use Viva Sales

Viva Sales applies your organization's existing CRM access controls and user permissions. Administrators must have correct permissions to customize their CRM systems, and users must have the correct permissions to view, update, and create records in their CRM systems from Viva Sales.

Note

If you've made changes in a user's permissions or security roles in your CRM, ask that user to sign out of Viva Sales in Outlook and then sign in again for these changes to be reflected appropriately.
Changes in user permissions or security roles in CRM can take up to 15 minutes to reflect in Viva Sales app for Teams.

Permissions required for Salesforce administrators

Salesforce administrators who need to customize Viva Sales must have the following permissions.

Requirement type	You must have
Permission	User profile needs to have Modify All Data or Manage Data Integrations permission Note: Permissions need to be on the user's profile and not in permission sets assigned to the user.

Additional privileges required for Dynamics 365 customers

Dynamics 365 administrators

If you're using out-of-the-box System Administrator or System Customizer security roles, Viva Sales administration privileges are added automatically.

If you're using custom security roles, you must assign the following security role and privilege to Dynamics 365 administrators who need to customize Viva Sales.

Requirement type	You must have
Security role	Viva Sales Administrator
Privilege	Read privilege on User table

Dynamics 365 sellers

If you're using the out-of-the-box Salesperson or Sales Manager security roles, Viva sales privileges are added automatically and no further action is required.

If you're using custom security roles, you must assign the following security role and privilege to Dynamics 365 sellers who need to use Viva Sales.

Requirement type	You must have
Security role	Viva Sales User
Privilege	Read privilege on User table

The Viva Sales User security role only compliments the custom security roles and does not replace them. If a custom security role assigned to sellers is missing any of the privileges included in Salesperson or Sales Manager security role, you might encounter errors specific to Dynamics 365 permission.

For information on how to assign security roles, see Assign a security role to a user.

To edit custom security roles to match with out-of-the-box Salesperson or Sales Manager role, see Create or edit a security role to manage access.

For information on security roles and privileges, see Security roles and privileges.

Deploy Viva Sales

Looking for step-by-step instructions on how to deploy Viva Sales? Here are the Viva Sales deployment guides:

How to use Viva Sales?

After you install Viva Sales for your users, they can start using it in Outlook and Teams. For information on how to use Viva Sales, see: