<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microsoft on scarbrough.co.uk</title>
    <link>/tags/microsoft/</link>
    <description>Recent content in Microsoft on scarbrough.co.uk</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/microsoft/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rewriting Azure Functions for .NET 10</title>
      <link>/post/reworking-azure-function-apps/</link>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      <guid>/post/reworking-azure-function-apps/</guid>
      <description>It seemed like a strange request, when a colleague asked me to look into upgrading our Function Apps to use .NET 10, &amp;lsquo;isolated worker&amp;rsquo;. Since when was it possible to change their runtime version ourselves? And what on God&amp;rsquo;s Green Earth was an &amp;lsquo;isolated worker&amp;rsquo;? It was time to investigate.&#xA;There are a couple of important things to remember about Function Apps, as a starting point. Firstly, my colleagues and I had developed Function Apps exclusively as custom Logic App components, to handle more cumbersome data transforms.</description>
    </item>
    <item>
      <title>Thread Safety in Azure Logic Apps</title>
      <link>/post/development/azure-logic-app-thread-safety/</link>
      <pubDate>Wed, 18 Sep 2024 00:00:00 +0000</pubDate>
      <guid>/post/development/azure-logic-app-thread-safety/</guid>
      <description>After resolving the previous issue with the Content-Type defect in the Azure Logic App&amp;rsquo;s storage connector, I ran into a second problem: The Web pages being generated were populated with the correct content type, but the incorrect content. I quickly discovered that was partly caused by a race condition and with how memory is managed by Azure.&#xA;By default, a Logic App will run up to twenty instances of a &amp;lsquo;For Each&amp;rsquo; loop in parallel, but this is multi-threading instead of true parallel processing.</description>
    </item>
    <item>
      <title>Content-Type Problem with Azure Storage Connector</title>
      <link>/post/development/azure-content-type-bug/</link>
      <pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
      <guid>/post/development/azure-content-type-bug/</guid>
      <description>One of our Logic Apps, which we developed as a static site generator, began writing the Web pages to the storage account as octet stream files, and I narrowed down the problem to a defect in the storage account connector.&#xA;I believe (but I&amp;rsquo;m not 100% certain yet) Microsoft&amp;rsquo;s developers hadn&amp;rsquo;t implemented the &amp;lsquo;&amp;quot;headers&amp;quot;: {&amp;quot;Content-Type&amp;quot;: &amp;quot;text/html&amp;quot;}&amp;rsquo; code for the storage account connectors, and the file type, therefore, always defaults to octet stream.</description>
    </item>
    <item>
      <title>I&#39;m not Richard Stallman, but...</title>
      <link>/post/security/recall/</link>
      <pubDate>Thu, 30 May 2024 00:00:00 +0000</pubDate>
      <guid>/post/security/recall/</guid>
      <description>After ensuring I didn&amp;rsquo;t misunderstand what I read, when I learned about Microsoft&amp;rsquo;s Co-Pilot Recall thing, I couldn&amp;rsquo;t help but ask myself the obvious question: &amp;lsquo;Just how the hell could anyone possibly believe it&amp;rsquo;s a smart idea?&amp;rsquo;. But I sort of know the answer: It&amp;rsquo;s because the obsession among corporations with pleasing investors by forcing &amp;lsquo;AI&amp;rsquo; onto everything and everyone, whether we like it or not, and regardless of the ramifications.</description>
    </item>
    <item>
      <title>Azure Resource Group Security and Authentication</title>
      <link>/post/security/resource-group-security/</link>
      <pubDate>Wed, 31 Jan 2024 00:00:00 +0000</pubDate>
      <guid>/post/security/resource-group-security/</guid>
      <description>The security configuration of Azure services is a fairly broad subject area, and this is more of an introduction to how it works for a Resource Group, in the context of a Logic App that needs to interact with multiple resources. If a DevOps team, instead of the developers, is managing the security, a considerable amount of time will be spent planning and designing services beforehand, and later trying to figure out which security configurations are preventing the services working.</description>
    </item>
    <item>
      <title>Why &#39;low code&#39; isn&#39;t always better</title>
      <link>/post/development/low-code-development/</link>
      <pubDate>Sat, 20 Jan 2024 00:00:00 +0000</pubDate>
      <guid>/post/development/low-code-development/</guid>
      <description>One of the most important lessons I&amp;rsquo;d learned from working with Azure, over the last year or so, is that careful thought should be given to whether it&amp;rsquo;s better to implement a service as a &amp;rsquo;low code&amp;rsquo; solution, or as conventionally-developed software. The former isn&amp;rsquo;t always the fastest, cheapest or more efficient way to get something deployed.&#xA;I&amp;rsquo;m currently of the opinion that Azure&amp;rsquo;s Logic App system is quite good for integrations and basic scheduled tasks - and it has indeed made those kind of things easier to manage - and there aren&amp;rsquo;t any convoluted deployment pipelines to bother with.</description>
    </item>
    <item>
      <title>An Azure subdomain takeover incident</title>
      <link>/post/security/azure-subdomain-takeover/</link>
      <pubDate>Fri, 22 Dec 2023 00:00:00 +0000</pubDate>
      <guid>/post/security/azure-subdomain-takeover/</guid>
      <description>A security incident was flagged this week. As it turned out, nothing was compromised, but it served as a valuable warning of how vulnerable an organisation using Microsoft Azure (or perhaps AWS) could be to a subdomain takeover that could be used in a more sophisticated attack.&#xA;The incident had something to do with a subdomain that was initially mapped to a staging Web site hosted on Azure.&#xA;The Web site was removed some time ago, but the mapping between the subdomain and the site&amp;rsquo;s public &amp;lsquo;azurewebsites.</description>
    </item>
    <item>
      <title>How secure is Azure Key Vault?</title>
      <link>/post/security/azure-key-vault-security/</link>
      <pubDate>Sun, 17 Sep 2023 00:00:00 +0000</pubDate>
      <guid>/post/security/azure-key-vault-security/</guid>
      <description>Azure Key Vault is designed to store (and protect) secrets such as API keys, passwords, cryptographic keys, connection strings, etc. It can store the following categories of data:&#xA;Keys Certificates Secrets The Secrets storage can store arbitrary plaintext values, so Key Vault could potentially be used as a means of centrally managing a collection of usernames and passwords that could be copied and pasted straight from the Azure Portal. Is this a safe method of password management, though?</description>
    </item>
  </channel>
</rss>
