Microsoft Graph Beta SDK for Python
Get started with the Microsoft Graph Beta SDK for Python by integrating the Microsoft Graph API into your Python application.
Note:
1. Installation
pip install msgraph-beta-sdk
Note:
- The Microsoft Graph Beta SDK for Python is a fairly large package. It may take a few minutes for the initial installation to complete.
- Enable long paths in your environment if you receive a
Could not install packages due to an OSError. For details, see Enable Long Paths in Windows 10, Version 1607, and Later.
2. Getting started with Microsoft Graph
2.1 Register your application
Register your application by following the steps at Register your app with the Microsoft Identity Platform.
2.3 Get a GraphServiceClient object
You must get a GraphServiceClient object to make requests against the service.
An instance of the GraphServiceClient class handles building client. To create a new instance of this class, you need to provide an instance of Credential, which can authenticate requests to Microsoft Graph.
Note: For authentication we support both
syncandasynccredential classes fromazure.identity. Please see the azure identity docs for more information.
# Example using async credentials.
from azure.identity.aio import EnvironmentCredential
from msgraph_beta import GraphServiceClient
scopes = ['User.Read', 'Mail.Read']
credential = EnvironmentCredential()
client = GraphServiceClient(credential, scopes=scopes)
Note: Refer to the following documentation page if you need to configure an HTTP proxy.
3. Make requests against the service
After you have a GraphServiceClient that is authenticated, you can begin making calls against the service. The requests against the service look like our REST API.
Note: This SDK offers an asynchronous API by default. Async is a concurrency model that is far more efficient than multi-threading, and can provide significant performance benefits and enable the use of long-lived network connections such as WebSockets. We support popular python async envronments such as
asyncio,anyioortrio.
The following is a complete example that shows how to fetch a user from Microsoft Graph.
import asyncio
from azure.identity.aio import ClientSecretCredential
from msgraph_beta import GraphServiceClient
credential = ClientSecretCredential(
'tenant_id',
'client_id',
'client_secret'
)
scopes = ['https://graph.microsoft.com/.default']
client = GraphServiceClient(credential, scopes=scopes)
async def get_user():
user = await client.users.by_user_id('userPrincipalName').get()
if user:
print(user.display_name)
asyncio.run(get_user())
Note that to calling me requires a signed-in user and therefore delegated permissions. See Authenticating Users) for more:
import asyncio
from azure.identity import InteractiveBrowserCredential
from msgraph_beta import GraphServiceClient
credential = InteractiveBrowserCredential()
scopes=['User.Read']
client = GraphServiceClient(credential, scopes=scopes)
async def me():
me = await client.me.get()
if me:
print(me.display_name)
asyncio.run(me())
3.1 Error Handling
Failed requests raise APIError exceptions. You can handle these exceptions using try catch statements.
from kiota_abstractions.api_error import APIError
async def get_user():
try:
user = await client.users.by_user_id('userID').get()
print(user.user_principal_name, user.display_name, user.id)
except APIError as e:
print(f'Error: {e.error.message}')
asyncio.run(get_user())
Documentation and resources
Upgrading
For detailed information on breaking changes, bug fixes and new functionality introduced during major upgrades, check out our Upgrade Guide
Issues
View or log issues on the Issues tab in the repo.
Contribute
Please read our Contributing guidelines carefully for advice on how to contribute to this repo.
Copyright and license
Copyright (c) Microsoft Corporation. All Rights Reserved. Licensed under the MIT license.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Third Party Notices
2 maintainers
Metadata
2 maintainers
Release files for msgraph-beta-sdk 1.66.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 | |
|---|---|---|---|---|
| msgraph_beta_sdk-1.66.0.tar.gz | 12.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| msgraph_beta_sdk-1.66.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.4 MB
Release files / msgraph_beta_sdk-1.66.0.tar.gz
| Download URL | msgraph_beta_sdk-1.66.0.tar.gz |
|---|---|
| Size | 12.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb73707e210c95c446f7f4bebd6f9e1b041f7102bd252f66e9a278ee8dc55350
|
|
BLAKE2b-256 checksum How to use checksums |
87db06eb1893e88666290cf3a56c3abf9126db2b57c1ef2502f253bff67d6365
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Release files / msgraph_beta_sdk-1.66.0-py3-none-any.whl
| Download URL | msgraph_beta_sdk-1.66.0-py3-none-any.whl |
|---|---|
| Size | 50.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
784506f47bc69bc203d19bf89bf3b425c5f6a27130f55ee3c88d4cf79a4050f8
|
|
BLAKE2b-256 checksum How to use checksums |
bc22beaec4bc22fce2b1a50ad0341f5c416d5b7af58269caa498385b8691b657
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
RestSharp/106.13.0.0
|
Security for msgraph-beta-sdk 1.66.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.
