azure-quickstart-templates
Enterprise-Scale
Our great sponsors
azure-quickstart-templates | Enterprise-Scale | |
---|---|---|
42 | 19 | |
13,708 | 1,609 | |
0.9% | 2.5% | |
9.9 | 8.7 | |
about 20 hours ago | 5 days ago | |
Bicep | PowerShell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
azure-quickstart-templates
- Instantly Deploy BrowserBox on Azure Cloud – open-source isolated browser
- Deploy BrowserBox from an Azure Quickstart Template
- Chef extension for Azure VM
-
Chef extension for Azure VM in Bicep
I found a quick start template for this in Arm, I’m sure if you just decompile the ARM json it will give you a good heads start on how it should work.
-
Bicep: Cyclical Dependency Issue (Network resources)
There is a GitHub issue regarding this topic - https://github.com/Azure/azure-quickstart-templates/issues/2786
- Struggling to understand "_artifactsLocation" parameter when using ARM templates
-
Removing secondary disk
I'm using this video (https://www.youtube.com/watch?v=J4NCvIMuzVE) as a guide to start building out Windows VM's, and running into some questions. I'm trying to use the template located here ( azure-quickstart-templates/quickstarts/microsoft.compute/vm-simple-windows at master · Azure/azure-quickstart-templates (github.com)).
- The yaml document from hell
-
ARM / Bicep template development just by hand?
You can use quick start templates (https://github.com/Azure/azure-quickstart-templates/) as a starting point, but not all examples are bicep ready yet. But those can be easily converted to bicep.
-
SFTP for Azure Blob Storage Generally Available - Pricing
I think it was this one https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files-existing-storage and this https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.containerinstance/aci-sftp-files
Enterprise-Scale
- Azure Policies
-
App Gateway deploy diagnostic settings with Azure Policy
We are deploying all our App Gateways in the hub subscription (a hub and spoke architecture). Occasionally, App Gateways are created without the diagnostic settings enabled on them (I know, this can be automated with IaC, but there more to it on a org level, and not worth discussing here, but yes, this could be a solution). However, I’m planning to use the following policy definition provided by the Azure Enterprise Scale project https://github.com/Azure/Enterprise-Scale/blob/main/src/resources/Microsoft.Authorization/policyDefinitions/Deploy-Diagnostics-ApplicationGateway.json I’ve imported it, tested, works. BUT, as of today all App Gateways are sitting in one resource group, meaning that when app/dev teams want to access the logs, they get to potentially view logs for others as well (different teams, countries etc.). Not sure how this could be a problem from a regulatory, compliance standpoint, but the IT team was thinking about splitting the App Gateways per individual resource groups scope to the countries (one rsg for country x, another for country y …) where people from subscription x would be granted access to only rsg x within the transit subscription. Each would then have a dedicated Log analytics workspace in that resource group (the central IT team would still have access to all logs, countries only scope with RBAC to the respective resource groups). I could then of course assign per resource group the above policy n-time to make sure that the parameters reflected in each policy assignment point to the correct Log Analytics workspace.
-
Recommended Azure Policies
Hey! You should check out all the policies that are included within the Azure landing zone, these are what’s recommended as part of a landing zone deployment: https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies
-
Management group separation
And it is in separate MG in the reference Enterprise Scale but if you look at the policies assignments - https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Policies - you will notice policies I mentioned are assigned at the intermediate root level, so sandbox MG inhertis them.
-
dis-allow users to add inbound port rules?
There is a Azure policy somewhere in https://github.com/Azure/Enterprise-Scale that can block creation of rules for specific ports, etc.
-
[Issue] No cost analysis when scoping to management group
If you plan to scale out more (and for many other reasons), you should consider the reference architecture for Azure Landing Zones fka Enterprise Scale Landing Zones. https://github.com/Azure/Enterprise-Scale
-
Management group structure for enterprise environment?
There is also a terraform version if that is your preferred IaC - https://github.com/Azure/Enterprise-Scale
-
Azure Landing Zone / Enterprise Model Assistance
You can opt to deploy the ESLZ reference implementation for AdventureWorks and select the single option for platform. https://github.com/Azure/Enterprise-Scale/
-
Azure Policy to Audit Application Gateway SSL Policy?
{ policyType: "Custom", mode: "Indexed", displayName: "Application Gateway should be deployed with proper sslPolicy", description: "This policy enables you to restrict that Application Gateways is always deployed with the proper sslPolicy", metadata: { version: "1.0.0", category: "Network", source: "https://github.com/Azure/Enterprise-Scale/" }, parameters: { effect: { type: "String", allowedValues: [ "Audit", "Deny", "Disabled" ], defaultValue: "Audit", metadata: { displayName: "Effect", description: "Enable or disable the execution of the policy" } } }, policyRule: { if: { allOf: [ { field: "type", equals: "Microsoft.Network/applicationGateways" }, { field: "Microsoft.Network/applicationGateways/sslPolicy.policyName", notequals: "20170401S" } ] }, then: { effect: "[parameters('effect')]" } } }
-
MSDN / no global owner rights
I have a MSDN subscription but do not have Owner rights to it. Is there a work around so I deploy an ARM template from the /Azure/Enterprise-Scale github repo.? https://github.com/Azure/Enterprise-Scale
What are some alternatives?
bicep - Bicep is a declarative language for describing and deploying Azure resources
terraform-azurerm-caf-enterprise-scale - Azure landing zones Terraform module
photoprism-auto-index - Photoprism supercharged with originals folder auto indexing
ALZ-Bicep - This repository contains the Azure Landing Zones (ALZ) Bicep modules that help deliver and deploy the Azure Landing Zone conceptual architecture in a modular approach. https://aka.ms/alz/docs
f5-azure-arm-templates - Azure Resource Manager Templates for quickly deploying BIG-IP services in Azure
opnazure - This template allows you to deploy an OPNsense Firewall Azure VM using the opnsense-bootsrtap installation method
protonmail-bridge-docker - ProtonMail IMAP/SMTP Bridge Docker container
TailwindTraders
aks-baseline - This is the Azure Kubernetes Service (AKS) Baseline Cluster reference implementation as produced by the Microsoft Azure Architecture Center.
azure-cli-extensions - Public Repository for Extensions of Azure CLI.
CloudAdoptionFramework - Code samples and extended documentation to support the guidance provided in the Microsoft Cloud Adoption Framework