Last reviewed: April 9, 2025
📘 In this article:
Significant Resources
Significant Resources are Azure resource types that ArchTechLytics actively evaluates and includes in system scoring.
These are the types of resources that meaningfully impact:
- Resiliency
- Security
- Cost
- Performance
- Operational Integrity
🧠 Why It Matters
Not every resource in Azure is critical to architecture analysis.
Significant Resources allow ArchTechLytics to:
- Focus scoring on what’s meaningful
- Ignore “noise” like NSGs or naming-only resources (unless contextually relevant)
- Continuously expand as new Azure services become relevant
📋 Current Examples
Some supported significant resource types include:
Microsoft.Compute/virtualMachines
Microsoft.Web/sites
Microsoft.Sql/servers
Microsoft.Insights/components
Microsoft.OperationalInsights/workspaces
Each is evaluated against its role in the system and the system’s declared criticality.
📊 Not All Significant Resources Are Scored
Just because a resource is significant doesn’t mean it’s scored (yet).
Scoring support requires ArchTechLytics to implement a full set of TechLytics for that resource type. This takes development time and research.
For example:
- Azure Virtual Machines are both significant and scored.
- Key Vaults may be significant (for security posture) but not yet scored if TechLytics aren’t implemented.
📦 Resource Mapping
When a System is defined, you’ll map resources to it. ArchTechLytics will:
- Validate that mapped resources are significant
- Score only those that impact architecture
- Alert you when significant resources are added or removed