Skills azure-identity-dotnet
๐Ÿ“ฆ

azure-identity-dotnet

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ”‘ Env variables

Configure Azure Identity for .NET

Azure authentication choices vary across local development and hosted workloads. This skill provides focused Azure Identity patterns for secure .NET client configuration.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "azure-identity-dotnet" from https://skillstore.io/skills/sickn33-azure-identity-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-identity-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-identity-dotnet". Choose authentication for a .NET API running in Azure App Service and on developer laptops.

Expected outcome:

  • Development: use DefaultAzureCredential so approved developer tools can authenticate.
  • Production: use the App Service managed identity through ManagedIdentityCredential.
  • Reuse one credential instance and grant only required Azure roles.

Using "azure-identity-dotnet". Review a service principal setup that stores a client secret in source control.

Expected outcome:

The review rejects source-controlled secrets, recommends managed identity, and lists required role, deployment, rotation, and validation steps.

Using "azure-identity-dotnet". Explain why DefaultAzureCredential works locally but fails in an Azure workload.

Expected outcome:

  • Confirm which local developer credential succeeds.
  • Verify that the Azure resource has an enabled managed identity.
  • Check identity selection, role assignments, endpoint configuration, and authentication logs.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All 81 static findings are false positives from Markdown formatting, documented package commands, sample credentials, placeholder endpoints, and official links. No executable script, prompt injection, secret exfiltration, or unsafe command construction appears.

1
Files scanned
349
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-azure-identity-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-identity-dotnet/security.svg)](https://skillstore.io/skills/sickn33-azure-identity-dotnet?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-identity-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-identity-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-identity-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-identity-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-identity-dotnet/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-identity-dotnet-2026, author = {sickn33}, title = {azure-identity-dotnet security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-identity-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-identity-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-identity-dotnet/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-identity-dotnet:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Local .NET Development

Choose developer credentials and configure DefaultAzureCredential for an application that uses Azure SDK clients.

Azure-Hosted Workloads

Select managed identity patterns for App Service, Functions, virtual machines, or Azure Kubernetes Service.

Enterprise Authentication Review

Compare service principal, certificate, sovereign cloud, and deterministic production credential options.

Try These Prompts

Install Azure Identity
Show how to add Azure.Identity to a .NET project and authenticate one BlobServiceClient with DefaultAzureCredential. Use placeholder endpoints.
Configure Development and Production
Design a .NET approach that uses DefaultAzureCredential locally and managed identity in Azure. Explain the required configuration.
Integrate Dependency Injection
Create an ASP.NET Core design for Blob Storage and Key Vault using Microsoft.Extensions.Azure. Reuse one credential and explain failure handling.
Review an Enterprise Strategy
Assess this .NET Azure authentication design: [describe environment]. Recommend deterministic credentials, sovereign cloud settings, retries, logging, and secret handling.

Best Practices

  • Use managed identity or another deterministic credential in production.
  • Reuse credential instances across Azure SDK clients to improve token caching and connection behavior.
  • Keep secrets outside source control and limit diagnostic logging to approved environments.

Avoid

  • Do not embed client secrets, certificate passwords, or production credentials in prompts or source files.
  • Do not enable interactive browser authentication for unattended production services.
  • Do not rely on a broad credential chain in production when one credential type is known.

Frequently Asked Questions

What does this skill cover?
It covers Azure.Identity packages, credential selection, Azure client integration, production guidance, retries, logging, and common authentication exceptions.
Does the skill execute commands automatically?
The skill provides guidance. An agent may run package commands only when the task requires them and the environment permits execution.
Which credential should production workloads use?
Use managed identity when available. Otherwise, select one deterministic credential that matches the deployment and secret-management requirements.
How should client secrets and certificates be handled?
Keep them outside source control, restrict access, rotate them, and prefer managed identity when the Azure service supports it.
Does the guidance support sovereign clouds?
Yes. It identifies Azure authority hosts for public, government, China, and Germany environments.
Can this skill verify that authentication works?
No. Users must test credentials, role assignments, endpoints, and network access in their own Azure environment.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

5 downloads ยท 111 views

File structure

๐Ÿ“„ SKILL.md