# Build Azure Maps Workflows in .NET

Building Azure Maps features in .NET requires choosing several prerelease SDKs and authentication patterns. This skill provides focused examples for search, routing, rendering, geolocation, weather, and error handling.

## Install

```bash
npx skillstore add sickn33/azure-maps-search-dotnet
```

## Metadata

- Status: approved
- Slug: sickn33-azure-maps-search-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: aa890566668e6f0be1c637b66cd379037ad547c6bc6cf2ef79e45c0e275e8fa9
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-maps-search-dotnet
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-maps-search-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-maps-search-dotnet/manifest

## Capabilities

- Explains package installation and authentication with subscription keys, Microsoft Entra ID, and shared access signatures.
- Shows address geocoding, batch geocoding, reverse geocoding, and boundary polygon retrieval.
- Covers route directions, traffic options, route matrices, and reachable-range calculations.
- Demonstrates map tile retrieval and file output with the rendering client.
- Provides examples for IP country lookup and current weather conditions.
- Summarizes important SDK types, rate-limit handling, caching, and request error handling.

## Use Cases

- Add Address Search: Create a .NET address lookup flow with confidence checks and reverse geocoding.
- Plan Delivery Routes: Design directions and route-matrix requests for multiple origins and destinations.
- Build Location Dashboards: Combine map tiles, IP country lookup, and weather data for operational views.

## Prompt Templates

### Set Up Authentication

```
Show how to configure Azure Maps Search in a .NET project using Microsoft Entra ID. Include required packages, settings, and validation steps.
```

### Create a Geocoding Flow

```
Design a C# workflow that geocodes an address and checks result confidence. Explain error handling for invalid input, authentication failure, and rate limits.
```

### Build a Route Matrix

```
Plan a .NET route matrix for these origins and destinations: [locations]. Choose synchronous or asynchronous processing and explain the service limits.
```

### Review a Production Architecture

```
Review this Azure Maps .NET design: [design]. Recommend authentication, caching, retries, privacy controls, monitoring, quota management, and tests for each workflow.
```

## Limitations

- Examples reference prerelease SDK versions that may change.
- The skill does not execute requests, provision resources, or validate your Azure configuration.
- An Azure Maps account, credentials, network access, and applicable service quota are required.
- Production applications need additional retries, observability, input validation, privacy controls, and cost management.

## Best Practices

- Prefer Microsoft Entra ID for production and keep subscription keys outside source control.
- Batch requests when appropriate, cache stable results, and apply bounded exponential backoff for rate limits.
- Validate coordinate order, user input, service limits, response confidence, and regional availability before using results.

## Anti Patterns

- Do not embed subscription keys, shared access signatures, or client secrets in code or prompts.
- Do not use synchronous route matrices above documented combination limits.
- Do not treat sample code as production-ready without testing current SDK versions, quotas, failure modes, and privacy requirements.

## Security Audit

- Audited at: 2026-07-23T20:44:13.201\+00:00
- Summary: All 80 static alerts are false positives caused by Markdown formatting, fixed package commands, official reference URLs, and a benign C\# comment. The documentation contains no executable payload, prompt injection, command substitution, suspicious endpoint, or semantic security issue.

## Stats

- Views: 100
- Downloads: 8
- Favorites: 0
- Popularity score: 0