Azure Docs -Add 28 Articles to Azure Docs

[paolosalvatori]

Add 28 new service articles

This PR adds 28 new documentation articles for LocalStack for Azure services. Each article covers a distinct Azure resource type and follows the standard article structure. All az CLI command blocks include a real output block captured from a running LocalStack emulator, with ... used to indicate properties omitted for brevity.

Articles

Service Name	Resource Type	Description
Action Group	Microsoft.Insights/actionGroups	Create and manage action groups used as notification targets in Azure Monitor alerts
API Management	Microsoft.ApiManagement/service	Lifecycle management for API Management service instances (create, show, list, delete)
Application Insights	microsoft.insights/components	Create and inspect Application Insights components for application telemetry and diagnostics
Autoscale Setting	Microsoft.Insights/autoscalesettings	Configure autoscale rules for App Service plans and other scalable Azure resources
Bastion Host	Microsoft.Network/bastionHosts	Provision Azure Bastion hosts for secure browser-based VM access over SSL
Container Instance	Microsoft.ContainerInstance/containerGroups	Provision Azure Container Instance single or multi-container applications
Container Registry	Microsoft.ContainerRegistry/registries	Create registries, push and pull container images using Docker CLI against LocalStack
Cosmos DB	Microsoft.DocumentDB/databaseAccounts	Create Cosmos DB accounts, SQL databases and containers, and MongoDB databases and collections
Data Collection Rules	Microsoft.Insights/dataCollectionRules	Create data collection endpoints, rules, and associations for Azure Monitor telemetry pipelines
Diagnostic Setting	microsoft.insights/diagnosticSettings	Attach diagnostic settings to Azure resources to route logs and metrics to storage or Log Analytics
Front Door	Microsoft.Cdn/profiles	Deploy a Front Door regional load balancer
Function Apps	Microsoft.Web/sites	Deploy and invoke Azure Functions (Python, .NET, Node.js) backed by a local Docker container
Log Analytics	Microsoft.OperationalInsights/workspaces	Create Log Analytics workspaces and query activity logs via saved searches
Metric Alert	microsoft.insights/metricalerts	Create metric-based alert rules targeting Azure resource scopes
Monitor	microsoft.insights/diagnosticSettings	Overview article covering the Azure Monitor emulation surface: diagnostics, activity logs, and storage export
NAT Gateway	Microsoft.Network/natGateways	Provision NAT gateways and associate public IP prefixes for outbound-only network flows
Network Interface	Microsoft.Network/networkInterfaces	Create NICs, attach them to subnets, and manage IP configurations
Private DNS Zone	Microsoft.Network/privateDnsZones	Create private DNS zones, add DNS records, and link zones to virtual networks
Private Endpoint	Microsoft.Network/privateEndpoints	Create private endpoints that expose Azure services on a private subnet
Public IP Address	Microsoft.Network/publicIPAddresses	Allocate and configure static and dynamic public IP addresses
Public IP Prefix	Microsoft.Network/publicIPPrefixes	Reserve a contiguous block of public IP addresses as a prefix
Queue Storage	Microsoft.Storage/queueStorage	Implement Storage Queue
Role Assignment	Microsoft.Authorization/roleAssignments	Assign built-in and custom RBAC roles to managed identities at subscription or resource group scope
Role Definition	Microsoft.Authorization/roleDefinitions	Create and manage custom RBAC role definitions with fine-grained action permissions
Route Table	Microsoft.Network/routeTables	Create route tables, add custom routes, and associate them with subnets
Scheduled Query Rules	microsoft.insights/scheduledqueryrules	Create log-based alert rules that run KQL queries against Log Analytics workspaces
Web Test	microsoft.insights/webtests	Create availability web tests that probe HTTP endpoints on a schedule
Workbook	microsoft.insights/workbooks	Create Azure Monitor workbooks via REST API for custom dashboards and reports

This pull requests also removes the following articles which services are already covered in other articles or postponed (Azure Kubernetes Service and Azure Container Apps):

Name
app.md
authorization.md
azure-container-registry.md
cdn.md
container-service.md
documentdb.md
network.md
operational-insights.md
tables.md
web.md

Article structure

Every article contains the following sections:

• Introduction — What the service is, what it is used for, and a link to the official Microsoft documentation
• Getting started — Step-by-step az CLI commands (including azlocal start-interception / azlocal stop-interception preamble) with one real output block per command
• Features — A bullet list of the operations and capabilities emulated by LocalStack for Azure
• Limitations — What is not emulated (e.g. network packet routing, live telemetry ingestion, Docker requirement for function execution)
• Samples — Links to working code samples in the LocalStack samples repository
• API Coverage — Embedded <AzureFeatureCoverage> component showing the full ARM operation coverage table

Output block conventions

• Every az command is followed by exactly one ```bash title="Output" block
• Output was captured live from a running LocalStack for Azure emulator
• When a response was shortened for readability, ... appears on its own line before the closing } to signal omitted properties

[cloudflare-workers-and-pages]

Deploying localstack-docs with    Cloudflare Pages

Latest commit:	907cf47
Status:	✅  Deploy successful!
Preview URL:	https://8a98cce4.localstack-docs.pages.dev
Branch Preview URL:	https://docs-azure-new-service-artic.localstack-docs.pages.dev

View logs

[remotesynth]

There is no reasonable way to review a PR of this size and given that it is AI generated content, it requires careful review. Please break it into smaller individual PRs.

[paolosalvatori]

@remotesynth as I said on Slack last week, this PR is an exception. In the future, articles will be submitted individually. I could not create 28 separate PRs, one for each article. I work 10-11 hours a day to make the emulator succeed. Breaking this PR down into individual PRs, one for each article, at this stage would require a work day of purely administrative work. If Lazar feels that this is the best use of my time, I can certainly do it, but I don’t see a functional difference between reviewing 28 articles in a single PR versus reviewing 28 separate PRs—other than the significant overhead the latter creates. As I mentioned on Slack, we need to accelerate our documentation efforts for two critical reasons:

• Customer Onboarding: We have already started the private preview. Providing an emulator without documentation is not a viable option for our users.
• Competitive Pressure: A competitor, miniblue.io, launched a few days ago with high-quality documentation. We cannot afford to fall behind.

I have personally verified the commands and content in every article to ensure they are stable and accurate. Given the urgency, I suggest we focus on the content itself so we can get this live for our customers.
cc: @lazarkanelov, @mmaureenliu