CORS Issue on Azure Function App (Flex Consumption Host Model)

Anonymous
2024-07-15T07:57:07+00:00

I'm currently facing a CORS (Cross-Origin Resource Sharing) issue with my Azure Function App, which is running on a Flex Consumption host model. It was developed locally and deployed to a Azure. I'm encountering the following error when trying to call the function from the protal:

HTTP response code: 0 Unknown HTTP error HTTP response content: Error: {"message":"Failed to fetch","stack":"TypeError: Failed to fetch\n at https://portal.azure.com/Content/Dynamic/qTMV9j3qzPmv.js:227:24350","isError":true}

Here are the steps I've taken so far:

  • Enabled CORS in Azure Portal in both Azure Function App and Azure Storage Account (Blob and File service - GET,POST,PUT allowed methods)
  • Verified the settings in the "Configuration" section under "Settings" in the Azure portal
  • Tried Incognito Mode
Windows Windows Client for IT Pros Devices and deployment Configure application groups

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-07-15T09:17:28+00:00

    Hello Shelani De Silva,

    thank you for posting on the Microsoft Community Forums.

    Based on the description, I understand that your issue is related to Azure.

    Since there are no engineers dedicated to Azure in this forum. In order to be able to deal with your questions quickly and efficiently, I recommend that you repost your questions in the Q&A forum, where there will be a dedicated engineer to provide you with a professional and effective response.

    Here is a link to the Q&A forum: https://learn.microsoft.com/en-us/answers/questions/

    Have a nice day.

    Best regards,

    Lei

    0 comments No comments
  2. Anonymous
    2024-07-15T09:26:53+00:00

    will do. Thank you Lei.

    0 comments No comments