Could we add the groupIds for secondary endpoints for RA-GRS/RA-GZRS storage accounts?

[milope]

Would it be possible to list the groupIds for secondary endpoints for Storage Accounts that are RA-GRS or RA-GZRS? The following would be added as a section below the primary endpoints. Something like the following:

Storage service	Target sub-resource	Zone name
Blob service	blob	privatelink.blob.core.windows.net
Data Lake Storage Gen2	dfs	privatelink.dfs.core.windows.net
File service	file	privatelink.file.core.windows.net
Queue service	queue	privatelink.queue.core.windows.net
Table service	table	privatelink.table.core.windows.net
Static Websites	web	privatelink.web.core.windows.net

For secondary endpoints, the following are the available sub-resources:

Storage service	Target sub-resource	Zone name
Blob service (secondary)	blob_secondary	privatelink.blob.core.windows.net
Data Lake Storage Gen2 (secondary)	dfs_secondary	privatelink.dfs.core.windows.net
Queue service (secondary)	queue_secondary	privatelink.queue.core.windows.net
Table service (secondary)	table_secondary	privatelink.table.core.windows.net
Static Websites (secondary)	web_secondary	privatelink.web.core.windows.net

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 1d6cc016-6c8f-81d7-3b5b-edce932294cf
• Version Independent ID: 619d6b5e-ea75-61dd-5ef4-f653f9822cb8
• Content: Use private endpoints - Azure Storage
• Content Source: articles/storage/common/storage-private-endpoints.md
• Service: storage
• Sub-service: common
• GitHub Login: @jimmart-dev
• Microsoft Alias: jammart

[YashikaTyagii]

@milope Thanks for your feedback! We will investigate and update as appropriate.

[SaibabaBalapur-MSFT]

@jimmart-dev Can you please check and add your comments on this doc update request as applicable.

[SaibabaBalapur-MSFT]

@milope I'm going to assign this to the document author so they can take a look at it accordingly.

[milope]

@SaibabaBalapur-MSFT Sounds good. Thank you.

[akashdubey-ms]

Thanks for your contribution to our documentation

Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information. ? Please continue to provide feedback about the documentation. We appreciate your contributions to our community.

please-close