Skip to content
Brian Lyttle edited this page May 1, 2023 · 3 revisions

Introduction

This document is an overview of the output. It is not yet an exhaustive overview of each file output and included attributes. Inspect the contents of the YAML to check specific details. Readers are expected to understand how multiple documents can be embedded in a YAML file.

User-related files

users.csv

The contents of the users document within the YAML file is transformed into CSV and output without filtering. This results in a complete line-per-object copy of the YAML file contents.

If an object represented in the YAML file is missing all, or some, attributes there should still be a line for the user in this file. When the line is blank, it is possible to investigate more by searching for the previous user within the YAML in Notepad.

Attributes

  • Email (email address registered in Viva Engage)
  • Internal (confirms whether user is a canonical or guest users)
  • State (pending/active/suspended/deleted states can exist in the user lifecycle which differs from AAD)
  • PrivateFileCount (count of private message files associated with the user)
  • PublicMessageCount (count of messages posted in communities)
  • PrivateMessageCount (count of messages posted in private message conversations)
  • LastAccessed (last time user accessed, if available)
  • AAD_State (information from the mapping to the AAD user, if available)

Community-related files

groups.csv

The contents of the groups document within the YAML file is transformed into CSV and output without filtering. This results in a complete line-per-object copy of the YAML file contents.

Attributes

  • Id (group identifier from Viva Engage)
  • Name (customizable group title set by the community admin)
  • Type (whether the group is internal or external)
  • PrivacySetting (whether the group is private or public)
  • State (whether group is active or deleted)
  • MessageCount (message count for the community)
  • LastMessageDate (timestamp of the last post to the community, if messages exist)
  • ConnectedToO365 (confirms if the community is connected to an M365 group)
  • Memberships.External (guest members in the community)
  • Memberships.Internal (internal members in the community)
  • Uploads.SharePoint (count of uploaded files store in SPO)
  • Uploads.Yammer (count of uploaded files stored in legacy Yammer storage)

groups-without-admins.csv

group-admins.csv

Guest-related files

community-guests.csv

other-community-guests.csv