azure-resource-manager-sql-dotnet
Manage Azure SQL with .NET ARM SDK
Azure SQL management tasks require correct ARM SDK types, authentication, and long-running operation handling. This skill provides .NET examples for servers, databases, elastic pools, firewall rules, and connection settings.
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-sql-dotnet" from https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-resource-manager-sql-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-sql-dotnet". I need to create an S0 Azure SQL database in an existing server.
Expected outcome:
- Confirm subscription, resource group, server, region, database name, and SKU.
- Use the server database collection and wait for the create or update operation to finish.
- Review firewall access before testing client connectivity.
Using "azure-resource-manager-sql-dotnet". I want several low-traffic databases to share capacity.
Expected outcome:
- Use an elastic pool when databases have variable or shared demand.
- Choose a pool tier and capacity before assigning databases.
- Track per-database minimum and maximum capacity limits.
Using "azure-resource-manager-sql-dotnet". I am unsure which Azure SQL SDK to use.
Expected outcome:
Use Azure.ResourceManager.Sql for provisioning and configuration. Use Microsoft.Data.SqlClient for queries, transactions, and application data access.
Security Audit
Medium RiskMost command findings are false positives caused by Markdown code fences and inline code, not executable Ruby backticks. The 0.0.0.0 Azure SQL firewall example is a real network exposure risk, and the public access sample adds related cloud configuration risk. No prompt injection, exfiltration intent, or malicious execution flow was found.
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 (4)
🔑 Env variables (3)
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-sql-dotnet/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-resource-manager-sql-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-resource-manager-sql-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-sql-dotnet security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet/audits/6BibTeX citation
@techreport{sickn33-sickn33-azure-resource-manager-sql-dotnet-2026,
author = {sickn33},
title = {azure-resource-manager-sql-dotnet security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet/audits/6},
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-sql-dotnet security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-azure-resource-manager-sql-dotnet/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-azure-resource-manager-sql-dotnet:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prototype Azure SQL provisioning
Build a small .NET workflow that creates a server, database, and basic resource settings.
Standardize SQL resource operations
Create repeatable ARM SDK patterns for databases, elastic pools, firewall rules, and error handling.
Review SDK boundaries
Decide when to use Azure.ResourceManager.Sql instead of data plane SQL libraries.
Try These Prompts
Show me how to create an Azure SQL server with Azure.ResourceManager.Sql and DefaultAzureCredential. Include required inputs and safety notes.
Help me add an Azure SQL database to an existing server using the .NET ARM SDK. Explain SKU choices and long-running operations.
Design an Azure.ResourceManager.Sql workflow for creating an elastic pool and adding databases. Include capacity considerations and rollback steps.
Review my Azure SQL ARM SDK deployment plan for production. Focus on identity, private networking, firewall scope, idempotency, and error handling.
Best Practices
- Use DefaultAzureCredential and avoid placing secrets in source files or prompts.
- Prefer private networking and narrowly scoped firewall rules for production databases.
- Handle RequestFailedException and make create or update operations idempotent.
Avoid
- Do not copy broad firewall examples into production without security review.
- Do not place SQL admin passwords in prompts, logs, or source control.
- Do not use the management plane SDK for querying or modifying table data.