Table of contents

1. Goals
2. Sources
   1. General
   2. Architectures
   3. Custom Management services
3. Concepts
4. Resources naming convention

Goals

This repository has 3 mainly goals :

• Deploy AKS cluster and postgresql to host the Dynamic Inventory Application
• Configure an Azure recipient to deploy resources from the Dynamic Inventory
• Provide a set of guide lines, automation scripts to configure Azure resources.

Used tools in this repository are :

• Ansible
• az-cli
• az powershell module
• Bicep
• Azure devops pipeline

Sources

General

• Hub-sopke network topology : https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/hybrid-networking/hub-spoke?tabs=cli
• Azure limits : https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits
• Azure Management groups : https://learn.microsoft.com/fr-fr/azure/governance/management-groups/overview

Architectures

• Well Architecture Framework : https://learn.microsoft.com/fr-fr/azure/well-architected/what-is-well-architected-framework
• Cloud Adoption Framework guidance : https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/
• Browse architectures : https://learn.microsoft.com/fr-fr/azure/architecture/browse/

Custom Management services

• Inventory API : https://ygo74.github.io/Inventory.API/

Concepts

Start the Azure’s journey by following Microsoft architecture recommendations with the usage of hub/spoke patterns and by segregating permissions granted to automation services accounts:

• Create Root user of Azure subscription : This account is responsible to create the resources groups for expected deployments, provision automation accounts, grant them on their respective resource and manage the Hub virtual networks

• Bootstrap Azure subscription : Deploy the inventory application to manage Azure inventory which is the brain of automation scripts.

• Standard Automation users : These accounts are used to deploy their resources inside their resources groups.

Resources naming convention

Majority of resources have their name which starts with the first letter of resource name’s words. the “-“ is used to split terms in the naming if it is allowed by the Azure’s APIs.

Some exceptions exist:

• Internal decision for short resource’name or because they are part of terms generaly used.
• Azure API rule

---