skills.rest
TheViziusGroup
TheViziusGroupOFFICIAL
Explore all skills by this author →
WebsiteGitHub

azure-services-catalog

Guides Azure service selection and production configuration across compute, messaging, networking, databases, and AI.

1|Updated Aug 10, 2026
Search Tags:#migration#azure#cost optimization#cloud architecture#service selection#aks#cosmos db
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill azure-services-catalog-theviziusgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: azure-services-catalog
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/azure-cloud-infra/skills/azure-services-catalog
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill azure-services-catalog-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing among Azure's overlapping services (Container Apps vs AKS vs Functions, Service Bus vs Event Hubs vs Event Grid, hub-spoke vs Virtual WAN) is error-prone, and wrong early decisions create costly re-architecture, outages, and surprise bills. ## Core Features & Use Cases - Decision Frameworks: Provides preference orders and comparison tables for compute, messaging, networking, storage redundancy, and databases, including crossover thresholds like the ~30-spoke hub-spoke to Virtual WAN tipping point. - Production Configuration Guidance: Covers AKS networking models, Cosmos DB partition-key design, Functions Flex Consumption, private endpoints, storage lifecycle tiers, and PTU vs pay-as-you-go for AI workloads. - Cost, Identity, and Retirements: Details Reservations/Savings Plans/Spot layering, managed identities and Zero Trust, Bicep vs Terraform, and 2024-2026 service retirements such as Azure AD B2C and the Log Analytics agent. - Use Case: When planning a new Azure landing zone or migrating workloads, ask which compute, messaging, and database services fit each workload and receive a staged production roadmap with concrete configuration defaults. ## Quick Start Ask the assistant to recommend Azure compute, messaging, and database services for a new multi-region SaaS application using this skill.

Frequently Asked Questions about azure-services-catalog

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

FAQPage Schema
How do I choose between Azure Container Apps and AKS?▼

Azure Container Apps is the default for container workloads, offering scale-to-zero and no control-plane management. Choose AKS only when you need direct Kubernetes API access, custom service mesh, node-level control, or strict multi-workload isolation.

What is the difference between Service Bus, Event Hubs, and Event Grid?▼

Service Bus handles transactional messages with FIFO sessions and dead-lettering, Event Hubs ingests high-volume telemetry streams with a Kafka-compatible endpoint, and Event Grid provides reactive pub/sub notifications without ordering guarantees. They are complementary and often used together.

When should I use Virtual WAN instead of hub-spoke networking?▼

Switch to Virtual WAN at roughly 2-3 active regions or around 30 spokes, or when branch and SD-WAN connectivity at scale is needed. Hub-spoke gives more routing control and lower cost at small scale.

Does Cosmos DB fit every NoSQL workload on Azure?▼

No. Cosmos DB should be reserved for genuine global-distribution or flexible-schema needs because it is expensive and unforgiving when misused. Partition key selection is the top performance lever, and scale failures are almost always design failures.

Which Azure services are being retired in 2024-2026?▼

The Log Analytics agent retired in November 2024, Azure AD B2C stopped new sales in May 2025 with migration to Entra External ID recommended, AzureAD/MSOnline PowerShell is retiring, and Prompt Flow retires April 2027 in favor of Microsoft Agent Framework.

Should I use Bicep or Terraform for Azure infrastructure as code?▼

Both are production-ready; standardize on one. Bicep suits Azure-only teams with day-0 feature support and no state file, while Terraform fits multi-cloud environments with a mature provider ecosystem but requires state management.

Related Skills

Explore More Software Engineering Skills→
JaviMontanoJaviMontano

cloud-migration

Plan cloud migrations with 7R classification, wave sequencing, landing zone design, and cutover runbooks.

Community
Advanced
MayaDispelerMayaDispeler
3

azure-architecture

Design Azure landing zones with Bicep, Terraform, and Azure Policy.

Community
Advanced
DCx7C5DCx7C5

cloud-SKILL.md

Aggregate cloud misconfigurations from AWS Security Hub, Azure Defender, and open-source tools.

Community
Advanced
EmmraanEmmraan

multi-cloud-architecture-design

Design unified multi-cloud architecture frameworks across AWS, GCP, and Azure.

Community
Advanced