Are dynamic connections for Office 365 Email activity on the roadmap?

[MCseh]

As an ISV, we are developing a solution that our customers can deploy in their own tenants.

We are looking to add email notifications but the fact that the Office 365 Email activity requires a specific connection is a problem for deployment, as having a connection GUID in the pipeline JSON that does not exist in the tenant where the workspace is located tends to block Git synchronization (our deployment method relies on exported Git repos) due to missing dependency errors.

Are there any plans in the near future to provide an option to set up the connection in this activity with a dynamic expression (referencing a variable), similarly to some other activities (e.g. Lookup, Stored procedure, Invoke Pipeline)?

[v-pnaroju-msft]

Hi MCseh,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @tayloramy for your response.

Hi MCseh,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @tayloramy to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[tayloramy · Accepted solution]

Hi @MCseh, 

I'm not seeing anything on the public roadmap: Microsoft Fabric Roadmap

I recommend you post an idea: Fabric Ideas - Microsoft Fabric Community

I think the main problem is that to send mail, a user with a mailbox is required. Service principals can't sent an email without impersonating a user with a mailbox. 

I agree that this is a problem currently, at my org everyone on the data engineering team needs to have their own email connections and switch them out depending on who last edited a pipeline, which is very much not ideal.