CI CD Deployment issues with Teams Notifications

Hi sammydyson555,

Thank you for your inquiry through the Microsoft Fabric Community Forum.

Based on our understanding, the new Microsoft Teams activity in Fabric pipelines uses user bound OAuth 2.0 authentication. Therefore, such connections might not be shared with service principals or CI/CD identities due to security reasons. As a result, pipelines that contain this activity cannot be deployed using CI/CD at this time. This limitation is officially documented by Microsoft, as shown in the attached screenshot.

The legacy Teams activity works because it might use webhook based authentication and is not identity bound. Currently, one supported option is to continue using the legacy Teams activity.

Additionally, please refer to the link provided below:
Teams activity - Microsoft Fabric | Microsoft Learn

We hope the information provided helps resolve your issue. Should you have any further questions, please feel free to contact the Microsoft Fabric community.

Thank you.

Hi sammydyson555,

Thank you for the update.

Based on our understanding, Microsoft has not announced any deprecation or retirement timeline for the legacy Teams activity in Microsoft Fabric pipelines. There are no indications in official documentation, blogs, or roadmap updates suggesting that it will be removed in the near term. Typically, if Microsoft plans to retire a feature, it is communicated well in advance through official channels such as the Microsoft Fabric blog, Microsoft Learn documentation updates, or the Microsoft 365 Message Center. None of these sources currently mention any deprecation of the legacy Teams activity.

Therefore, you can continue using the legacy Teams activity as a supported and stable option for CI/CD scenarios today. At the same time, for long-term planning, we recommend that you keep an eye on product updates and roadmap announcements, as Microsoft generally ensures that a suitable alternative or feature parity is available before retiring widely used functionality.

If CI/CD support for the newer Teams activity is important for your scenario, we kindly request that you submit an idea in the Ideas portal using the following link: Fabric Ideas - Microsoft Fabric Community. This will help prioritize the capability.

Additionally, please refer to the links below:
Microsoft Fabric Blog
Teams activity - Microsoft Fabric | Microsoft Learn
Microsoft Fabric Roadmap

We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.

Hi sammydyson555,

We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Thank you.

Hi sammydyson555,

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.

Hi sammydyson555  ,

This is a well‑known and very intentional security restriction in Azure DevOps / Power Platform connectors.

This is the Microsoft‑recommended replacement for CI/CD scenarios.

How it works:

Create an Incoming Webhook in the Teams channel and post messages using a simple HTTP POST

• No delegated user identity
• Fully CI/CD safe

Steps

1. In Teams → Channel → Connectors
1. Add Incoming Webhook
2. Copy the webhook URL
3. In Azure DevOps pipeline:
• Use HTTP task or PowerShell
• POST JSON payload
2. Example (PowerShell):

Invoke-RestMethod -Uri $WEBHOOK_URL `

  -Method Post `

  -ContentType 'application/json' `

  -Body '{

    "text": "✅ Deployment completed successfully"

  }'

Option 2: Power Automate Flow (Service‑Triggered)

If you want richer formatting or reuse logic:

1. Create a Power Automate flow
2. Trigger: When an HTTP request is received
3. Action: Post message in Teams
4. Call the Flow from CI/CD using HTTP
5. Benefit:
• Teams auth stays inside Power Automate
• DevOps only calls an endpoint

It is CI/CD friendly and works with new Teams.

Option 3: Graph API + Application Permissions (Advanced)

Only if you control Entra ID and want full automation.

High‑level:

• Register an Entra ID App
• Grant Application permissions to Microsoft Graph:
• ChannelMessage.Send
• Use client credentials flow
• Call Graph API directly

Let me know if any solution from above works for you.

Thanks!