Azure SQL transient error

We occasionally encounter a transient Azure SQL error 47073 (see definition below) in our DF application. Our IT department is investigating root cause. It can hit any DF in our app. Is this a candidate to add to the transient errors list for automatic retry? Could additional error codes be configurable?

We could add custom retry handlers to activity and sub-orchestrator functions, but that doesn't address the other cases (entities, external events, etc). Other suggestions for handling such an error (other than wrapping every DF call in a try/catch)?

Reason: Unable to set Deny Public Network Access to Yes since there is no private endpoint enabled to access the server. Please set up private endpoints and retry the operation (https://learn.microsoft.com/azure/sql-database/sql-database-private-endpoint-overview#how-to-set-up-private-link-for-azure-sql-database).