Skip to content

Commit b0b005e

Browse files
Warning cleanup after link removal
1 parent 5057bdb commit b0b005e

2 files changed

Lines changed: 1 addition & 4 deletions

File tree

support/azure/azure-container-registry/troubleshoot-push-error-operation-disallowed-timeout.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,9 +87,6 @@ az acr repository update --name myregistry --image myrepo@sha256:123456abcdefg -
8787

8888
Another potential issue is that your container registry might have reached its storage limit. The container registry has a maximum storage capacity of 40 TiB. For more information, see [Service Tier Features and Limits](/azure/container-registry/container-registry-skus#service-tier-features-and-limits).
8989

90-
If you require storage beyond this limit, contact [Azure Support](#contact-us-for-help).
91-
92-
9390
## Error 2: Request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
9491

9592
> `Get "https://yourARC.azurecr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)`

support/azure/azure-storage/files/backup-restore/troubleshoot-azure-files.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Azure file share backup
33
description: This article is troubleshooting information about issues occurring when protecting your Azure file shares.
4-
ms.date: 04/01/2026
4+
ms.date: 04/01/2025
55
ms.reviewer: jsuri
66
ms.service: azure-file-storage
77
ms.custom: sap:Backup and Restore

0 commit comments

Comments
 (0)