Update DNS zone identifier range in documentation for single digit storage endpoints

[jorchiu]

For storage accounts that have single digit in its zone identifier, I noticed that it was not 0 padded.

The screenshot below shows five instances with single-digit zone identifiers when I queried for their endpoints.

[prmerger-automator]

@jorchiu : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 827bef0:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/storage/common/storage-account-overview.md	✅Succeeded

For more details, please refer to the build report.

[v-regandowner]

@akashdubey-ms

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[Copilot]

Pull request overview

Updates Azure Storage documentation to reflect that DNS zone identifiers for some storage accounts are not zero-padded when single-digit.

Changes:

• Adjusted the documented DNS zone identifier range description (from z00… to z0/z10…).
• Updated the endpoint format examples in the service table to match the new identifier range.

Comments suppressed due to low confidence (1)

articles/storage/common/storage-account-overview.md:173

• This sentence is correct but a bit harder to scan than necessary. Consider simplifying to ...can range from z0 to z50 (single-digit zone identifiers are not zero-padded). to convey the key point more directly.

* A domain that includes the name of the service and the identifier for the DNS zone. The identifier for the DNS zone always begins with `z` and can range from `z0` to `z9`, or `z10` to `z50`.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The bracket expression z[0-9\\|10-50] is not a valid/clear range representation (inside [] it reads like a character class, and the escaped pipe \\| will render literally). Consider rewriting these examples to an unambiguous form, e.g., using prose (z0–z50), or a clearer pattern such as z0-z9 or z10-z50 (without \\|).

Suggested change

	| Blob Storage | `https://<storage-account>.z[0-9\|10-50].blob.storage.azure.net` |
	| Static website (Blob Storage) | `https://<storage-account>.z[0-9\|10-50].web.storage.azure.net` |
	| Data Lake Storage | `https://<storage-account>.z[0-9\|10-50].dfs.storage.azure.net` |
	| Azure Files | `https://<storage-account>.z[0-9\|10-50].file.storage.azure.net` |
	| Queue Storage | `https://<storage-account>.z[0-9\|10-50].queue.storage.azure.net` |
	| Table Storage | `https://<storage-account>.z[0-9\|10-50].table.storage.azure.net` |
	| Blob Storage | `https://<storage-account>.z<N>.blob.storage.azure.net` |
	| Static website (Blob Storage) | `https://<storage-account>.z<N>.web.storage.azure.net` |
	| Data Lake Storage | `https://<storage-account>.z<N>.dfs.storage.azure.net` |
	| Azure Files | `https://<storage-account>.z<N>.file.storage.azure.net` |
	| Queue Storage | `https://<storage-account>.z<N>.queue.storage.azure.net` |
	| Table Storage | `https://<storage-account>.z<N>.table.storage.azure.net` |