Sentinel_Not able to create playbook 'Fortinet-FortiGate-ResponseOnBlockIP' using in-built Data Connector

Question

Sentinel_Not able to create playbook 'Fortinet-FortiGate-ResponseOnBlockIP' using in-built Data Connector

Austin Smith 0

Hi,

I am trying to create a playbook that uses the built-in template 'Fortinet-FortiGate-ResponseOnBlockIP'.

I was able to create the connector/API and it seems to be connected as shown in the image..

The location of the connector is Australia East.

User's image

Now when I am trying to create the playbook using the above mentioned connector and template, I get the error shown in the image.

User's image

Could someone please tell me what I am doing wrong here.

Thanks,

Austin

Ohekpeje 0 Reputation points

2025-04-27T11:44:24.0133333+00:00

“The provided connection definition is not valid. The connection must be located in the same region as the managed API. The requested location was 'australiaeast' whereas the referenced managed API in resource group location” is the connector and playbook in the same region?
Austin Smith 0 Reputation points

2025-04-27T12:29:55.5233333+00:00

@Ohekpeje I believe it is referencing the API 'fortinetcustomconnector-1' which is in Australia East.
Ohekpeje 0 Reputation points

2025-04-27T15:41:47.33+00:00

error indicates that when deploying your ARM template (or playbook) with an API connection—for example, one using managed identity—the region specified for the connection resource does not match the region where the managed API is defined. When Microsoft’s managed APIs (like your fortinetcustomconnector-1) are used within Logic Apps or other services, their connection resource must be deployed in the same region as the managed API’s definition. In this case, hardcoding "australiaeast" in the connection while the managed API reference uses the resource group’s location (i.e. [resourceGroup().location]) is causing a regional mismatch.

1 answer

Your answer

Ohekpeje 0 Reputation points

2025-04-27T11:44:24.0133333+00:00

“The provided connection definition is not valid. The connection must be located in the same region as the managed API. The requested location was 'australiaeast' whereas the referenced managed API in resource group location” is the connector and playbook in the same region?
Austin Smith 0 Reputation points

2025-04-27T12:29:55.5233333+00:00

@Ohekpeje I believe it is referencing the API 'fortinetcustomconnector-1' which is in Australia East.
Ohekpeje 0 Reputation points

2025-04-27T15:41:47.33+00:00

error indicates that when deploying your ARM template (or playbook) with an API connection—for example, one using managed identity—the region specified for the connection resource does not match the region where the managed API is defined. When Microsoft’s managed APIs (like your fortinetcustomconnector-1) are used within Logic Apps or other services, their connection resource must be deployed in the same region as the managed API’s definition. In this case, hardcoding "australiaeast" in the connection while the managed API reference uses the resource group’s location (i.e. [resourceGroup().location]) is causing a regional mismatch.

Answer 1

Hi Austin,

It looks like the issue you're facing is probably due to a mismatch between the location of your connection and the managed API. Your connection is set to "Australia East," but the managed API seems to be in a different region, which is why you're getting that error.

To fix it, start by checking the region where the managed API is deployed. It needs to be the same as the region of your connection. If the API isn't in "Australia East," you'll need to create a new connection in the correct region. Another option is to modify the resource group's location to match the API's region, if that's an option for you.

Here another issues related to fortigate and playbooks:

If the information helped address your question, please Accept the answer.

Luis

Share via

Sentinel_Not able to create playbook 'Fortinet-FortiGate-ResponseOnBlockIP' using in-built Data Connector

1 answer

Your answer