1. Enable the Process Scheduler utility. Engage Reporting Processes must be set to run daily.
2. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   remote_meeting_attendee__v	CRED	ms_team_call_meeting__v	network_type__v	Read
   			All Other Fields	Edit
   remote_meeting__v	CRE	ms_teams_call_meeting__v	attendance_report_process_status__v latest_meeting_start_datetime__v	Edit

3. Grant View permission to the Engage Platform Process Administration (engage_meeting_process_admin_page__v Page.
4. Grant View permission to the CRM PL3 Generic Page.
5. Ensure a layout is assigned to the ms_teams_call_meeting__v record type on the remote_meeting_attendee__v and remote_meeting__v objects.

1. Ensure Configuring Microsoft Teams Meetings is enabled.
2. Grant the following permissions:

   Object	OLS	Record Types	Fields	FLS
   remote_meeting__v	CRED	ms_teams_call_meeting__v	attendance_report_process_status__v engagement_minutes__v meeting_duration__v (optional) meeting_outcome_status__v	Edit
   remote_meeting_attendee__v	CRED	ms_teams_call_meeting__v	account__v join_time__v leave_time__v meeting_duration__v meeting_end_time__v meeting_start_time__v name__v object_type__v remote_meeting__v vexternal_id__v	Edit

Attendance data is pulled in to Vault CRM for all call reports with a Microsoft Teams meeting associated and a call datetime in the previous two weeks. This includes call reports which are not submitted.

The reporting process can be scheduled to run at certain intervals or performed immediately by selecting the Run button on the Process Scheduler. In the Microsoft Teams attendance reporting process, only remote_meeting__v records with the ms_teams_call_meeting__v record type are updated.

If a user previously scheduled an Engage meeting for a call but switched the meeting type to Microsoft Teams, attendance data is pulled for both the Engage meeting’s remote_meeting__v record and the Microsoft Teams meeting’s remote_meeting__v record. For more on switching meeting types, see Switching Remote Meeting Types.

The following data is captured on a remote_meeting__v record for each Microsoft Teams meeting started from Vault CRM:

• engagement_minutes__v - Captures the total number of minutes where the host and at least one attendee were in the meeting together
• meeting_duration__v (optional) - Captures the total meeting duration
• meeting_outcome_status__v - Indicates the meeting outcome using the following values:
• meeting_not_started__v - Displays if the meeting never started
• meeting_not_started_and_attendees_joined__v - Displays if attendees join the meeting but the host never starts the meeting. Whether attendees can join a meeting before the host depends on the organization’s Microsoft Teams configuration.

  If waiting rooms are enabled for Microsoft Teams and an attendee joins the waiting room, but does not join the meeting, they are not counted as an attendee.

• meeting_started_without_attendees__v - Displays if the meeting started but attendees did not join
• meeting_started_with_attendees__v - Displays if the meeting started and at least one attendee joined
• attendance_report_process_status__v - Indicates the status of the reporting process:
• Empty (no value) - The field is empty if this record is still in the two-week processing window or the record is set to a date in the future
• retry__v - Displays if the admin manually sets the field value to retry__v
• success__v - Displays when the record is successfully processed for the last time

The following data is captured on a remote_meeting_attendee__v record for each device joining the meeting:

• join_time__v - Datetime when the device joined
• leave_time__v - Datetime when the device left
• meeting_duration__v - Number of minutes the device was in the meeting
• meeting_end_time__v - Datetime when the meeting ended
• meeting_start_time__v - Datetime when the meeting started
• name__v - Attendee’s display name in Microsoft Teams
• remote_meeting__v - Lookup to the remote_meeting__v record for the meeting joined
• vexternal_id__v - Engage record ID for the attendee

If an attendee rejoins a meeting after leaving or being disconnected for any reason, a new remote_meeting_attendee__v record is created each time they join or rejoin the meeting.

Reviewing Reporting Process History

From the Engage Meeting Process Administration page, admins use the Microsoft Teams Attendance Report Process History table to review the following information from the ten most recent runs:

• Start and end timestamps - Process start and end datetime. The end timestamp only displays when the process is finished.
• Status - Indicates whether the process is currently running
• Type - MS Teams
• Success - Number of records successfully processed. To download the success log as a .CSV file, select the number in the Success column. If the number is zero, users cannot download the log.
• Error - Number of records that encountered an error during processing. To download the error log as a .CSV file, select the number in the Error column. If the number is zero, users cannot download the log.
• Message - States successes and failures that occurred during the run

Retrying Record Processing

To re-run the reporting process for a remote meeting after the two-week time period, manually set the value of the attendance_report_process_status__v field on the appropriate remote_meeting__v records to retry__v. Records are re-run during the next attendance processing job, and remote meeting and remote meeting attendee data is updated accordingly.