There have been some changes to the Azure Portal that have people scratching their heads; I am talking about the infamous collapsable Blade menu.

Troubleshooting Azure Open AI and API calls to OpenAI can be challenging, especially when you may not know where to start!

The idea of this article is to give you not only a place to start with some common scenarios you may run into but also a way of thinking - to help you troubleshoot. This is not a technical 'get-your-hands dirty, delve into those logs' type article.

I am a big fan of the KT, or Kepner-Tregoe problem analysis methodology, and I have used it in many scenarios throughout my career to help discover and test the root cause of various problems. So, we will use the base of this problem analysis methodology to help us troubleshoot the scenarios we will discuss in this article.

When attempting to work with Azure Open AI, you may want to work with an Azure Functions to adjust or massage the response, to do so you can use the Azure Functions bindings for OpenAI's GPT engine to query the OpenAI API. However, you may encounter a 404 Not Found error when attempting to query OpenAI using the Azure Function binding.

When working with Microsoft Azure, you may want an environment for learning, whether for an individual or a team.

This article aims to highlight some reference implementation considerations for implementing a Sandbox environment within the Microsoft Azure platform.

Updating the timezone of your Azure Container Apps containers might not be a common operation, but there are scenarios where it could be necessary.