Fabric Pipelines: Teams activity connection sharing blocked+Web v2 cannot post to Teams Incoming

[Tejeswar]

Hello Community Members,

I’m trying to send Microsoft Teams notifications from a Fabric Data Pipeline for both testing and production runs. I’ve hit two blockers:

1. Teams activity (connector) → Cannot be used for testing because the connection is identity‑bound and cannot be shared with my testing team (per tenant policy).
2. Web v2 activity with Teams Incoming Webhook → Fails with 404 Not Found from the Web v2 call, even though the same webhook URL works from PowerShell/cURL. It looks like Web v2 requires a Connection and doesn’t support a pure anonymous POST to external webhooks.

I’m looking for official guidance or supported patterns to send Teams notifications from Fabric Pipelines without sharing connections.

Thanks,

Tejeswar

[v-pgoloju]

Hi @Tejeswar,

Just wanted to follow up to see if you had a chance to try the approach shared by @Lozovskyi  earlier. Please feel free to reach out if you have any questions or need further assistance.

Thanks & Regards,

Prasanna Kumar

[Tejeswar]

Hi @Lozovskyi,

Thank you for your time and suggestion on this query.

I will check the above mentioned approach and update you on the progress.

Thank you for your time.

Regards,

Tejeswar.

[v-pgoloju]

Hi @Tejeswar,

Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @Lozovskyi  for prompt and helpful response.

@Tejeswar Thanks for the Update.

Thanks & Regards,

Prasanna Kumar

[Tejeswar]

Hi @v-pgoloju ,

Do you have any suggestions on the above?

Thank you in advance

Regards,

Tejeswar.

[Lozovskyi]

Hello @Tejeswar, thank you for sharing the issue. Yes, it seems to be a bug. Recently, a service principal was added; it is supposed to be shared.

What I can advise is to raise a ticket for Fabric support. The other way to overcome is to share spn details via the key vault, and all of you create the same spn' connection.

[Tejeswar]

Hi @Lozovskyi ,

Thank you for your inputs.

I have raised the ticket to fabric support. Below is the reply from the support team.

"I would like to inform you that the Teams activity in Microsoft Fabric pipelines supports sending messages to Teams channels or group chats using user authentication methods such as OAuth or organizational accounts. However, service principal authentication is not supported directly within the Teams activity for Fabric pipelines.

Please ensure that you use OAuth or organizational account authentication when creating the connection for the Teams activity in your Fabric pipeline. This approach will allow you to post messages successfully to Teams channels or group chats as part of your pipeline execution."

Post confirmation from fabric team, I have started using Oauth as my auhentication type. Also, I was not able to find any official documentation on how to use service principal for sending teams messages from fabric pipeline.

Thank you in advance.

regards,
Tejeswar

[Lozovskyi]

Hello @Tejeswar,

I apologize for the confusion. Following an additional round of testing, I’ve identified a functional gap or potential bug: while the Connections management interface successfully allows for SPN (Service Principal Name) creation, that specific connection type is not currently selectable within the Pipeline UI activity. Consequently, the only viable path forward is to create a dedicated admin/messaging account to handle all notification routing.

Best regards, Taras

[Tejeswar]

Hi @Lozovskyi ,

Yes, I agree. I have created an admin account which I can use to send the notification but the problem comes when I wanted to share the connection with my collegues.

The connection can't be shared due to security reasons which was set by microsoft. I need to share the connection because on account of a failure of an pipeline any one from the team can rerun it but if one don't have access to the connection, pipeline will fail at the teams activity. 

Thank you for your support.

Regards,

Tejeswar.

[Lozovskyi · Accepted solution]

@Tejeswar Yup, that's an issue.

I can advise building a Logic App for messaging to overcome it.

Use a consumption plan, trigger 'request', then create a connection to that logic app and share it with your team.