Customizing Retry Logic for Type C Errors in Microsoft Graph API

Question

When using the Microsoft Graph API, guidance is sought on customizing the retry logic for Type C errors (e.g., rate limiting, throttling). It is understood that implementing exponential backoff manually via a custom interceptor or within the catch block is a feasible solution. Before proceeding with this approach, confirmation is needed on whether this method is considered best practice or if there are any recommended alternatives within the Graph API SDK for handling retries on Type C errors.