{"id":14038,"date":"2023-05-30T23:23:05","date_gmt":"2023-05-31T06:23:05","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=14038"},"modified":"2023-05-30T23:23:05","modified_gmt":"2023-05-31T06:23:05","slug":"microsoft-graph-developer-proxy-v0-8-with-minimal-permissions-detection-and-improved-simulating-throttling","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-developer-proxy-v0-8-with-minimal-permissions-detection-and-improved-simulating-throttling\/","title":{"rendered":"Microsoft Graph Developer Proxy v0.8 with minimal permissions detection and improved simulating throttling"},"content":{"rendered":"

Build resilient and performant apps with the latest preview version of the Microsoft Graph Developer Proxy<\/strong><\/a>. In this new version, we\u2019re excited to introduce the preview ability to detect minimal permissions for calling Microsoft Graph APIs, improved simulation of throttling, and caching guidance.<\/p>\n

Download Microsoft Graph Developer Proxy v0.8<\/a> and check if your apps properly handle API errors.<\/p>\n

Detect minimal permissions for calling Microsoft Graph APIs<\/h2>\n

Microsoft Graph exposes hundreds of endpoints that allow you to tap into data and insights in Microsoft 365. To use these API endpoints, you need to request a correct set of permissions. If you work on a large solution that uses many endpoints, it can be difficult to build the exact list of minimal permissions for your application.<\/p>\n

In this version, we\u2019re excited to introduce a preview of a new feature that shows the list of minimal Microsoft Graph API permissions for your app<\/strong>. Just start the proxy, put it in recording mode and let your app run and call Microsoft Graph APIs. After you stop recording, Developer Proxy will determine the list of minimal permissions based on the requests that it intercepted.<\/p>\n

\"A<\/p>\n

Use this feature to get the list of both application- and delegated permissions. For more information about how it works, and the available configuration options, see the documentation<\/a>.<\/p>\n

We\u2019re releasing this feature in preview and will continue to improve its accuracy. We\u2019d love to hear feedback on how it\u2019s working and how we can make it better.<\/p>\n

Improved simulating throttling<\/h2>\n

When we released Developer Proxy, we\u2019d simulate forced throttling based on the exact URL match. If the chaos plugin returned a 429 error, we recorded the URL that was throttled and checked if your app was backing off for the designated amount of time. If your app called the exact URL too early, Developer Proxy would forcefully fail the request with a 429 error. Throttling on Microsoft Graph actually happens per workload, rather than by specific URL. So, if your app has been throttled while retrieving information about one user, it will likely be throttled when retrieving information about another user too.<\/p>\n

In this version, we improved simulating throttling and let different plugins choose how they want to implement throttling<\/strong>. Plugins can choose throttling simulation from the following:<\/p>\n