This repository was archived by the owner on Aug 30, 2024. It is now read-only.
Blob Post: Azure Storage Firewalls #199
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If someone has a good stock photo to use for this, let me know |
timotab
suggested changes
Oct 6, 2023
timotab
approved these changes
Oct 9, 2023
PMByrne
approved these changes
Oct 10, 2023
|
The preview storage account has been deleted. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a blob post that attempts to clarify some of the common misconceptions of the Azure Storage firewall and private endpoint features. While it is essentially a retelling of the existing documentation, it is meant to explicitly point out the differences between the public and private options which is buried in the details of the documentation.