azure-resource-manager-mysql-dotnet
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-resource-manager-mysql-dotnet" from https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-resource-manager-mysql-dotnet/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-resource-manager-mysql-dotnet". Plan a secure production server for an internal application.
Expected outcome:
- Use a General Purpose SKU sized from measured workload demand.
- Use private networking and avoid the Azure-wide firewall rule.
- Enable zone-redundant high availability and tested backup retention.
- Prefer Entra ID authentication and managed identities.
Using "azure-resource-manager-mysql-dotnet". Explain a point-in-time restore workflow.
Expected outcome:
Select the source server and validated restore timestamp, create a separate restored server, verify data and connectivity, then switch consumers deliberately.
Using "azure-resource-manager-mysql-dotnet". Review a server scaling change.
Expected outcome:
Confirm regional SKU availability, storage limits, expected interruption, maintenance timing, rollback options, monitoring thresholds, and post-change validation.
Security Audit
Medium RiskMost 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.
Confirmed security concerns (1)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (9)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-resource-manager-mysql-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-resource-manager-mysql-dotnet.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-resource-manager-mysql-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-resource-manager-mysql-dotnet-2026,
author = {sickn33},
title = {azure-resource-manager-mysql-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-resource-manager-mysql-dotnet security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-resource-manager-mysql-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-resource-manager-mysql-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Show the minimal .NET setup for Azure.ResourceManager.MySql using DefaultAzureCredential. List required packages and required Azure inputs.
Design a .NET workflow to create an Azure MySQL Flexible Server in [region] with [SKU], [storage], backups, and a database.
Review my Azure MySQL Flexible Server design for least privilege, private networking, Entra ID, backup retention, and high availability. Identify unsafe defaults.
Create an advanced .NET migration plan from [source] to Azure MySQL Flexible Server. Include staged provisioning, validation, restore testing, rollback, monitoring, and cleanup.
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.
Avoid
- 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.