Forum Discussion
Creating ICMs via Activator
Hi v-sshirivolu I alrady tried that but there's no option for ICM in suggested solutions
And when I try to go to help desk, it sends me an internal unrelated tech support page. Is there a proper link for support?
Hi iremugurlu ,
The issue with creating ICM incidents using Microsoft Fabric Activator often occurs when Activator cannot properly connect to the configured ICM connector or when the required incident fields are not mapped correctly. Fabric Activator does not create incidents directly in ICM, instead it sends requests through an ICM connector configured in Azure. To resolve this, ensure that the Connector ID and Routing ID are correctly specified in the Activator rule configuration and that required fields such as Title, Severity, Routing ID, and Description are properly populated in the action settings, as missing or incorrect mappings can cause the Test Action to fail. It is also important to confirm that the user or service principal running the rule has permission to create incidents in ICM and that the Fabric workspace can access the connector. Additionally, check the tenant-level settings in the Fabric Admin Portal, since external integrations may be disabled by default and may need to be enabled by an administrator. If the Test Action still fails, reviewing the rule configuration, connector details, and field mappings usually helps identify whether the issue is related to connector configuration or routing information. Once the connector details, required fields, permissions, and tenant settings are correctly configured, rerun the Test Action to validate the setup, after which the Activator rule should successfully generate an ICM incident when the specified condition is triggered.
Thanks! A few specific things I need help with:
1. Which service principal / identity does Fabric Activator use when calling the ICM connector? Is it a built-in Fabric first-party SP, or do I need to create my own?
2. What connector type should I select in ICM - Certificate, Managed Certificate, or Azure Managed Service Identity (MSI)? And if MSI, which Azure tenant (PME/AME/Corp)?
3. What Application ID do I need to whitelist in the ICM connector's allowed callers?
4. Can you share a working example of a Connector ID + Routing ID pair that someone has already used successfully with Fabric Activator?HI iremugurlu ,
Fabric Activator usually calls downstream services using a Microsoft managed backend identity, so you normally do not need to create your own service principal. For the ICM connector type, you can try using Managed Certificate first since many Microsoft services use that model for service to service calls. If the test action fails, check the ICM connector logs or error message. Sometimes the failure response shows the caller application id that attempted the request. You can take that application id and add it to the allowed callers list in the ICM connector configuration and try again. For routing id and connector id, these are usually created and managed by your organization’s ICM admin or owning team, so you will need to use the values defined in your internal routing setup. This approach may help identify the correct caller identity and resolve the authorization issue.
Hi iremugurlu ,
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