Azure/azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 11th, 2026
Created on December 6th, 2011
Open Issues & Pull Requests: 1,368 (+0)
GitHub issues: Enabled
Number of forks: 5,191
Total Stargazers: 6,051 (+0)
Total Subscribers: 1,393 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.4 hours
Mean response time: 22.6 days
90th percentile: 44.5 days
Tracked items: 4,530

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 54% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "Azure.Identity" is answered fastest, typically in under an hour, while "Service Attention" waits about 30 hours. 70% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 5% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,059
New in 7 days: 26
Closed in 7 days: 28
Avg open age: 317 days
Stale 30+ days: 969
Stale 90+ days: 836

Recent activity

Opened in 7 days: 26
Closed in 7 days: 28
Comments in 7 days: 2
Events in 7 days: 8

Top labels

  • Client (3,433)
  • customer-reported (2,086)
  • question (1,940)
  • needs-team-attention (1,628)
  • Service Attention (1,321)
  • Mgmt (1,242)
  • CodeGen (1,066)
  • Storage (454)

Detailed Description

Azure SDK for .NET is a software development kit that provides .NET libraries for building applications that consume and manage Azure cloud services.

The SDK addresses the need for consistent, idiomatic access to Azure services from .NET applications. It organizes libraries into client libraries for consuming Azure resources and management libraries for administering them. The project maintains two generations of packages: newer libraries that follow unified Azure SDK Design Guidelines and implement shared features through Azure.Core, and stable previous-version libraries that offer broader service coverage. The newer client libraries use a consistent naming scheme starting with "Azure" followed by service category and name, making them discoverable and predictable across different Azure services.

Developers should choose this SDK when building .NET applications that interact with Azure. The newer GA and preview client libraries are recommended for new projects, as they provide consistent patterns for HTTP retries, logging, transport protocols, and authentication across all services. The stable previous-version libraries remain suitable for production use and cover more Azure services, though they may not implement the current design guidelines. The project distinguishes between client libraries for consuming resources and management libraries for administrative tasks, allowing developers to select the appropriate package for their use case.

The project maintains active development across multiple service libraries organized in the /sdk directory. Documentation is kept current through both public developer docs and versioned reference materials. The SDK implements a structured approach to library evolution, with clear guidance on which packages are production-ready and which are in preview, helping developers make informed choices about stability versus feature currency.