# Manage Azure MySQL Flexible Server with .NET

Azure MySQL management requires precise SDK types, authentication, and lifecycle operations. This skill provides focused .NET patterns for common Flexible Server tasks.

## Install

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

## Metadata

- Status: approved
- Slug: sickn33-azure-resource-manager-mysql-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: a87875edfb3ec5b925524c682db0b0a45689492afd79250d4d6a33f0e9f422b0
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-resource-manager-mysql-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, filesystem
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-resource-manager-mysql-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-resource-manager-mysql-dotnet/manifest

## Capabilities

- Shows package setup and DefaultAzureCredential authentication for the Azure Resource Manager SDK.
- Guides Flexible Server creation with compute, storage, backup, availability zone, and high-availability settings.
- Demonstrates database, firewall, server parameter, and Entra ID administrator management.
- Covers server listing, scaling, stopping, starting, restarting, and deletion.
- Explains backup discovery, point-in-time restore, error handling, and token-based connections.

## Use Cases

- Provision a Development Server: Create a practical .NET provisioning flow with suitable compute, storage, backups, and database settings.
- Standardize Production Configuration: Review high availability, firewall, Entra ID, backup retention, and server parameter choices before deployment.
- Automate Database Operations: Build lifecycle, scaling, restore, and inventory routines using Azure Resource Manager resource types.

## Prompt Templates

### Set Up Authentication

```
Show the minimal .NET setup for Azure.ResourceManager.MySql using DefaultAzureCredential. List required packages and required Azure inputs.
```

### Create a Flexible Server

```
Design a .NET workflow to create an Azure MySQL Flexible Server in [region] with [SKU], [storage], backups, and a database.
```

### Review Production Security

```
Review my Azure MySQL Flexible Server design for least privilege, private networking, Entra ID, backup retention, and high availability. Identify unsafe defaults.
```

### Plan a Resilient Migration

```
Create an advanced .NET migration plan from [source] to Azure MySQL Flexible Server. Include staged provisioning, validation, restore testing, rollback, monitoring, and cleanup.
```

## Limitations

- Provides guidance and examples but does not execute Azure operations independently.
- Requires valid Azure credentials, permissions, subscription details, and environment-specific resource names.
- Focuses on MySQL Flexible Server and does not cover deprecated MySQL Single Server.
- Examples require security, cost, networking, and compliance review before production use.

## Best Practices

- Use DefaultAzureCredential with managed identity and assign only required Azure roles.
- Prefer private networking, narrow firewall rules, zone-redundant availability, and tested backups for production.
- Validate SDK versions, regional capabilities, quotas, costs, and operation results in a nonproduction environment.

## Anti Patterns

- Do not embed passwords, tokens, subscription identifiers, or tenant identifiers in source code.
- Do not use the 0.0.0.0 Azure-wide firewall rule without explicit risk acceptance.
- Do not delete, scale, restart, or restore production servers without validation and a rollback plan.

## Security Audit

- Audited at: 2026-07-23T22:21:52.721\+00:00
- Summary: Most static findings are false positives caused by Markdown fences, inline code, documentation links, placeholders, and an OAuth scope. The Azure-wide firewall example is a confirmed exposure risk, and the hardcoded password example is an additional medium-severity concern.

## Stats

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