feat: enrich Azure Services pages with service details, repo info, and links

Closes #18

- Expanded all 8 service pages with service details, use cases, and architecture notes
- Added repo links, descriptions, and getting started references for services with AzureLocal repos
- Added documentation site links for repos with GitHub Pages sites
- Added Microsoft Learn external references to all pages (all links verified)
- Updated index page with summary table of services, repos, and docs sites
- Added supporting repositories table to index

Author: kristopherjturner

docs/azure-services/aks-on-azure-local.md

@@ -5,24 +5,59 @@ sidebar_position: 3
 
 # Azure Kubernetes Service (AKS) on Azure Local
 
-Azure Kubernetes Service (AKS) is integrated into Azure Local, allowing you to run containerized workloads on-premises with cloud-like management.
+Azure Kubernetes Service (AKS) on Azure Local delivers a fully managed Kubernetes experience on-premises. Clusters are provisioned and managed through Azure Arc, giving teams cloud-consistent container orchestration while keeping workloads, data, and compute within the local infrastructure boundary.
 
-## Overview
-- Native Kubernetes orchestration on Azure Local
-- Managed through Azure Arc and Azure portal
-- Supports hybrid and disconnected operations
+## Service Details
+
+### What It Enables
+
+AKS on Azure Local allows organizations to run production Kubernetes clusters on their own hardware with the same Azure management experience used for cloud-hosted AKS. Cluster lifecycle management — creation, scaling, upgrades, and monitoring — is handled through the Azure portal, CLI, or ARM/Bicep templates via Azure Arc.
+
+### Key Use Cases
+
+- **Cloud-native apps on-premises** — Run containerized microservices architectures in datacenters or edge locations where cloud connectivity is limited or data must remain local
+- **Regulated workloads** — Deploy Kubernetes workloads that must comply with data residency, sovereignty, or air-gapped operation requirements
+- **Edge computing** — Run lightweight Kubernetes clusters at edge sites for real-time processing, analytics, or IoT data aggregation
+- **Developer consistency** — Give development teams the same Kubernetes APIs and tooling (kubectl, Helm, Flux) regardless of whether clusters are in Azure or on-premises
+- **Application modernization** — Containerize legacy workloads and run them on Kubernetes without migrating to the public cloud
+
+### Architecture
+
+- **Azure Arc integration** — AKS clusters on Azure Local are projected into Azure as Arc-connected resources, enabling unified management across cloud and on-premises
+- **Control plane** — Runs locally on Azure Local cluster nodes (no dependency on Azure for workload scheduling)
+- **Networking** — Supports Azure CNI and Calico for pod networking; integrates with existing datacenter networks via load balancers and VLANs
+- **Storage** — Persistent volumes backed by Storage Spaces Direct (S2D) on the Azure Local cluster
+- **Identity** — Microsoft Entra Workload ID and Azure RBAC for cluster access control
 
 ## Supported Features
-- Standard Kubernetes APIs
-- Integration with Azure Monitor and Security
-- GPU and AI workload support (where hardware available)
+
+- Standard Kubernetes APIs (CNCF-conformant)
+- Multi-node and single-node cluster topologies
+- Cluster autoscaling and node pool management
+- Azure Monitor and Container Insights integration
+- Azure Policy for Kubernetes (Gatekeeper)
+- GitOps with Flux v2 (Azure Arc)
+- GPU workload scheduling (where hardware available)
+- Windows and Linux node pools
 
 ## Deployment Notes
-- Requires Azure Local infrastructure (Stack HCI/Hub/Edge)
-- See Microsoft’s AKS on Azure Local deployment documentation
+
+- Requires Azure Local infrastructure (Azure Stack HCI 23H2+ recommended)
+- Clusters are provisioned via Azure Arc; an Azure subscription is required
+- Minimum 8 GB RAM and 4 vCPUs per worker node recommended
+- Storage classes map to S2D volumes on the Azure Local cluster
 
 ## Limitations
-- Some Azure cloud integrations may be limited
+
+- Some AKS cloud add-ons (e.g., Virtual Nodes, KEDA with Azure Event sources) may not be available on-premises
+- Azure Container Registry integration requires network connectivity to Azure
+- Cluster upgrades follow the Arc-connected Kubernetes lifecycle, which may lag behind cloud AKS versions
 - Hardware and licensing requirements apply
 
-> Data verified with Microsoft Azure Local documentation, February 2026.
+## External References
+
+- [AKS on Azure Local overview — Microsoft Learn](https://learn.microsoft.com/azure/aks/hybrid/aks-hybrid-options-overview)
+- [Deploy AKS clusters on Azure Local — Microsoft Learn](https://learn.microsoft.com/azure/aks/hybrid/aks-create-clusters-portal)
+- [Azure Arc-enabled Kubernetes — Microsoft Learn](https://learn.microsoft.com/azure/azure-arc/kubernetes/overview)
+
+> Data verified with Microsoft Azure Local documentation, March 2026.

docs/azure-services/app-services-on-azure-local.md

@@ -5,24 +5,57 @@ sidebar_position: 4
 
 # Azure App Services on Azure Local
 
-Azure App Services enables you to host web apps and APIs directly on Azure Local infrastructure, providing cloud-native capabilities on-premises.
+Azure App Services on Azure Local extends the platform-as-a-service (PaaS) experience to on-premises infrastructure. Organizations can host web applications, REST APIs, and background services using the same App Service programming model and deployment workflows used in Azure — while keeping application compute and data within their local environment.
 
-## Overview
-- Host web applications and APIs locally
-- Managed through Azure portal and APIs
-- Supports hybrid and disconnected scenarios
+## Service Details
+
+### What It Enables
+
+App Services on Azure Local runs on a Kubernetes cluster (AKS on Azure Local) with the App Service extension installed via Azure Arc. This provides a fully managed application hosting platform on-premises, with built-in scaling, deployment slots, and CI/CD integration.
+
+### Key Use Cases
+
+- **Internal line-of-business apps** — Host corporate web applications on-premises with cloud-grade management and deployment automation
+- **Data-sensitive APIs** — Run APIs that process regulated or sensitive data without sending it to the cloud
+- **Hybrid app modernization** — Migrate legacy IIS/.NET workloads to the App Service model while keeping them on-premises during the transition
+- **Edge-hosted applications** — Deploy lightweight web frontends or API gateways at edge sites that serve local users or devices
+
+### Architecture
+
+- **App Service Kubernetes environment** — An Arc-enabled AKS cluster with the App Service extension deployed
+- **Control plane** — Azure manages the App Service configuration; the Kubernetes extension handles local orchestration
+- **Scaling** — Built-in horizontal scaling within the AKS cluster resource limits
+- **Networking** — Applications are exposed via Kubernetes ingress on the local network; external access configurable through network infrastructure
+- **Storage** — Persistent storage backed by the AKS cluster's storage classes (S2D on Azure Local)
 
 ## Supported Features
-- .NET, Java, Node.js, PHP, Python support
-- Integration with local and hybrid storage
-- Built-in scaling and security features
+
+- .NET, Java, Node.js, PHP, Python, and custom container runtimes
+- Deployment slots for staged rollouts
+- CI/CD integration with GitHub Actions and Azure DevOps
+- Custom domains and TLS certificates
+- App settings and connection string management
+- Built-in authentication (Easy Auth)
+- Application Insights integration
 
 ## Deployment Notes
-- Requires Azure Local infrastructure (Stack HCI/Hub/Edge)
-- See Microsoft’s App Services on Azure Local deployment documentation
+
+- Requires AKS on Azure Local with the App Service extension installed via Azure Arc
+- Azure subscription required for the Arc-connected App Service environment
+- DNS and ingress configuration needed for application endpoints
+- Minimum cluster sizing depends on the number and resource requirements of hosted applications
 
 ## Limitations
-- Some Azure cloud integrations may be limited
+
+- Some cloud App Service features (e.g., Azure Functions Consumption plan, some managed integrations) are not available on-premises
+- Custom domains require manual DNS configuration on the local network
+- Auto-scaling is limited to the available compute capacity on the AKS cluster
 - Hardware and licensing requirements apply
 
-> Data verified with Microsoft Azure Local documentation, February 2026.
+## External References
+
+- [App Service on Azure Arc — Microsoft Learn](https://learn.microsoft.com/azure/app-service/overview-arc-integration)
+- [Set up Azure App Service on Azure Arc — Microsoft Learn](https://learn.microsoft.com/azure/app-service/manage-create-arc-environment)
+- [AKS on Azure Local — Microsoft Learn](https://learn.microsoft.com/azure/aks/hybrid/aks-hybrid-options-overview)
+
+> Data verified with Microsoft Azure Local documentation, March 2026.

docs/azure-services/avd-on-azure-local.md

@@ -5,25 +5,84 @@ sidebar_position: 2
 
 # Azure Virtual Desktop (AVD) on Azure Local
 
-Azure Virtual Desktop (AVD) can run on Azure Local infrastructure, enabling organizations to deliver Windows desktops and applications from their own datacenter or edge locations.
+Azure Virtual Desktop (AVD) on Azure Local enables organizations to deliver full Windows desktops and RemoteApp sessions from their own datacenter, edge, or sovereign locations — without routing user traffic through the public cloud. Session hosts run as VMs on Azure Local clusters, while the AVD control plane in Azure handles brokering, diagnostics, and gateway services.
 
-## Overview
-- Run Windows desktops and apps locally
-- Managed via Azure portal and APIs
-- Supports hybrid and disconnected scenarios
+## Service Details
+
+### What It Enables
+
+AVD on Azure Local brings cloud-managed virtual desktops to on-premises infrastructure. User sessions run locally on Azure Local cluster nodes, keeping desktop compute and data within the physical boundary of the organization while still leveraging Azure for identity, management, and monitoring.
+
+### Key Use Cases
+
+- **Data sovereignty and compliance** — Keep user sessions and profile data on-premises to satisfy regulatory requirements (healthcare, government, finance)
+- **Low-latency desktops** — Deliver responsive desktop experiences for users co-located with the infrastructure, eliminating round-trip latency to cloud regions
+- **Branch office and edge** — Provide managed desktops at remote sites without dedicated VDI infrastructure at each location
+- **Hybrid workforce** — Combine cloud-hosted and on-premises session hosts in a single AVD host pool for flexible capacity
+
+### Architecture
+
+AVD on Azure Local uses a hybrid architecture:
+
+- **Control plane** — Hosted in Azure; handles connection brokering, gateway, diagnostics, and web client access
+- **Session hosts** — Windows VMs running on Azure Local cluster nodes, registered to AVD host pools via Azure Arc
+- **User profiles** — Stored on local SMB shares (typically a Scale-Out File Server with FSLogix profile containers)
+- **Identity** — Microsoft Entra ID (Azure AD) with optional hybrid join for on-premises Active Directory integration
+- **Networking** — User traffic flows directly to session hosts on the local network; only control-plane signaling traverses the internet
 
 ## Supported Features
-- Multi-session Windows 10/11
-- App streaming
-- Integration with Azure Active Directory
-- Local and hybrid storage options
+
+- Multi-session Windows 10/11 Enterprise
+- Single-session personal desktops
+- RemoteApp streaming
+- FSLogix profile containers on local storage
+- Microsoft Entra ID and hybrid AD join
+- Azure Monitor and Log Analytics integration
+- Conditional Access and MFA
+- Multimedia redirection and Teams optimization
+
+## Repository: azurelocal-avd
+
+The [`AzureLocal/azurelocal-avd`](https://github.com/AzureLocal/azurelocal-avd) repository provides infrastructure-as-code templates and automation for deploying AVD session hosts on Azure Local.
+
+**What's in the repo:**
+
+- **Bicep, ARM, Terraform, PowerShell, and Ansible** templates for deploying AVD infrastructure
+- Centralized variable configuration (`config/variables.yml`)
+- Pipeline examples for GitHub Actions and Azure DevOps
+- Validation and test scripts
+
+**Getting started:** Clone the repo, copy `config/variables.example.yml` to `config/variables.yml`, configure your environment values, and deploy with your preferred tooling. See the repo [README](https://github.com/AzureLocal/azurelocal-avd#readme) for full instructions.
+
+### Documentation Site
+
+Full deployment documentation, architecture guides, and scenario walkthroughs are published at:
+**[azurelocal.github.io/azurelocal-avd](https://azurelocal.github.io/azurelocal-avd/)**
+
+### Companion: SOFS for FSLogix
+
+AVD session hosts need a performant storage layer for user profiles. The companion repository [`AzureLocal/azurelocal-sofs-fslogix`](https://github.com/AzureLocal/azurelocal-sofs-fslogix) automates deployment of a three-node Scale-Out File Server cluster on Azure Local to host FSLogix profile containers.
+
+- Docs site: [azurelocal.github.io/azurelocal-sofs-fslogix](https://azurelocal.github.io/azurelocal-sofs-fslogix/)
 
 ## Deployment Notes
-- Requires Azure Local infrastructure (Stack HCI/Hub/Edge)
-- Follow Microsoft’s AVD on Azure Local deployment guide
+
+- Requires Azure Local infrastructure (Azure Stack HCI 23H2+ recommended)
+- Session hosts must be Arc-enabled and registered to an AVD host pool
+- FSLogix profile storage should be provisioned on local SMB shares (see SOFS companion above)
+- Azure subscription required for the AVD control plane
 
 ## Limitations
-- Some cloud-only features may not be available
-- Licensing and hardware requirements apply
 
-> Data verified with Microsoft Azure Local documentation, February 2026.
+- Cloud-only features such as Azure Files–backed profiles require connectivity to Azure storage
+- Start VM on Connect requires persistent Azure connectivity for the control plane
+- GPU-accelerated sessions depend on physical GPU passthrough or DDA support on cluster nodes
+- Licensing: Windows Enterprise multi-session requires Microsoft 365 or per-user AVD access rights
+
+## External References
+
+- [Azure Virtual Desktop on Azure Local — Microsoft Learn](https://learn.microsoft.com/azure/virtual-desktop/azure-stack-hci-overview)
+- [Deploy AVD session hosts on Azure Local — Microsoft Learn](https://learn.microsoft.com/azure/virtual-desktop/deploy-azure-virtual-desktop)
+- [FSLogix profile containers — Microsoft Learn](https://learn.microsoft.com/fslogix/overview-what-is-fslogix)
+
+> Data verified with Microsoft Azure Local documentation, March 2026.

docs/azure-services/disconnected-operations-on-azure-local.md

@@ -5,24 +5,61 @@ sidebar_position: 9
 
 # Disconnected Operations on Azure Local
 
-Azure Local supports fully disconnected operations, enabling organizations to meet data residency and regulatory requirements by running workloads without a persistent cloud connection.
+Azure Local supports fully disconnected and intermittently connected operations, enabling organizations to run Azure-managed infrastructure in environments where persistent cloud connectivity is not available, not permitted, or unreliable. Workloads continue to run locally with full functionality while the cluster operates independently of Azure.
 
-## Overview
-- Operate Azure Local infrastructure in fully disconnected mode
-- Maintain local control plane and management
-- Supports critical workloads in regulated environments
+## Service Details
+
+### What It Enables
+
+Disconnected operations mode allows Azure Local clusters to function without a persistent connection to Azure. The local control plane manages VMs, containers, storage, and networking independently. When connectivity is restored (or during scheduled sync windows), telemetry, billing, and management data synchronize with Azure.
+
+### Key Use Cases
+
+- **Classified and sovereign environments** — Run Azure-managed infrastructure in air-gapped networks where no internet connectivity is permitted (defense, intelligence, critical government systems)
+- **Remote and austere locations** — Operate clusters at sites with unreliable or no network connectivity (mining, maritime, oil rigs, field hospitals)
+- **Regulatory compliance** — Meet data residency requirements that mandate all compute, storage, and management remain within a physical boundary
+- **Disaster resilience** — Ensure workloads continue operating during extended network outages without degradation
+- **Edge retail and manufacturing** — Run store or factory clusters that must operate independently when WAN links are unavailable
+
+### Architecture
+
+- **Local control plane** — Azure Local retains a fully functional local management stack; Hyper-V, S2D, failover clustering, and SDN operate independently of Azure
+- **Azure Arc (when connected)** — Arc agents report health, sync policy, and upload telemetry during connectivity windows
+- **Identity** — Local Active Directory provides authentication when Entra ID is unreachable; hybrid join resumes when connectivity is restored
+- **Updates** — Managed locally via WSUS or SCCM; Azure Update Management synchronizes when connected
+- **Billing** — Usage data is cached locally and reported to Azure during the next sync window
 
 ## Supported Features
-- Local management and monitoring
-- Data residency and sovereignty
-- Resilient operations during network outages
+
+- Full VM and container workload execution without cloud connectivity
+- Local failover clustering and high availability
+- Storage Spaces Direct with local resilience (mirror, parity)
+- SDN-based networking and micro-segmentation
+- Local monitoring and alerting (Windows Admin Center, SCOM)
+- Periodic Azure Arc synchronization when connectivity is available
+- Cached billing and compliance reporting
+- Support for intermittently connected and fully air-gapped deployment models
 
 ## Deployment Notes
-- Requires Azure Local infrastructure (Stack HCI, Hub, Edge)
-- See Microsoft’s documentation for disconnected operations on Azure Local
+
+- Initial cluster deployment and Arc registration require temporary connectivity to Azure
+- Plan for local identity infrastructure (Active Directory domain controllers on-site)
+- Configure local update infrastructure (WSUS/SCCM) for patching in disconnected mode
+- Define sync windows and procedures for periodic Azure connectivity (unless fully air-gapped)
+- Consider Windows Admin Center for local cluster management when Azure portal is unreachable
 
 ## Limitations
-- Some Azure cloud services/features unavailable when disconnected
+
+- Azure portal management is unavailable when disconnected; local tools (Windows Admin Center, PowerShell) must be used
+- Azure Arc policy enforcement and compliance reporting pause until connectivity is restored
+- Some Azure services that require constant cloud connectivity (e.g., Azure Monitor real-time streaming) are unavailable while disconnected
+- Extended disconnection periods may affect license validation and Azure subscription status
 - Hardware and licensing requirements apply
 
-> Data verified with Microsoft Azure Local documentation, February 2026.
+## External References
+
+- [Azure Local overview — Microsoft Learn](https://learn.microsoft.com/azure-stack/hci/overview)
+- [Azure Arc connectivity modes — Microsoft Learn](https://learn.microsoft.com/azure/azure-arc/servers/network-requirements)
+- [Azure Local overview — Microsoft Learn](https://learn.microsoft.com/azure-stack/hci/overview)
+
+> Data verified with Microsoft Azure Local documentation, March 2026.