@Betty Xu (Yun) (202) Thanks for reaching out. Not all built-in connectors are the same for consumption and standard logic app as documented here.
A Standard logic app workflow has many of the same built-in connectors as a Consumption logic app workflow, but not all.
The workaround would be leveraging the HTTP connector passing the right header and URL to make the call to your APIM endpoint.
Update:
This document from logic app covers how you can make any HTTP call using native connector. APIM API’s does have the endpoint and to authenticate the request you need to pass ocp-apim-subscription-key header as you make any call from your application or while testing any APIM from console/developer portal.
To get more details on how subscription works please refer to this document.
The first step is to get what the request URL, HTTP method, header, request body need to be passed to your APIM API so you can navigate to any of your APIM from azure portal/developer portal. For example, for my below APIM API it is GET method without any request body. To authenticate the APIM API’s you need to leverage the subscription key and pass it as ocp-apim-subscription-key header to authenticate the request.
The next step is to pass the URL, header, request body etc to pass correctly in your native HTTP connector as below for my test API.
Feel free to get back to me if you need any assistance.
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.