[Feature Request] Add Built-in Retry Support for HTTP 429 in Azure.Core for Swagger-Generated SDKs #53576
Description
Library name
Azure.ResourceManager.EventHubs
Please describe the feature.
Currently, when we generate SDKs from Swagger using:
dotnet build /t:GenerateCode
(for example, Azure.ResourceManager.EventHubs), the generated code relies on Azure.Core for HTTP pipeline behaviors such as retries. However, the default retry policy does not explicitly handle HTTP 429 (Too Many Requests) with exponential backoff.
This is critical because many Azure services enforce throttling, and 429 responses are common in high-scale scenarios. Without built-in retry handling, consumers must implement custom policies manually after SDK generation, which is not persistent across regeneration and adds maintenance overhead.
Request:
Please consider adding first-class support for retry on 429 responses in Azure.Core’s RetryPolicy implementation, ideally with configurable backoff settings. This would ensure all generated SDKs automatically benefit from robust throttling handling without manual intervention.