infra-azure-data-platform-review

Evaluate Azure data platform architecture for security, governance, connectivity, and cost gaps.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-azure-data-platform-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-azure-data-platform-review
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/group_skills/infra_dataops_group_skills/infra_azure_data_platform_review
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill infra-azure-data-platform-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of designing and validating an Azure-native data platform by translating architecture choices into concrete, secure, and operationally sound configurations.

Core Features & Use Cases

  • ADLS Gen2 foundation review: validate hierarchical namespace, RBAC approach (avoid SAS), versioning/soft delete, and lifecycle tiering (bronze/silver/gold).
  • End-to-end security & identity: map AKS Workload Identity to Azure Managed Identity for service-to-service access, and ensure Key Vault access patterns and network restrictions are correct.
  • Platform component trade-offs: compare Azure Synapse vs Databricks vs HDInsight across orchestration, SQL/Spark capabilities, governance (Purview/Unity Catalog), and cost drivers.
  • Event streaming integration checks: ensure Event Hubs Kafka protocol compatibility and correct authentication practices for producers/consumers.
  • Observability & governance readiness: confirm Azure Monitor/Log Analytics diagnostic settings and Purview registration/scanning/lineage expectations.
  • Private connectivity & cost controls: enforce Private Endpoints for data services and include cost-management guardrails (reserved capacity, spot where appropriate).

Quick Start

Ask the agent to review your proposed Azure data platform design and return a checklist of security, governance, connectivity, and cost gaps with suggested fixes.

Frequently Asked Questions about infra-azure-data-platform-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review and harden my Azure data platform architecture?

To review an Azure data platform, validate ADLS Gen2 hierarchical namespace and RBAC, map AKS Workload Identity to Managed Identity, enforce Key Vault network restrictions, and configure Private Endpoints. This returns a checklist of security, governance, connectivity, and cost gaps with suggested fixes.

What is the best way to secure ADLS Gen2 storage accounts?

Securing ADLS Gen2 requires using hierarchical namespace with RBAC instead of SAS, enabling versioning and soft delete, configuring lifecycle tiering for bronze, silver, and gold layers, and enforcing Private Endpoints for network isolation.

Azure Synapse vs Databricks: how do I choose for my data platform?

Choosing between Azure Synapse and Databricks involves comparing orchestration, SQL and Spark capabilities, governance via Purview or Unity Catalog, and cost drivers. A platform review evaluates these trade-offs against enterprise best practices to recommend the optimal compute component.

Does Event Hubs support Kafka protocol for data ingestion?

Yes, Azure Event Hubs supports Kafka-compatible protocol for streaming ingestion. A platform design review checks Kafka protocol compatibility and validates correct authentication practices for producers and consumers connecting to Event Hubs.

How do I configure AKS Workload Identity for Azure Key Vault access?

Configuring AKS Workload Identity involves mapping Kubernetes service accounts to Azure Managed Identity for service-to-service access. The review validates this mapping and ensures Key Vault access patterns and network restrictions are correctly applied.

What are the limitations of using SAS tokens for ADLS Gen2 access?

Using SAS tokens for ADLS Gen2 access bypasses centralized RBAC controls and complicates revocation. A data platform review identifies this limitation and recommends hierarchical namespace RBAC approach to maintain secure, manageable storage access.