Azure is so awesome because the features it provides are so very dynamic and flexible. The platform provides a starting point for the fruition of ideas, ideas only limited by ones imagination. With its dynamic nature and the flexibility it delivers to consumers, sometimes you just need a note to get your ideas optimally flowing […]
Read More →
According to this “Operating system functionality on Azure App Service” and my interpretation, it means if you attempt to use named pipes (*)(*) for anything other than inter-process communications (*) that it will not work. I was coding some stuff and was getting these errors: SqlException: A network-related or instance-specific error occurred while establishing a […]
Read More →
Here is what I wanted to do. Add some code like this to my ASP.NET application. using System.Diagnostics; … System.Diagnostics.Trace.WriteLine(“System.Diagnostics.Trace.WriteLine() in the Page_Load method”); Trace.Write(“Trace.Write() in the Page_Load method”); System.Diagnostics.Trace.TraceError(“System.Diagnostics.Trace.TraceError() in the Page_Load method”); System.Diagnostics.Trace.TraceWarning(“System.Diagnostics.Trace.TraceWarning() in the Page_Load method”); System.Diagnostics.Trace .TraceInformation(“System.Diagnostics.Trace.TraceInformation() in the Page_Load method”); Then I wanted to write those logs out to […]
Read More →
A method to 100% shutdown the public endpoint of an App Service running in the public tenant is not provided. However, you can create an ILB ASE (which is not a public tenant) or you can restrict the access using an IP Restriction. Here is some information on the detailed feature for setting this up […]
Read More →
I wrote a few articles that discuss how and or why you would need to know the apiVerion api-version when calling Azure REST APIs or making a deployment with an Azure Resource Manager (ARM) template. Azure Function 400 Bad Request How to disable/enable HTTP/2, Azure App Service Using Postman to call Azure REST APIs Make […]
Read More →
There are numerous flavors of ASP.NET modules, for example Web Forms (Web Sites and Web Applications), Web Pages, Model-View-Controller (MVC) and the newest one Core. In this article I want to discuss some learnings about the difference between the compilations of an ASP.NET Web Site (Figure 1) and an ASP.NET Web Application (Figure 2). Figure […]
Read More →Instead of storing user id / passwords or database connection strings in source or configuration files, you should consider storing them in an Azure Key vault. Azure Function 400 Bad Request How to connect to a database from an Azure Function Create an Azure Key Vault secret How to connect to a database from an […]
Read More →In my original article here where I stored the database connection string in an Environment Variable which is no longer an optimal approach (it was only for example). I will now update the Azure Function to access an Azure Key Vault secret which has the database connection string and use it to make the database […]
Read More →Storing, for example, a database connection string which include server name, user id and password in source code or in a configuration file is what is called ‘password leaking’. That means that anyone who has access to application source code can search through and get access to the database, because the information required to connect […]
Read More →I was writing these articles and received this error when calling my Azure Function: [Info] The following Exception happened: Response status code does not indicate success: 400 (Bad Request). Create an Azure Key Vault secret Using Managed Service Identity MSI with and Azure App Service or an Azure Function How to connect to a database […]
Read More →