Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

vvargasv

Enable Cross‑Workspace Sharing of Email & Teams Connections

Submitted by Microsoft Employee on ‎04-21-2026 07:47 AM

Description

Hi community,

I’d like to raise a feature request related to governance and connection management in Microsoft Fabric, specifically for Email (Office 365 Outlook) and Microsoft Teams connectors used in Data Factory pipelines.

Scenario

In enterprise environments, it is common to require:

  • Centralized management of connections (e.g., Email / Teams)
  • Reuse of the same connection across multiple workspaces (Dev/Test/Prod, or multiple domains)
  • Consistent governance, including credential lifecycle management and auditing

However, when working with Fabric pipelines that use Outlook or Teams activities, we observed the following behavior:

  • When deploying a pipeline to another workspace, the activity becomes inactive
  • A new user authentication connection must be created in the target workspace
  • If the connection is not recreated, deployment fails or the activity cannot run

This behavior is documented here:

Current Behavior (Documented Limitation)

As per official documentation:

  • Outlook / Teams connections are tied to user authentication
  • When moving pipelines across workspaces:

    “The activity will be inactive in the target workspace until you create a new user authentication connection there” [learn.microsoft.com]

  • Same behavior applies to Teams activity [learn.microsoft.com]

This effectively means:

  • Connections are scoped to the workspace
  • Connections are not reusable across workspaces
  • Each workspace requires manual reconfiguration

Expected Behavior

From an enterprise governance perspective, we would expect:

  • Ability to define centralized, reusable connections
  • Secure sharing of those connections across multiple workspaces
  • Support for CI/CD scenarios without manual re-authentication
  • Reduced duplication of connections and credentials

Why this matters

Other connection types in Fabric (e.g., cloud connections) are moving toward shared and governed models, but Email and Teams connectors still require per-workspace authentication.

This creates an inconsistency in the platform’s governance model, especially for enterprise adoption.

Feature Request

We would like to request support for:

  • Secure, reusable Email and Teams connections
  • Cross-workspace connection sharing
  • Centralized management (similar to cloud connections / gateways)
  • CI/CD-friendly connection lifecycle
Status: New
Comment