Azure SDK for Go
This repository is for active development of the Azure SDK for Go. For consumers of the SDK you can follow the links below to visit the documentation you are interested in
- Overview of Azure SDK for Go
- SDK Reference
- Code Samples for Azure Go SDK
- Azure REST API Docs
- General Azure Docs
A new set of management libraries for Go that follow the Azure SDK Design Guidelines for Go are now available. These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. Those new libraries can be identified by locating them under the
/sdk directory in the repo, and you can find the corresponding references here.
To get started, please follow the quickstart guide here. To see the benefits of migrating to the new libraries, please visit this migration guide that shows how to transition from older versions of libraries.
Previous Go SDK packages are located under /services folder, and you can see the full list on this page. They might not have the same feature set as the new releases but they do offer wider coverage of services.
For instructions and documentation on how to use our Azure SDK for Go, we have provided quick-start tutorials for both new and previous releases.
- Quickstart tutorial for new releases. Documentation is also available at each readme file of the individual module (Example: Readme for Compute Module)
- Quickstart tutorial for previous versions
Other Azure Go Packages
Azure provides several other packages for using services from Go, listed below. If a package you need isn't available please open an issue and let us know.
|Storage - Blobs||github.com/Azure/azure-storage-blob-go|
|Storage - Files||github.com/Azure/azure-storage-file-go|
|Storage - Queues||github.com/Azure/azure-storage-queue-go|
Packages that are still in public preview can be found under the
services/preview directory. Please be aware that since these packages are in preview they are subject to change, including breaking changes, outside of a major semver bump.
Reporting security issues and security bugs
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) email@example.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
- File an issue via Github Issues
- Check previous questions or ask new ones on StackOverflow using