When the Function App cannot access the table service (due to missing permissions, firewall/private endpoint restrictions, invalid SAS, etc.), attempts to flush logs in DiagnosticEventsTableRepository fail repeatedly. This generates excessive log entries and does not resolve itself without manual intervention.
We need to enhance error handling so that if table access remains unavailable, we can disable the service and stop flushing logs as we have done in #10539, reducing log noise and preventing endless retries.
When the Function App cannot access the table service (due to missing permissions, firewall/private endpoint restrictions, invalid SAS, etc.), attempts to flush logs in
DiagnosticEventsTableRepositoryfail repeatedly. This generates excessive log entries and does not resolve itself without manual intervention.We need to enhance error handling so that if table access remains unavailable, we can disable the service and stop flushing logs as we have done in #10539, reducing log noise and preventing endless retries.