Skip to main content

Posts

Azure Functions - Common Developer Requirements

In this blog, I am going to cover some of the most frequent issues/requirements people face when developing Azure Functions via Visual Studio. These topics are based on my learnings while developing Azure Functions and I wanted to share the same with community out there. Here are the topics that I will cover in this blog post - Local Debugging of Service Bus Triggered Azure Functions Solving CORS Issue - Local Debugging and after deployment to Azure Run Azure Functions Locally on a different Port Debug Timer Triggered Azure Functions So let's get started. Local Debugging of Service Bus Triggered Azure Functions When you try to debug your Service Bus triggered Azure Function locally, you would need to ensure that there are no other listeners active for your Service Bus Topic and Subscription. Listeners here refer to other people trying to debug on same Service Bus, Topic and Subscription, other Azure Functions or any WebJobs deployed on Azure and running contin
Recent posts

Swagger Authentication in Dot Net Core

Swagger is really a cool tool to document and test out REST API's. This blog tells about steps to enable Swagger on a Dot Net Core Application along with Authentication as well. In this demo, I am using Azure Active Directory OAuth 2 Authentication to protect my Web API from unauthenticated access. We will be enabling OAuth 2 Authentication on our Swagger UI as well so that we can authenticate using Swagger and then invoke our APIs successfully. OAuth 2 Authentication works by using Bearer Token to validate the caller and provide access to resource. This requires us to register an Application in the Active Directory tenant, which will be used for authentication of the API, and we will use the same app to authenticate Swagger as well. Lets get started - Assuming you have a Dot Net Core Web API that's authenticated via Azure Active Directory OAuth 2 Authentication. Azure Active Directory Application Registration - We need to set up our Active Directory Application so th

Secure Logic App HTTP Endpoints with Azure API Management

Prerequisites ? Azure Subscription PostMan / Fiddler / VS Code with Rest Client Extension ( https://marketplace.visualstudio.com/items?itemName=humao.rest-client ) A HTTP triggered Logic app (this will serve as the HTTP endpoint that we will secure using API Management, you can also do this with Azure Functions, Web API's/Web Services, etc.) What ? API Management (APIM) helps organizations publish APIs to external, partner, and internal developers to unlock the potential of their data and services. You can use API Management to publish APIs to external, partner, and employee developers securely and at scale.  In this blog, we will be configuring APIM so that we can use it to secure our Logic App HTTP Endpoint from public access. What are subscriptions? When you publish APIs through API Management, it's easy and common to secure access to those APIs by using subscription keys. Developers who need to consume the published APIs must include a valid subscript