Azure Connectors Python SDK
Type-safe, async Python clients for Azure managed connectors. Version 1.0.0 is the first generally available release, with 103 connector clients for services such as Office 365, SharePoint, Teams, Dataverse, Salesforce, and GitHub.
Install
Requires Python 3.10 or later.
pip install azure-connectors
Send an email
Create a connector connection and grant your identity access before calling it. See the connection setup guide.
import asyncio
from azure.identity.aio import DefaultAzureCredential
from azure.connectors.office365 import Office365Client, SendEmailInput
async def main():
connection_url = "https://example.azure.com/connections/office365"
async with DefaultAzureCredential() as credential:
async with Office365Client(connection_url, credential) as client:
await client.send_email(
input=SendEmailInput(
to="recipient@example.com",
subject="Hello from Python",
body="<p>Sent with the Azure Connectors Python SDK.</p>",
)
)
if __name__ == "__main__":
asyncio.run(main())
Features
- Async-only clients and typed models in
azure.connectors.<connector>. - Caller-owned async Azure Identity or Azure Core API key credentials.
- Azure Core pipelines, request controls, and configurable retry policies.
AsyncItemPagedcollections andAsyncLROPollerlong-running operations.- Lazy client exports, type stubs, and generated API documentation.
Safe HTTP methods use configured retries. Unsafe methods make one attempt by default; opt in to retries only when an operation can tolerate replay.
SDK general availability does not change the availability, permissions, or service limits of the Azure connector resources and services your app uses. Azure Functions trigger hosting and SDK-type conversion use a separate extension.
Documentation and migration
- Documentation and API reference
- Supported connectors
- Release notes
- Preview API migration
- Preview naming migration
- Report an issue
This project uses the MIT license.
Metadata
Release files for azure-connectors 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| azure_connectors-1.0.0.tar.gz | 800.1 kB | Without provenance | Details for azure_connectors-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| azure_connectors-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for azure_connectors-1.0.0-py3-none-any.whl |
Total release size: 1.7 MB
Release files / azure_connectors-1.0.0.tar.gz
| Download URL | azure_connectors-1.0.0.tar.gz |
|---|---|
| Size | 800.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
332d6c797ac62e98398e48e1428e959fc7fa28f840a1482c4f8318054c61ad2c
|
|
BLAKE2b-256 checksum How to use checksums |
e393b19cada3b87e51a48943e542b978b46a521f38a82b476fa4b56f61dce4c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Release files / azure_connectors-1.0.0-py3-none-any.whl
| Download URL | azure_connectors-1.0.0-py3-none-any.whl |
|---|---|
| Size | 904.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f23fa0ed1efc1bb02092efb781cda2b04acaa1accfd96a579bdacea201a4ae7d
|
|
BLAKE2b-256 checksum How to use checksums |
5e58c3ad6c45f033388faf717f5ca233dc754cf25216eb1945e2d6c907eaa8e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Security for azure-connectors 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.