You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To cross promote MLZ Edge and MLZ Core we wish to advertise the other solution with a link to the Github repo on the read me section of our information.
Description
Please add the text below to the ReadMe section:
If you are looking for a Mission Landing Zone solution for your connected or disconnected Azure Stack Hub devices, we invite you to visit our MLZ for Edge Github Repo here: https://github.com/Azure/missionlz-edge
Acceptance Criteria
The text is added with the link.
The link is tested and works.
The text was updated successfully, but these errors were encountered:
Think this makes sense to insert where we describe how Azure Firewall is configured or with the Network Diagram. It seems like the decision someone would make whether to use Mission LZ or Mission LZ Edge is the presence of Azure Firewall Premium or if you're using an Azure-in-a-box product.
## Mission LZ Edge
Lorem ipsum dolor set are you using Azure Stack/HCI/Edge?
Check out lorem ipsum for a similar deployment and network design to solve similar problems...
Benefit/Result/Outcome
To cross promote MLZ Edge and MLZ Core we wish to advertise the other solution with a link to the Github repo on the read me section of our information.
Description
Please add the text below to the ReadMe section:
If you are looking for a Mission Landing Zone solution for your connected or disconnected Azure Stack Hub devices, we invite you to visit our MLZ for Edge Github Repo here: https://github.com/Azure/missionlz-edge
Acceptance Criteria
The text was updated successfully, but these errors were encountered: