How to enable API commands (POST, PUT, DELETE, ...) to work on App Service (auth issue)

Warley Farias 20 Reputation points
2024-02-14T17:03:51.08+00:00

Hi, after I searched a lot of sites and watched several videos, I am here to ask for help, for setup my Azure App Service. I implemented functions in API for GET, POST, PUT and DELETE, think like a smal CRUD, but just the GET's functions works fine. The others give me 405 - Method Not Allowed. I want to inform that is not declaration problem (API endpoint with an unsupported verb) or route, but auth problem like verified on this links: I made all recomendations but do not worked, then I have non other options. Because I believe that is just enable something and will work like in my computer.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
{count} votes

Answer accepted by question author
  1. Bryan Trach 17,837 Reputation points Microsoft Employee Moderator
    2024-02-17T05:52:14.08+00:00

    @Warley Farias I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

    Issue: You were looking how to enable API commands on Azure App Service Solution: "HTTPS Considerations:

    • If you’re using HTTPS, ensure that your client-side code (e.g., Postman) also makes requests over HTTPS.
    • Sometimes, switching from HTTP to HTTPS in your request can resolve the issue.

    This worked for me, I just put the "https://" before the calling. I hope that this help somebody in the future, I lost much time." If you have any other questions or are still running into more issues, please let me know.
    Thank you again for your time and patience throughout this issue. Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

    2 people found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Warley Farias 20 Reputation points
    2024-02-16T15:07:53.33+00:00

    Hi everyone, after several try, I asked to Copilot that answered with this:

    1. HTTPS Considerations:
      • If you’re using HTTPS, ensure that your client-side code (e.g., Postman) also makes requests over HTTPS.
      • Sometimes, switching from HTTP to HTTPS in your request can resolve the issue.

    This worked for me, I just put the "https://" before the calling. I hope that this help somebody in the future, I lost mutch time.

    Thanks everyone for the attention.

    0 comments No comments

  2. NICccc-1952 6 Reputation points
    2025-07-03T22:53:03.0766667+00:00

    http://localhost:7290/api/Function

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.