Simple Azure Resource Deployment

Introduction

Welcome to Simple Azure Resource Deployment (SARD).

Think of SARD as a 'poor' person's, Azure Landing Zone.

SARD (Simple Azure Resource Deployment) is a group (call 'environment') of Azure resources that is deployed in a single step and reside within the one Azure subscription, inside one Azure Resource Group and generally in one location. Each SARD deploymemt has consistent naming, tagging and security features enabled by default including any Azure Security Perimeter.
There are options including deploying 'private endpoints' and three inbound access options: NAT Gateway, Azure FrontDoor or none. SARD is powered by Hashicorp Terraform, leveraging the azurerm and azapi providers, plus the Microsoft Verified Modules (for Terraform)

BTW, there is nothing wrong with Azure Landing Zones, but they get expensive for individual developers and some organisation, because of all the subscriptions and management groups required. It is also complicated and time consuming to managed.
That makes it next to impossible to deploy them for someone with a single Visual Studio MSDN subscription or a single Non-For-Profit (NFP) subscription.
Now you can deploy all your resources, for prod, dev, test, preprod, uat etc... as dedicated Resource Group within the same Azure subscription.
It is not suitable for large organisation who already have lots of subscriptions, but for hobbyist, NFP and developers, it is a viable option. SARD consolidates resources as much as practical, with overall goal of reducing cost. As a result, SARD does NOT follow some of Azure Best Practices. A lot of Azure Best Practices, creating deidcated resource such as a Storage Accounts for nearly every resource that needs ones, can get very expensive. But turning on Defender for a storage account, which is something you should do, is charged per Storage Account, so even if it is only $10 a month, 1,000 Storage Accounts is $10,000 per month
In other words, what can appear cheap, can add up quick and become quite astronomincal.

For example: A resource that is 10 cents per hour, at 24 hours a day for 30 days = $72 per month Utlimately, SARD is designed for situations where you want the base cost to be no more than $30-50 USD per month.
BTW: As an exception, AZure KeyVaults are create quite liberally, because you cannot apply a RBAC permission to a Key, Secret or Certificate within a Key Vault. So you should create a dedicated one, every time you need one. However, having one or 100 KeyVaults really doesn't make any difference in terms of cost, since the cost is in accessing KeyVault, not creating or have them exist
The currently supported resources are:-