Latest

Appropriate data handling is an important part of any software system design. Often times we overlook the risks involved with the visibility and accessibility of data passing through our solutions and don't even think about how secure data handling applies to telemetry and logging. In this post I am going to explore how you can use Azure Logic Apps in-built input/output obfuscation capabilities to limit the exposure of data in operational logging and how you can check that the settings are configured.

Regardless of where your git repositories are hosted, there is always a need to have visbility over what's going on in them. While services like GitHub provide metrics APIs, there are some limitations around those metrics APIs, particularly for busy or large repositories. In this post I'm going to look at how you can use Azure Data Explorer to analyse the commit history for a git repository.

When you provide an open input prompt it's only a matter of time before someone with type or create something inappropriate. In this post we'll look at how you can use features in Azure OpenAI Service to minimise inappropriate use of your chatbots.

As always, Ignite covers a lot of non-developer content, so there's not a huge amount of content to dig into, but I think I've found the developer gold in amongst the lot.

Publication of APIs, particularly for consumer applications, requires some next-level attention to protecting your service. In this post I am going to look at you can use Azure API Management to help protect new or existing RESTful APIs that receive and process JSON objects.