Forum Discussion

vivien57's avatar
vivien57
Icon for Super User rankSuper User
9 months ago

BMC Control-M Integration with Microsoft Fabric

Hello everyone,

We use BMC Control-M as an orchestrator for all workflows in our information system.

We would therefore like to be able to trigger Fabric workflows via Control-M.

Have any of you already done this?

Did you use the connector that was released at the end of 2025?

https://documents.bmc.com/supportu/controlm-saas/en-US/Documentation/Microsoft_Fabric.htm

Thank you in advance for your feedback.

Vivien

admin
governance

5 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable
    9 months ago

    Hi vivien57 ,
    From a Microsoft Fabric support perspective, as of today Microsoft Fabric does not expose a native inbound connector for external orchestration tools such as BMC Control-M. Fabric Data Factory connectors are primarily data-movement oriented and are not designed for external job orchestration triggers. As a result, from the Fabric side, there is currently no dedicated Control-M connector or listener.
    This is reflected in the official Fabric connector documentation
    Connector overview - Microsoft Fabric | Microsoft Learn

    For the recommended Control-M–driven orchestration pattern, the integration is expected to be initiated from BMC Control-M, not from Microsoft Fabric. Based on BMC’s documentation, the typical integration pattern involves Control-M triggering Fabric workloads through REST API calls, with commonly triggered Fabric artifacts including Pipelines, Notebooks, and Dataflows Gen2. Authentication is handled using Microsoft Entra ID (OAuth 2.0 / Service Principal) in combination with Fabric REST APIs. The connector released at the end of 2025 is currently the supported and recommended approach for Control-M to Fabric integration.


    For Debugging & Validation, if issues arise during setup or execution, troubleshooting should be performed from the Control-M side, such as checking - 
    * API request and response validation
    * Authentication token generation
    * HTTP status codes returned by Fabric APIs
    * Control M job logs and debug traces

  • vivien57's avatar
    vivien57
    Icon for Super User rankSuper User
    9 months ago

    Hello,

    Thank you very much for your feedback.

    Indeed, things will be triggered on the Control-M side. I just wanted to know if anyone had already tested this integration and if they did so via the API or with the Control-M Fabric connector available since the end of 2025.

    Have a nice day,

    Vivien

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 months ago

      Hi vivien57 ,

      At this time, we didn't have an internally tested or documented Control-M and Microsoft Fabric integration to reference. However, based on the currently supported Microsoft Fabric architecture, orchestration is expected to be initiated from the Control-M side rather than from Fabric.

      The suggested approach includes the following high-level steps:

      1. Configure an Azure Entra ID service principal with the appropriate access to the target Fabric workspace.

      2. From Control-M, trigger Fabric artifacts such as pipelines or notebooks using the Microsoft Fabric REST APIs.

      3. Monitor execution status and handle retries or failures from the Control-M side.

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 months ago

        Hi vivien57 ,

        I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you