Custom Connector import using Open API 3.0

(4) Share

Report

Posted on by smalm

According to this link: Open API 3 support the ability to create a custom connecter from an Open API 3.0 .json file is supported automatically since 9/30. However, still getting the "OpenAPI 3.0 schema definitions are not supported. Please try again with an OpenAPI 2.0 definition" message when attempting to import from a 3.0 file. This link: https://learn.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition still contains a box indicating 3.0 is not supported. So which is it? And if it should be enabled are there any special settings in the tenant that need to be enabled to allow it to work?

Categories:

Building Power Apps

I have the same question (0)

All responses (7)

Answers (0)

Community Power Pla... on at

Like (0)

Report

I have the same issue! I'm curious to if this functionality has actually been released and what settings needs to be enabled to make it work

Was this reply helpful? Yes No
smalm 12 on at

Like (1)

Report

Hi @Anonymous ,

What I've learned is that you can import an OpenAPI 3.0 file (yaml or json) if you are creating the connector through Power Automate (not Power Apps). Unclear to me why they are different. That said, the approach is to down convert from 3.0 to 2.0, rather than the platform natively supporting 3.0, so you may run into issues (as I have). It is in preview after all, but my import had several errors (40+) related to schema resolution and path parameters. I have not yet had a chance to identify the specifics on the errors and see if there are any tweaks that can be made in the source file to have better success. FWIW, I've had better success importing my 3.0 files into Postman which supports it natively and then exporting the collection and using that as the source in the "Import a Postman Collection" when creating the custom connector.

Was this reply helpful? Yes No
agsb 2 on at

Like (0)

Report

Workaround: I made Open API 3 spec, made it into a postman collection and then created the custom connector with the postman collection. Custom connector allows Postman collection import even if it has a Open API spec 3 file. This longer workflow is good enough for me temporarily. clearly the permanent solution is for MS to support import of Open API 3 spec YAML.

Was this reply helpful? Yes No
jhoneyfield 4 on at

Like (0)

Report

Big thank you for this! We were able to use Open API 3.1 -> Postman Collection -> Export as Postman Collection 2.1 and Import it directly into Power Automate; worked like a charm. 🙏👏

Was this reply helpful? Yes No
ApiTrader 174 on at

Like (0)

Report

ChatGPT 4.0 is a great way to transform a Swagger 3.0 to 2.0

Was this reply helpful? Yes No
jdaniel1 83 on at

Like (1)

Report

Has there every been support for Open API 3.0 yet? This appears to be backlogged item for over a few years now. One Microsoft learn page says it was int he works but here we still are waiting for it.

Was this reply helpful? Yes No
Suggested answer

JD-26110827-0 2 on at

Like (0)

Report

Update: According to this article, this appears to be hopefully generally available in Feb, 2026, and Public Preview as of now? Curious if anybody has tried this yet. Its hard to trust these Microsoft Articles as they have claimed this was already in Public Preview sense 2022 but obviously was not the case.

https://learn.microsoft.com/en-us/power-platform/release-plan/2025wave2/microsoft-copilot-studio/build-power-platform-connectors-openapi-v3

Was this reply helpful? Yes No