Open spmanjunath opened 6 months ago
You can reverse engineer it using the Developer feature in your browser to see how the connection is being created.
You'll see which Microsoft.ApiManagement resources are being created and which Power Platform APIs are being called to create the connection.
When creating resources in Portal it quietly creates and or interacts with (often many) other resource dependencies to complete a task. Mapping that button click or GUI-based resource creation workflow back to bicep can be difficult if you don't know what the underlying operations are.
In the Azure Portal it is possible to publish API as connector in Power Platform environment by clicking on 'Create Connector' button in 'Power Platform' blade. However, it appears that this capability is not supported via. bicep file (at least i couldn't find any documentation related to this).
Is it possible to provide this feature maybe as part of
Microsoft.ApiManagement/service/apis
namespace?