Update set-up-zone-redundancy-availability-zones.md #123634
Merged
+1
−1
Conversation
This file contains 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
Trying to remove the ambiguity from the following Consideration when deploying Zone Redundant Standard Logic Apps; * You can enable availability zone redundancy *only at creation time using Azure portal*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone redundancy. The above reads to me (and some of my colleagues) that you can only deploy a zone redundant Standard Logic App/App Service if its done via the Azure Portal ONLY which isn't the case. App Service Plans can be deployed via all manner of CLI tools but Zone Redundancy cannot be enabled post creation. I feel like this consideration should be in fact worded like this; * You can enable availability zone redundancy *only at creation time*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone redundancy post creation. Hopefully this removes some of the confusion!
|
@sheppyj : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 6cf0484: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@ecfan Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
ecfan
reviewed
Jul 8, 2024
articles/logic-apps/set-up-zone-redundancy-availability-zones.md
Outdated
Show resolved
Hide resolved
Change "post" to "after" for clarity Co-authored-by: Esther Fan <ecfan@users.noreply.github.com>
|
Learn Build status updates of commit c217d9f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Thank you @ecfan I have updated with a slight amendment! |
|
#sign-off |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Trying to remove the ambiguity from the following Consideration when deploying Zone Redundant Standard Logic Apps;
The above reads to me (and some of my colleagues) that you can only deploy a zone redundant Standard Logic App/App Service if its done via the Azure Portal ONLY which isn't the case. App Service Plans can be deployed via all manner of CLI tools but Zone Redundancy cannot be enabled post creation. I feel like this consideration should be in fact worded like this;
Hopefully this removes some of the confusion!
To further demonstrate that the original could be confusing I found an old issue where a user was having the exact same thoughts I was;
Azure/logicapps#887