support for Standard SKU #737
Merged
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
|
Thank you for submitting this PR; this is indeed an issue that should be corrected in the MLZ baseline. |
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
lisamurphy-msft
approved these changes
Aug 24, 2022
jwaltireland
pushed a commit
to ARPA-H/AzureMissionLZ
that referenced
this pull request
Nov 14, 2024
* support for Standard SKU * move AMPLS Private Endpoint to Operations VNET * Revert "move AMPLS Private Endpoint to Operations VNET" This reverts commit 7d3b6b0. Co-authored-by: Fabien Gilbert <[email protected]>
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.
Description
This change enables deployment of Standard SKU firewall. Right now MLZ only deploys successfully with a Premium SKU firewall. The Standard SKU firewall fails with an error as pointed out in issue #736.
Issue reference
The issue this PR will close: #736
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: