-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Update copy-blobs-between-storage-accounts-network-restriction.md #1850
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Fixed a spelling error with verify and updated some text for workaround 2 while adding links to VNet peering to make it easier to understand.
@justingross-msft : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit f3f8cec:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md | Details |
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md
- Line 80, Column 110: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-network-peering-overview'.
- Line 84, Column 64: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-networks-faq'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving in Jarrett's absence
[like] Justin Gross reacted to your message:
…________________________________
From: Kaushik Ainapure ***@***.***>
Sent: Friday, April 11, 2025 4:07:04 PM
To: MicrosoftDocs/SupportArticles-docs ***@***.***>
Cc: Justin Gross ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/SupportArticles-docs] Update copy-blobs-between-storage-accounts-network-restriction.md (PR #1850)
@kaushika-msft approved this pull request.
Approving in Jarrett's absence
—
Reply to this email directly, view it on GitHub<#1850 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2IZC5OG57UYAFUEK3VDFI32Y7SCRAVCNFSM6AAAAAB2Y7XN7OVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONRQHA2TEOBQHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Learn Build status updates of commit 85141ec:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md | Details |
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md
- Line 80, Column 110: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-network-peering-overview'.
- Line 84, Column 23: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-networks-faq'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit c04f8e3:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md | Details |
support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md
- Line 80, Column 97: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-network-peering-overview'.
- Line 84, Column 23: [Warning: file-not-found - See documentation]
Invalid file link: 'azure/virtual-network/virtual-networks-faq'.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit b879ddf: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Fixed a spelling error with verify and updated some text for workaround 2 while adding links to VNet peering to make it easier to understand.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.