11 posts · rss

Microsoft Graph in C#

Microsoft Graph from .NET: batching and mapping responses back to requests, rich notifications, throttling, and the SDK behaviour the docs leave out.

Graph is the API I reach for first and argue with most. The SDK is good until it is not, and the gap between what the documentation describes and what the service does is where these posts live.

Recurring themes: batching, and the genuinely annoying problem of mapping batch responses back to the requests that produced them. Retry logic that separates the requests worth retrying from the ones that will fail again. Rich change notifications that carry their own payload, so you do not have to call back for the thing you were just told about. And the odd corner where the beta SDK is the only way through and nobody has written it down.

If you are chasing throttling specifically, that has its own topic. If you are chasing cost, look at API performance.