UPGRADING.md

Microsoft Graph Python SDK Upgrade Guide

This guide highlights breaking changes, and new features introduced in the new Microsoft Graph Beta Python SDK.

Upgrading to msgraph-beta-sdk from msgraph-core

• Installation
• New Features
• Breaking Changes

Installation

# msgraph-core
pip install msgraph-core

# msgraph-sdk
pip install msgraph-beta-sdk

New Features

Model classes

The msgraph-beta-sdk provides auto-generated model classes that correspond to objects that are accepted and returned from the Microsoft Graph Beta API. These models leverage Python's typing features and have fully typed properties, methods and return types.

This package (msgraph-sdk) will only contain models that match the Microsoft Graph Beta API metadata. If you are interested in the v.1 API, please see the Microsoft Graph Python SDK.

Fluent Request Builder Pattern

msgraph-beta-sdk provides a fluent interface that takes advantage of method chaining and IDE autocomplete when making requests to the Graph. This is a shift from msgraph-core where raw URLs would be passed instead:

# msgraph-core
resp =client.get('/users/userId/messages')

# msgraph-beta-sdk
req = client.users_by_id('userId').messages().get()
resp = asyncio.run(req)

Hopefully this makes it more intuitive to work with the SDK and reduces time checking reference docs. Your feedback would be appreciated on your preferred experience or whether we should support both scenarios.

Breaking Changes

The following breaking changes were introduced in msgraph-beta-sdk:

• Changes to Authentication Mechanism
• Changes to the Graph client construction and configuration experience.
• Changes to Graph request functionality.
• Dependency changes.

Changes to authentication

msgraph-beta-sdk introduces an AuthenticationProvider that handles the fetching, caching and refreshing of tokens ensuring all your requests are always authenticated.

The AuthenticationProvider makes use of the azure-identity library hence its name - AzureIdentityAuthenticationProvider. The AzureIdentityAuthenticationProvider class is imported from the kiota-authentication package and expects an async credential. See azure.identity.aio documentation for more details on supported credential classes.

# msgraph-core
from azure.identity import ClientSecretCredential
from msgraph.core import GraphClient

credential = ClientSecretCredential(tenant_id: str, client_id: str, client_secret: str)


# msgraph-sdk
from azure.identity.aio import ClientSecretCredential # async credentials only
from kiota_authentication_azure.azure_identity_authentication_provider import AzureIdentityAuthenticationProvider

credential=ClientSecretCredential(tenant_id: str, client_id: str, client_secret: str)
auth_provider = AzureIdentityAuthenticationProvider(credential)

See more code samples on how to initialise the Authentication Provider.

Changes to Graph client instantiation and configuration

msgraph-beta-sdk introduces a new format for creating and configuring clients based on our Kiota client generator. It involves creating an instance of a GraphRequestAdapter that will take care of all generic processing of HTTP requests, and passing the instance to the GraphServiceClient which holds strongly typed models and request builders to simplify the process of creating requests and consuming responses.

# msgraph-core
from msgraph.core import GraphClient

client = GraphClient(credential=credential)


# msgraph-sdk
from msgraph_beta.graph_request_adapter import GraphRequestAdapter
from msgraph_beta.graph_service_client import GraphServiceClient

adapter = GraphRequestAdapter(auth_provider)
client = GraphServiceClient(request_adapter)

With version 2's configuration, all your requests are authenticated without additional effort.

See this example on how to customise the GraphRequestAdapter configuration.

Changes to graph request mechanism

All requests are asynchronous by default in the msgraph-beta-sdk and return a coroutine. In order to execute a request, you need to run them in an async environment using one of the available popular python async libraries asyncio, anyio, trio.

To configure the request, you need to pass a RequestConfiguration object to the method call.

The request method also allows you to pass your custom response handler that handles the raw Response object. By default the Response body is deserialized to the expected model type.

# msgraph-core
result = client.get('/users/userId/messages',params={'$select': 'subject','$top': '5', '$skip': '1'})
for message in result.json()['value']:
    print message['subject']

# msgraph-beta-sdk
query_params = MessagesRequestBuilder.MessagesRequestBuilderGetQueryParameters(
    select=['subject',], skip=1, top=5
)
request_config = MessagesRequestBuilder.MessagesRequestBuilderGetRequestConfiguration(
    query_parameters=query_params,
)

messages = asyncio.run(client.users_by_id('userId').messages().get(request_configuration=request_config))
for msg in messages.value:
    print(msg.subject)

See the examples on how to pass headers in your requests.

Exception Handling

Any 4xx or 5xx responses from the Graph API will result in an ApiException being thrown.

try:
    users = asyncio.run(client.users().get())

except ApiException as e {
    return f"Exception occurred: {repr(e)}"
}

Dependency changes

• Python 3.6 is the new minimum supported Python version.
• requests support is deprecated in favour of httpx.
• asyncio/any other supported async envronment e.g AnyIO, Trio.