# Manage Azure Redis Resources with .NET

Azure Redis management requires correct SDK types, authentication, and long-running operation handling. This skill provides focused .NET guidance for common resource workflows.

## Install

```bash
npx skillstore add sickn33/azure-resource-manager-redis-dotnet
```

## Metadata

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

## Capabilities

- Explains package installation and authentication with DefaultAzureCredential.
- Shows how to create, retrieve, update, and delete Redis cache resources.
- Covers firewall rules, patch schedules, SKU selection, and TLS configuration.
- Demonstrates RDB import and export through Azure Blob Storage.
- Shows access-key retrieval, rotation, and StackExchange.Redis connection setup.
- Provides ARM error-handling patterns and common provisioning constraints.

## Use Cases

- Provision a Development Cache: Create a secure cache configuration with an appropriate SKU, TLS settings, tags, and asynchronous operation handling.
- Standardize Redis Operations: Prepare repeatable workflows for updates, firewall rules, maintenance schedules, backups, and key rotation.
- Review Production Readiness: Check authentication, networking, secret handling, error management, and premium feature requirements before deployment.

## Prompt Templates

### Set Up the SDK

```
Show the packages and minimal .NET setup for Azure Resource Manager Redis authentication. Use DefaultAzureCredential and never print secrets.
```

### Create a Secure Cache

```
Create a .NET workflow for a Standard Azure Redis cache in East US. Require TLS 1.2, disable non-SSL, and add environment tags.
```

### Configure Production Controls

```
Design .NET management steps for private firewall ranges, a weekend patch schedule, robust RequestFailedException handling, and idempotent updates.
```

### Plan an Advanced Migration

```
Plan a Premium cache migration with RDB transfer, key rotation, asynchronous polling, validation, rollback, and strict secret redaction.
```

## Limitations

- Provides guidance and examples but does not execute Azure operations.
- Focuses on management-plane tasks; most cache data operations require StackExchange.Redis.
- SDK versions, Azure APIs, and service availability can change after publication.
- Destructive operations and credential-handling examples require explicit review before use.

## Best Practices

- Use DefaultAzureCredential with least-privilege Azure roles and managed identity where available.
- Require TLS 1.2, disable non-SSL access, and restrict firewall ranges.
- Redact access keys, review destructive changes, and test long-running operations before production.

## Anti Patterns

- Do not print Redis access keys or place SAS tokens in source code.
- Do not use the management SDK for normal cache data operations.
- Do not assume Premium-only features work on Basic or Standard SKUs.

## Security Audit

- Audited at: 2026-07-23T22:35:17.849\+00:00
- Summary: The 58 external-command alerts are Markdown formatting and documentation, while credential environment variables and private network values are placeholders. The hardcoded SAS URI example is unsafe, and console output of Redis access keys creates a high-severity credential exposure risk. No prompt injection or malicious intent was found.

## Stats

- Views: 106
- Downloads: 10
- Favorites: 0
- Popularity score: 0