Share via

Logic Apps can't show Custom Connectors

Andreas Georgsson 16 Reputation points
2022-09-28T15:32:26.853+00:00

Logic apps can't load Custom Connectors, error message when choosing All or Custom Connectors.

Error: Resource provider 'Microsoft.Web' failed to return collection response for type 'customApis'.

The problem started when I tried to create a Custom Connector in the region Sweden Central,
Error: The service is temporarily unable to service your request. The tracking Id is '6de3eeac-abb4-4510-9124-4c591bd66205'.

When I tried to create a new Custom Connector whit same name in another resource group I get
Error: The resource 'SwishQRCode' already exists in location 'swedencentral' in resource group 'Sweden'. A resource with the same name cannot be created in location 'northeurope'. Please select a new resource name.

But the resource SwishQRCode can't be found in the location SwedenCentral

I tried creating another Cutom Connector named Swish-QR-Code in reegion North Europe and that Succeded.

But the problem in Logic Apps still remains I can't list Custom Connectors just the error message Resource provider 'Microsoft.Web' failed to return collection response for type 'customApis'. and the connector I created that Succeded is not shown.

Please assist in how to solve this.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,996 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mike Urnun 9,786 Reputation points Microsoft Employee
    2022-10-04T20:36:23.143+00:00

    Hello @Andreas Georgsson - Thanks for posting on MS Q&A!

    It sounds like the initial attempt failed due to service-related issues and left the resource creation process in such a state where you can't use the "SwishQRCode" name anymore -- if you must use this exact name/location pair in your project & need the underlying service related issue resolved, please open a support ticket and work with a service engineer who has deeper insights into your environment to troubleshoot the root cause. If your Azure subscription doesn't carry a support plan to do that, feel free to let me know so and I'd be happy to reach out to you in private comments to enable your subscription with a one-time free support case enablement for resolving this particular problem.

    As for the successful creation of the Custom Connectors but them being absent on the Logic Apps side related issue, could you verify if the Customer Connectors were created in the same region/location as your Logic Apps is in? It might be that you've created the Logic Apps resource in Sweden Central location first, and the Customer Connectors in North Europe?

    0 comments