Make new Office 365 Email Fabric Connection with Service Principal Shareable

[caseybks]

Hi,

The new Office 365 Email Fabric Connection that is required to run a new Office 365 Email in an activity using Service Principal authentication cannot be shared. I get that should be the case for OAuth authentication connections with individual user accountsfor security reasons.

New Office 365 Email Activity

This causes us issues becasue we are using git and branched workspaces. If a connection is not shared with other workspace users then when people branch out to their workspace, artifacts with unshared connections cannot load. Hence, why we are still using the old Email activities. I've just noticed today that the old Email activity is no longer available in pipeline activitiy options. When will the legacy version be going completely, please? And before it goes, will there be any updates to the new Email connection to make it sharable? In the mean time, are there any other options?

Thanks.

[keith_smith1]

Maybe an unexpected side-effect of this is that I can't make a copy of the pipeline in my Fabric workspace. {"message":"Request failed with 400(Bad Request): {\"error\":{\"code\":\"RequestValidationFailed\",\"pbi.error\":{\"code\":\"RequestValidationFailed\",\"exceptionCulprit\":1}}}, \nrequestid: fbc7df47-35cc-6b6e-59b1-481135f282b6"} A workaround for this issue is to export the Pipeline to a zip file, create a new pipeline, then import the zip file and it will allow you to replace the connections. Another workaround to consider is putting the Email task in its own Pipeline and use an Invoke Pipeline task instead. You can parameterize the Pipeline so you can pass all of the relevant values for the email task. This would allow other users to edit the task without needing to create a new Email connection. I doubt these workarounds will work for @caseybks use case.