Skip to content
This repository is for active development of the Azure SDK for Python. For consumers of the SDK we recommend visiting our public developer docs at or our versioned developer docs at
Python Other
  1. Python 99.9%
  2. Other 0.1%
Branch: master
Clone or download


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update CODEOWNERS (#11516) May 19, 2020
common/smoketest update parameters to use SubscriptionConfiguration (#11425) May 18, 2020
doc Refresh appservice test (#10911) Apr 20, 2020
eng Sync eng/common directory with azure-sdk-tools repository (#11692) May 30, 2020
scripts Azure storage meta package deprecation (#11348) May 11, 2020
sdk Reimplement AadClient without msal.oauth2cli (#11466) May 29, 2020
tools Add force parameter to SwaggerToSdk CLI (#11609) May 23, 2020
.coveragerc PR validation pipelines for Python repo. (#5234) May 17, 2019
.gitattributes Add example application for ARM. Jun 29, 2015
.gitignore Disable pip cache (#9704) Feb 5, 2020 Code of Conduct Mar 16, 2016 change to highlight pip commands (#9352) Jan 7, 2020
LICENSE.txt Change basic files to MIT Jul 20, 2016
NOTICE.txt Adding placeholder to list any third party licenses (#9746) Feb 6, 2020 Add Gitter community channel (#9314) Mar 10, 2020
README.rst We don't release preview of "azure" anymore (#4788) Apr 5, 2019 Add security policy (#9806) Feb 11, 2020 Skip Building on incompatible Python Versions (#7160) Sep 11, 2019
pylintrc [EventHubs] Track2 Preview3 (#7059) Sep 9, 2019
setup.cfg Remove default development settings (#6376) Jul 23, 2019 Azure storage meta package deprecation (#11348) May 11, 2020
shared_requirements.txt Persistent caching for interactive credentials on Linux and macOS (#1… May 12, 2020
swagger_to_sdk_config.json Remove explicit version tag from automation (#10002) Feb 26, 2020

Azure SDK for Python

Packages Dependencies DepGraph Python Build Status

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

Getting started

For your convenience, each service has a separate set of libraries that you can choose to use instead of one, large Azure package. To get started with a specific library, see the (or README.rst) file located in the library's project folder.

You can find service libraries in the /sdk directory.


The client libraries are supported on Python 2.7 and 3.5.3 or later.

Packages available

Each service might have a number of libraries available from each of the following categories:

Client: New Releases

New wave of packages that we are announcing as GA and several that are currently releasing in preview. These libraries allow you to use and consume existing resources and interact with them, for example: upload a blob. These libraries share a number of core functionalities such as: retries, logging, transport protocols, authentication protocols, etc. that can be found in the azure-core library. You can learn more about these libraries by reading guidelines that they follow here.

You can find the most up to date list of all of the new packages on our page

NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.

Client: Previous Versions

Last stable versions of packages that have been provided for usage with Azure and are production-ready. These libraries provide you with similar functionalities to the Preview ones as they allow you to use and consume existing resources and interact with them, for example: upload a blob. They might not implement the guidelines or have the same feature set as the Novemeber releases. They do however offer wider coverage of services.


Libraries which enable you to provision specific resources. They are responsible for directly mirroring and consuming Azure service's REST endpoints. The management libraries use the azure-mgmt-<service name> convention for their package names.

Need help?


  • Chat with other community members Join the chat at

Reporting security issues and security bugs

Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) 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.


For details on contributing to this repository, see the contributing guide.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.


You can’t perform that action at this time.