Datasets, regions, and sinks supported by Microsoft Graph Data Connect

Microsoft Graph Data Connect supports a variety of datasets, data regions, and storage locations in Microsoft Azure. This article describes the supported datasets and how to access the dataset schemas, the Microsoft 365 and Microsoft Azure regions that are supported, and the storage locations that Data Connect utilizes through Azure Data Factory.

Datasets

Microsoft Graph Data Connect currently supports the following datasets. To view the schemas for each dataset, create a new dataset in Azure Data Factory and use the Schema tab to view it.

Dataset name Description Sample Schema
BasicDataSet_v0.CalendarView_v0 Contains the events from the Calendar view. CalendarView_v0 Schema
BasicDataSet_v0.Contact_v0 Contains the available information from each user’s address book. Contact_v0 Schema
BasicDataSet_v0.Contact_v1 Contains contact information from each user's address book. Contact_v1 Schema
BasicDataSet_v0.DirectReport_v0 Contains user information about the employees that directly report to each user. DirectReport_v0 Schema
BasicDataSet_v0.Event_v0 Contains the information from a user’s calendar events. Event_v0 Schema
BasicDataSet_v0.Event_v1 Contains the events in each user's calendar. Event_v1 Schema
BasicDataSet_v0.Inbox_v1 Contains the mail folders from each user's inbox. Inbox_v1 Schema
BasicDataSet_v0.MailboxSettings_v0 Contains the mailbox settings of each user. MailboxSetting_v0 Schema
BasicDataSet_v0.MailFolder_v0 Contains the mail folders from each user's mailbox. MailFolder_v0 Schema
BasicDataSet_v0.Manager_v0 Contains user information for the manager of each user. Manager_v0 Schema
BasicDataSet_v0.Message_v0 Contains the email messages from a user’s mailbox. Message_v0 Schema
BasicDataSet_v0.Message_v1 Contains the email message in each user's mailbox. Message_v1 Schema
BasicDataSet_v0.SentItem_v0 Contains the messages sent from each user's mailbox. SentItem_v0 Schema
BasicDataSet_v0.SentItem_v1 Contains the message sent from each user's mailbox. SentItem_v1 Schema
BasicDataSet_v0.TeamChat_v1 Contains Teams chat messages for one-on-one and group chat messages. This dataset excludes chat messages explicitly deleted by users. TeamChat_v1 Schema
BasicDataSet_v0.User_v0 Contains user information (DisplayName, UserPrincipalName, and other information). User_v0 Schema
BasicDataSet_v0.User_v1 Contains user information. User_v1 Schema
DocumentSharingDataset_v0_Preview Contains information about sharing permissions of documents. DocumentSharingDataset_v0_Preview Schema

Regions

Microsoft Graph Data Connect supports extracting data from a variety of different Microsoft 365 regions. To successfully move data from the Microsoft 365 datacenter into your Microsoft Azure storage, the Azure Data Factory instance and the Azure storage location must both map to a supported region for the location of the Microsoft 365 data.

The following table indicates which Microsoft 365 regions are supported and the corresponding Azure regions required for data movement.

Office region Azure region
Asia-Pacific
  • East Asia
  • Southeast Asia
Australia
  • Australia East
  • Australia Southeast
Europe
  • North Europe
  • West Europe
North America
  • Central US
  • East US
  • East US 2
  • North Central US
  • South Central US
  • West Central US
  • West US
  • West US 2
United Kingdom
  • UK South
  • UK West

Sinks

Sinks are the output location that Azure Data Factory uses to place data in Azure storage. Data Connect supports the following sink storage types:

The following characteristics apply to sinks:

  • The output files are of format JSON lines. The output format is fixed, and there is no support for modifying the format of the output. However, you can use Azure Data Factory to copy the result of a Data Connect pipeline into another storage mechanism (such as Azure SQL Database).
  • Service Principal authentication is the only supported authentication mechanism for all sink types in a copy activity with Microsoft 365 as the source.
  • When using Azure Storage Blob as the sink, you must ensure that your application has Storage Blob Data Contributor access to the Azure Storage Blob location.

See also