Before Vault CRM admins configure this functionality, Microsoft Global Administrators must grant tenant wide consent to the Vault CRM App in the Azure tenant from the Vault CRM-hosted webpage.

This allows the app to do the following:

• Create, read, update and delete events in all calendars the user has permission to access. This includes delegate and shared calendars. Required for Integrating My Schedule and Microsoft Outlook Calendars.
• Read users’ primary email addresses
• Read and create online meetings on behalf of the signed-in user. Required for Microsoft Teams for Service Center.
• Read online meeting artifacts on behalf of the signed-in user. Required for Microsoft Teams for Service Center.
• Create groups and read all group properties and memberships on behalf of the signed-in user. Required for Microsoft Teams for Service Center and Microsoft OneNote for Service Center.
• Read, share, and modify OneNote notebooks the signed-in user has access to in the organization. Required for Microsoft OneNote for Service Center.
• Create, read, update, and delete mail a user has permission to access, including their own and shared mail
• See and update the data you gave it access to, even when users are not currently using the app
• See basic user profile information when the user signs in with their work or another account
• Read the full set of profile properties, reports, and managers of other users in the organization, on behalf of the signed-in user

Ensure the Vault CRM Graph API integration is granted the following permissions:

• User.Read
• Calendars.ReadWrite
• Calendars.ReadWrite.Shared
• OnlineMeetingArtifact.Read.All
• OnlineMeetings.ReadWrite
• Group.ReadWrite.All
• Notes.ReadWrite.All
• Mail.ReadWrite.Shared
• offline_access
• openid
• profile
• email

Multiple Vault CRM Vaults can connect to the same Microsoft tenant.

Granting tenant wide consent enables Vault CRM to request information through the Microsoft Graph API, but it does not provide access to Microsoft Office 365 information. The Vault CRM Microsoft Integration uses Microsoft's best practices for authorization (authZ), authentication (OpenId Connect over OAuth 2), data in transit (HTTPS and TLS 1.2+ encryption) and data at rest. Only Microsoft has access to user credentials.

For more control over the integration from the Microsoft side, admins can assign the application to specific users or groups of users, instead of granting access to all users. For more information on assigning applications to Microsoft groups, see Microsoft's Manage users and groups assignment documentation.

To configure this feature:

1. Ensure Configuring Service Center is complete.
2. Navigate to Business Admin > Objects.
3. Select the Console Application Settings object.

4. Select the Default object record.

5. Select the Edit icon.

6. Select the type of Microsoft Integration.

   Settings for Microsoft integrations apply globally to all cases in the Vault.

• None - Uses Service Center's standard Case Note capabilities
• Microsoft integrations are not available in this option
• MS Teams - Adds Microsoft Teams integration
• Enables integrated collaboration through MS Teams
• Standard application Case Note
• MS OneNote - Enables Case Notes to be stored in Microsoft OneNote
• Changes the Case Note experience
• Administrators should determine the desired case note experience before deploying the Service Center application
• Toggling the Service Center application between Microsoft OneNote and Case Note is not recommended
• MS Teams and OneNote - Enables both Microsoft Teams and Microsoft OneNote



7. Select Save.

The first time you sign in to Vault CRM after the Microsoft integration is enabled for Service Center, you are prompted to log in to Microsoft.

1. Select the Log In button. The Microsoft Sign in page displays.

   

2. Enter your Microsoft credentials.
   
   OR
   
   Select Sign-in options if you are using Single Sign On.

   • If the "Successfully logged in to Microsoft" message displays, close the Microsoft window
   • If the “Unable to log in to Microsoft” message displays, contact your internal help desk for assistance

The Microsoft Teams integration allows you to create a Teams Channel to collaborate with colleagues to address a case. You can create a channel for every case if needed, but Service Center does not automatically create a channel for you.

To create a Teams Channel, select the Create Channel button in the Collaboration Workspace in the right panel.

The button label changes from Create Channel to Creating Channel with a spinner to indicate the channel is being loaded. Channel creation may take up to five seconds.

If the channel is created successfully:

A link to the channel displays. Select the link to open the channel and start working with your team.



• The Timeline updates to display a “Conversation Started: MS Teams Channel” entry with a link to the channel

If a message displays saying the request for Teams is taking longer than expected, select the Check Again button.