@Jaime Huffman Thank you for reaching out to Microsoft Q&A. Sorry for the inconvenience caused by this issue. If you are importing OpenApi 3.0 schema without Servers
and facing this issue in the azure portal, then this is a known issue. Per OpenApi 3.0, if servers array is not provided in the schema it defaults to '/' which causes the failure in the portal. Our product team is working on the fix and ETA is around 2-3 months subject to change based on other factors.
Workaround is to use PowerShell, CLI or REST to import API or add a valid URL such as "https://www.bing.com" to the Servers
array.
If you face any issues with the workaround, please let us know to investigate further. I hope this answers your question and feel free to add a comment if you have any other questions. We would be happy to assist you. Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community.