<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Azure SQL DB on Erwin Staal</title>
    <link>https://staal-it.nl/tags/azure-sql-db/</link>
    <description>Recent content in Azure SQL DB on Erwin Staal</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>KVK: Staal IT, 56920202 - Copyright © 2025</copyright>
    <lastBuildDate>Wed, 27 May 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://staal-it.nl/tags/azure-sql-db/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Securing your Azure SQL DB using Azure Private Link</title>
      <link>https://staal-it.nl/posts/securing-your-azure-db-connection-using-azure-private-link/</link>
      <pubDate>Wed, 27 May 2020 00:00:00 +0000</pubDate>
      
      <guid>https://staal-it.nl/posts/securing-your-azure-db-connection-using-azure-private-link/</guid>
      <description>Whenever you create a new SQL Database on the Azure Cloud, one of the first things you probably do is set the &amp;lsquo;Allow Azure services and resources to access this server&amp;rsquo;-switch to &amp;lsquo;Yes&amp;rsquo;. This allows your App Service for example to access your database. It&amp;rsquo;s not very secure however since all an attacker then needs is your connections string. And although you are probably very careful with that, it might just accidentally get public.</description>
    </item>
    
  </channel>
</rss>
