Azure Design Document

I couldn’t find a proper design document template for Azure projects when searched in the internet, so I thought better I’ll make a reference design template for solutions based on Azure cloud.

Solution Architecture

  1. Solution Diagrams using latest approved Azure icons.

Sample Diagram (Image owned by Microsoft Corporation)

  • General overview of solution architecture, Azure services and Non-Azure services used. (Example Function App, API, Azure AD, Front Door, Storage Account etc.)
  • Decision factors behind using specific services.

Network Architecture

  1. Solution communication flow between the components and other systems which are integrated
  2. Whitelisting of certain IPs as access to the public end points of the resources will be restricted from Internet
  3. Source and Destination communication matrix

Sample Diagram (Image owned by Microsoft Corporation)

Storage Architecture

  1. Whether Storage is a Database in IaaS, or as a PaaS service like Azure SQL DB, Cosmos DB, Storage account etc.
  2. Architecture Diagram of the Storage

Sample Diagram (Image owned by Microsoft Corporation)

Backup and Disaster Recovery Architecture

  1. Sample Diagram (Image owned by Microsoft Corporation)

Security Architecture

  1. Details on securing the solution at Network Level – using Azure services or third-party products. (Example Firewall, WAF, Application gateway etc.) need to be detailed.
  2. Details on securing the data of the solution– (Example: Data in transit, data at Rest, data encryption, masking etc.) need to be detailed.
  3. Details on Identity and Access Requirements for all the components used in the solution architecture – RBAC (at all levels of the enterprise from network access control at the device level, database access control at the data level, application level access control, as well as user access), SPN, Key Vaults, Access Keys etc.
  4. Certificate Requirements

Sample Diagram (Image owned by Microsoft Corporation)

Environment Details

  1. Resources and their specifications along with cost is required in Production Azure Subscription.
  2. Resources and their specifications along with cost is required in Staging Azure Subscription.
  3. Resources and their specifications along with cost is required in DevTest Azure Subscription.

Sample Table:

Service typeQuantityRegionDescription
Container Registry1West EuropeStandard Tier, 5 units x 30 days, 5 GB Bandwidth, 0 GB Extra Storage
Storage Accounts1West EuropeFile Storage, Premium Performance Tier, LRS Redundancy, 100 GB Capacity, 100 GB Snapshots
Azure Database for MySQL1West EuropeMemory Optimized Tier, 1 Gen 5 (4 vCore), 1 year reserved, 5 GB Storage, 100 GB Additional Backup storage – LRS redundancy
Notification Hubs1West EuropeFree tier
App Service (Two slots for web app)1West EuropePremium V2 Tier; 2 P3V2 (4 Core(s), 14 GB RAM, 250 GB Storage) x 730 Hours; Linux OS
App Service (Two slots for Cron jobs)1West EuropePremium V2 Tier; 2 P3V2 (4 Core(s), 14 GB RAM, 250 GB Storage) x 730 Hours; Linux OS

Monitoring Architecture

  1. Azure Monitoring
  2. Log Analytics
  3. Application Insights
  4. Diagnostic settings

Sample Diagram (Image owned by Microsoft Corporation):

Deployment Architecture

  1. ARM template, PS, DSC, CLI etc. (Deployment using Azure Portal is not accepted)
  2. DevOps – Repos, Service Connection, Build and Release Pipelines.
  3. Slots for Prod and Pre-Prod.

Sample Diagram (Image owned by Microsoft Corporation)

Integrations

  1. Integration with other systems
  2. Source and Destination communication matrix

Sample Diagram (Image owned by Microsoft Corporation)

Assumptions and Considerations

  1. Existing NGFW and WAF will be used for the solution
  2. Sentinel will be used as security information event management (SIEM) and security orchestration automated response (SOAR) solution

Appendix

  1. Asset naming convention document
  2. Asset reference document
  3. Tagging convention document

Leave a Reply

Your email address will not be published. Required fields are marked *