officedev / ms-graph-data-connect

One stop shop for developers using Microsoft Graph data connect

page_type	products	description	languages	extensions
sample	office-365 ms-graph	Microsoft Graph data connect brings Office 365 data and Azure resources to independent software vendors (ISVs). This sample shows you how to use Office 365 data with Azure analytics to build intelligent applications.	csharp	contentType technologies services createdDate samples Microsoft Graph Office 365 Microsoft Graph data connect 2/6/2018 9:50:48 AM

Microsoft Graph data connect

Using Office 365 data with Azure analytics to build intelligent applications

Introduction

Microsoft Graph data connect brings Office 365 data and Azure resources to independent software vendors (ISVs). This system enables ISVs to build intelligent applications with Microsoft’s most valuable data and best development tools. Office 365 customers will gain innovative or industry-specific applications that enhance their productivity while keeping full control over their data. For more information, see Overview

Table of Contents

1. Run ADF pipelines to copy Office 365 data
   • Prerequisites
   • Linked Service Properties
   • Data Set Properties
   • Samples
2. Publish an Azure Managed Application to copy Office 365 data
   • Create a managed application
   • Publish a managed application
3. Capabilities
   • ADF Sinks
   • Compliance Policies
   • Data Regions
   • Datasets
   • Filters
   • User Selection

Deployment

Environment	Description	Deploy
adlsgen2sink-sample	N/A
basic-sample	N/A
blobaadauthsink-sample	N/A
incrementaldataload-sqlwatermark-sample	N/A
incrementaldataload-tumblingwindow-sample	N/A
sql-sample	N/A

Quick Links

• Approve a data access request
• Manage ADF piplines

Help

• FAQ
• Troubleshooting
  • Error Handling
• Contact us

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

ms-graph-data-connect's Issues

Recommended Parameter for Create-Users.ps1

The Create-Users.ps1 script has a hard coded "":ENTERPRISEPACK" license. I recommend using a parameter so users with other subscriptions (:O365_BUSINESS_PREMIUM, etc) can use the script unaltered.

Readme instructions doesn't match deployment script.

I'm noticing the README may need to be updated in the ARMTemplates directory. The parameter for Deploy-AzureResourceGroup.ps1 has changed from ArtifactsDirectory to ArtifactsStagingDirectory.

In addition, there are no directories with adf-v*-sample.

ANNOUNCEMENT: Office 365 data load failure due to Customer Lockbox

Thank you for being an early adopter of Microsoft Graph data connect. If you see the error message below while attempting to run a pipeline it is likely that your organization is configured with the Office 365 Customer Lockbox enabled. Currently, we exclude it as a source for the preview Office 365 Connector.

For now, you may ask the tenant admin to temporarily disable Customer Lockbox or begin development with another organization identity.

The error message you will currently see is shown below:

{ "errorCode": "2200", "message": "ErrorCode=UserErrorOffice365DataLoaderError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Office365
data loading failed to execute. Failed to extract data from Office 365 for Tenant xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx and dataset BasicDataSet_v0.yyy into AzureX account,Source=Microsoft.DataTransfer.ClientLibrary,'", "failureType":
"UserError", "target": "O365toAzureCopyData" }

We will post an update to this issue once we remove this restriction.

testing issue notification

If we receive this email that means any issue posted on github will be forwarded to [email protected]

Closed Issue

Removal of Account key authentication for storage and ADLS Gen2

Thank you for being an early adopter of Microsoft Graph data connect. We have recently rolled out a change to disable Account key authentication to destination sinks of type storage and Azure Data Lake Store Gen2 (Azure Data Lake Store Gen1 did already not support Account key). If your pipeline is using Account key with one of those storage types, we recommend moving to Service Principal authentication, more details on how to utilize Service Principal authentication can be found in this lab. Please reach out here or at [email protected] with any questions.

I have a problem with Microsoft.DataExchange/plans source

Hello, all!

After create service catalog managed application I have a error "The source Office365EnterpriseDataSecurityPackageV1 does not exist or is not accessible."

This is part of mainTemplate.json

"o365dataPlanSourceName": "Office365EnterpriseDataSecurityPackageV1"

{
"type": "Microsoft.DataExchange/plans",
"name": "[variables('o365dataPlanName')]",
"apiVersion": "2018-03-01-preview",
"location": "[resourceGroup().location]",
"properties": {
"source": "[variables('o365dataPlanSourceName')]",
"managedApplicationEnrollment": {
"complianceMonitoring": "Enabled"
}
}
}

Maybe do I need change source, but I don't know what to replace...

Can you help me?

ANNOUNCEMENT: License enforcement to use Microsoft Graph data connect

Thank you for being a Microsoft Graph data connect developer. With Microsoft Graph data connect entering GA at //build 2019 earlier this month, Microsoft Graph data connect is now available through Workplace Analytics. Organizations with Workplace Analytics can extend their insights from Office 365 data by granting and governing access to their data at scale to applications developed in-house or by independent software vendors (ISVs). For more information about the licensing model (including how to obtain a Workplace Analytics license), visit our licensing documentation on the Microsoft Graph site: https://docs.microsoft.com/en-us/graph/data-connect-policies#licensing

If you attempt to run a pipeline and encounter a "Group Expansion Failure. Please contact us for support" error message, ensure you have assigned a valid Workplace Analytics license to the users you are requesting data for and try again. Please create a new GitHub issue if you have any questions.

ANNOUNCEMENT: Issues approving PAM requests through PAM UX

There is currently an ongoing issue where Microsoft Graph data connect requests approved through the PAM UX will ultimately result in a pipeline failure. As a workaround, use the Exchange Online PowerShell module to approve requests. We will continue to provide updates as we work toward a resolution.

Cannot read Contact Object in MS-Graph-Data-Connect

Hello I am trying to read data from contact object and to store in azure blob storage through azure factory pipeline but I am getting below error:

{ "errorCode": "2200", "message": "ErrorCode=UserErrorOffice365DataLoaderError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Office365 data loading failed to execute. Group Expansion Failed. Please contact us for support.,Source=Microsoft.DataTransfer.ClientLibrary,'", "failureType": "UserError", "target": "Copy Data1" }

I am able to read emails and events successfully. Can somebody help me why I am getting this issue?

Managed App confusion

With regards to the Managed App readme.md we have a question with regards to the following paragraph:

Enable tracking resources for your template
Follow instructions at https://aka.ms/aboutinfluencedrevenuetracking to register unique GUID and update mainTemplate.json to enable tracking resources. This is a required step to avoid application package validation error during publishing and it is required for applications in the service catalog (internal organization consumption) and to the Azure marketplace (external consumption).

Following up on the instructions to register a newly generated GUID correctly it appears one needs to have a full fledged cloud partner portal (CPP) registration. Is this really required for publishing into a service catalog that lives in an Office365 demo tenant?

The documentation on
https://docs.microsoft.com/en-us/azure/managed-applications/publish-service-catalog-app does not mention this requirement.