When we migrated to Office 365 some years ago, the Microsoft Graph API hooked me immediately. The API exposes almost all information stored in Office 365 and allows us to connect 3rd party tools to the data stored in Office 365.
Recently, we ran into a weird permission problem on OneDrive / Sharepoint with a user account we've set up with an email address that was used more than 2 years ago.
Last month Microsoft introduced a new release of the Microsoft Graph Developer Proxy. The latest release introduces support for monitoring specific processes, a new plugin allowing testing against rate limiting supported APIs and provides a new OData paging guidance.
In the process of refactoring an internal tool that connects to the Microsoft Graph API I re-worked the process of retrieving an authentication token that is needed for making a request to the MS Graph API.
While refactoring and upgrading one of our internal tools that is using the MS Graph API, I experimented with several techniques to fake API responses to simulate requests without actually hitting the MS Graph Production API.