From 256f5009e9e43d00dbe125c5bb979d46e610f835 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:00:18 -0400 Subject: [PATCH 01/22] Create ACCELERATORS. --- ACCELERATORS. | 1 + 1 file changed, 1 insertion(+) create mode 100644 ACCELERATORS. diff --git a/ACCELERATORS. b/ACCELERATORS. new file mode 100644 index 000000000..8b1378917 --- /dev/null +++ b/ACCELERATORS. @@ -0,0 +1 @@ + From 87340558553f5da6212c86adfd0a296f9d7410f5 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:18:06 -0400 Subject: [PATCH 02/22] Update and rename ACCELERATORS. to ACCELERATORS.md --- ACCELERATORS. | 1 - ACCELERATORS.md | 16 ++++++++++++++++ 2 files changed, 16 insertions(+), 1 deletion(-) delete mode 100644 ACCELERATORS. create mode 100644 ACCELERATORS.md diff --git a/ACCELERATORS. b/ACCELERATORS. deleted file mode 100644 index 8b1378917..000000000 --- a/ACCELERATORS. +++ /dev/null @@ -1 +0,0 @@ - diff --git a/ACCELERATORS.md b/ACCELERATORS.md new file mode 100644 index 000000000..ff70888a4 --- /dev/null +++ b/ACCELERATORS.md @@ -0,0 +1,16 @@ +## Mission Landing Zone Accelerators + +Azure Landing Zone Accelerators are architectural guidance, reference architecture, reference implementations, and automation packaged to deploy workload platforms on Azure at scale and aligned with industry proven practices. Built on top of Mission Landing Zone, +each link below redirects to directories on this repository aimed to enable users to rapidly deploy each accelerator. + +### [ESRI ArcGIS Pro & Enterprise with AVD](./docs/esri.md) +This accelerator allows for the deplayment of both ArcGIS Pro & Enterprise on Azure Virtual Desktop. + +### [AVD (Azure Virtual Desktop)](./src/bicep/add-ons/azure-virtual-desktop/README.md) +This accelerator allows for the deployment of Zero Trust, SCCA compliant instances of Azure Virtual Desktop. + +### [Zero Trust Imaging](./src/bicep/add-ons/imaging/README.md) +This accelerator enables users to create customizable, zero trust images for use with Azure Virtual Desktop. + + + From d9b23c5b37a758f948deff38a420fb89fc81d092 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:21:42 -0400 Subject: [PATCH 03/22] Create ARCHITECTURE.md --- ARCHITECTURE.md | 62 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 ARCHITECTURE.md diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md new file mode 100644 index 000000000..98be42f72 --- /dev/null +++ b/ARCHITECTURE.md @@ -0,0 +1,62 @@ +## Scope + +Mission LZ has the following scope: + +- Hub and spoke networking intended to comply with SCCA controls +- Predefined spokes for identity, operations, shared services, and workloads +- Ability to create multiple, isolated workloads or team subscriptions +- Remote access +- Compatibility with SCCA compliance (and other compliance frameworks) +- Security using standard Azure tools with sensible defaults +- Azure Policy initiatives + + + +A table of the components Mission LZ provisions in Azure beneath a rectangle labeled DISA Secure Cloud Computing Architecture Controls + + +## Networking + +Networking is set up in a hub and spoke design, separated by tiers: T0 (Identity and Authorization), T1 (Infrastructure Operations), T2 (DevSecOps and Shared Services), and multiple T3s (Workloads). Access control can be configured to allow separation of duties between all tiers. + + + +A diagram that depicts a hub with four spokes, each spoke pointing at the hub + + +Each virtual network has been given a default address prefix to ensure they fall within the default super network. Refer to the [Networking page](docs/networking.md) for all the default address prefixes. + +## Subscriptions + +Most customers will deploy each tier to a separate Azure subscription, but multiple subscriptions are not required. A single subscription deployment is good for a testing and evaluation, or possibly a small IT Admin team. + +## Firewall + +All network traffic is directed through the firewall residing in the Network Hub resource group. The firewall is configured as the default route for all the T0 (Identity and Authorization) through T3 (workload/team environments) resource groups as follows: + +| Name | Address prefix | Next hop type | Next hop IP address| +|---------------|----------------|-------------------|--------------------| +| default_route | 0.0.0.0/0 | Virtual Appliance | 10.0.128.68 | + +The default firewall configured for MLZ is [Azure Firewall Premium](https://docs.microsoft.com/en-us/azure/firewall/premium-features). The Azure Firewall Premium SKU includes the IDPS feature necessary to satisfy the SCCA VDSS requirement. However, if you do not require IDPS, you can optionally deploy Azure Firewall Standard by settings the `firewallSkuTier` parameter to `Standard`. + +Presently, there are two firewall rules configured to ensure access to the Azure Portal and to facilitate interactive logon via PowerShell and Azure CLI, all other traffic is restricted by default. Below are the collection of rules configured for Azure Commercial and Azure Government clouds: + +| Rule Collection Priority | Rule Collection Name | Rule Name | Source | Port | Protocol | +|--------------------------|---------------------------|-----------------|---------------|-----------|----------------------------------------| +| 100 | AllowAzureCloud | AzureCloud | * | * | Any | +| 110 | AzureAuth | msftauth | * | Https:443 | aadcdn.msftauth.net, aadcdn.msauth.net | +| 200 | AllowTrafficBetweenSpokes | AllSpokeTraffic | 10.0.128.0/18 | * | Any | + +To deploy Mission LZ using Azure Stack Hub and an F5 BIG-IP Virtual Edition instead of Azure Firewall Premium, there is an alternate repository with instructions [found here](https://github.com/Azure/missionlz-edge). + +## Product Roadmap + +See the [Projects](https://github.com/Azure/missionlz/projects) page for the release timeline and feature areas. + +Here's a summary of what Mission Landing Zone deploys of as of April 2024: + + + +A diagram that depicts a hub and spoke network topology built with Azure resources + From 7cd0df5091672c820990acd255cc64050f0940ba Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:23:14 -0400 Subject: [PATCH 04/22] Rename ARCHITECTURE.md to DESIGN.md --- ARCHITECTURE.md => DESIGN.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename ARCHITECTURE.md => DESIGN.md (100%) diff --git a/ARCHITECTURE.md b/DESIGN.md similarity index 100% rename from ARCHITECTURE.md rename to DESIGN.md From 4e538901f1187b1f48581acbcb63d2dd24d20bf8 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:27:10 -0400 Subject: [PATCH 05/22] Update DESIGN.md --- DESIGN.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/DESIGN.md b/DESIGN.md index 98be42f72..15efb35c1 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -1,3 +1,5 @@ +# Mission LZ Design + ## Scope Mission LZ has the following scope: From 6e2587ae15ae844f8a7749238fa8591a8bb4b35e Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:28:48 -0400 Subject: [PATCH 06/22] Create RESOURCES.md --- RESOURCES.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 RESOURCES.md diff --git a/RESOURCES.md b/RESOURCES.md new file mode 100644 index 000000000..766a1f5e9 --- /dev/null +++ b/RESOURCES.md @@ -0,0 +1,17 @@ +# Mission LZ Resources + +## Contributing + +This project welcomes contributions and suggestions. See our [Contributing Guide](CONTRIBUTING.md) for details. + +## Feedback, Support, and How to Contact Us + +Please see the [Support and Feedback Guide](SUPPORT.md). To report a security issue please see our [security guidance](./SECURITY.md). + +## Trademarks + +This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft +trademarks or logos is subject to and must follow +[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). +Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. +Any use of third-party trademarks or logos are subject to those third-party's policies. From 7282241086b95c725113bd582337ff79da20feb6 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:36:48 -0400 Subject: [PATCH 07/22] Update RESOURCES.md --- RESOURCES.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/RESOURCES.md b/RESOURCES.md index 766a1f5e9..2abf2c5b9 100644 --- a/RESOURCES.md +++ b/RESOURCES.md @@ -1,5 +1,13 @@ # Mission LZ Resources +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) + +## What is a Landing Zone? + +A **landing zone** is networking infrastructure configured to provide a secure environment for hosting workloads. + +[![Landing Zones Azure Academy Video](https://img.youtube.com/vi/9BKgz9Rl1eo/0.jpg)](https://youtu.be/9BKgz9Rl1eo "Don't let this happen to you 😮 Build A Landing Zone 👍 - Click to Watch!") + ## Contributing This project welcomes contributions and suggestions. See our [Contributing Guide](CONTRIBUTING.md) for details. From c8636c9b5f0582fa6945191c948856ee1402fe77 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:36:52 -0400 Subject: [PATCH 08/22] Update README.md --- README.md | 92 ++----------------------------------------------------- 1 file changed, 2 insertions(+), 90 deletions(-) diff --git a/README.md b/README.md index be7cbc32d..434e99036 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # Mission LZ +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) + Mission Landing Zone is a highly opinionated Infrastructure-as-Code (IaC) template which IT oversight organizations can use to create a cloud management system to deploy Azure environments for their workloads and teams. Mission Landing Zone addresses a narrowly scoped, specific need for a [Secure Cloud Computing Architecture (SCCA)](docs/scca.md) compliant hub and spoke infrastructure. @@ -31,18 +33,6 @@ Our intent is to enable IT Admins to use this software to: - Customize the deployment configuration to suit specific needs - Deploy multiple customer workloads in production -## Mission Landing Zone Add-ons - -- [ESRI ArcGIS Pro & Enterprise with AVD](./docs/esri.md) -- [AVD (Azure Virtual Desktop)](./src/bicep/add-ons/azure-virtual-desktop/README.md) -- [Zero Trust Imaging](./src/bicep/add-ons/imaging/README.md) - -## What is a Landing Zone? - -A **landing zone** is networking infrastructure configured to provide a secure environment for hosting workloads. - -[![Landing Zones Azure Academy Video](https://img.youtube.com/vi/9BKgz9Rl1eo/0.jpg)](https://youtu.be/9BKgz9Rl1eo "Don't let this happen to you 😮 Build A Landing Zone 👍 - Click to Watch!") - ## Quickstart You can deploy Mission Landing Zone from the Azure Portal, or by executing an Azure CLI command. @@ -100,85 +90,7 @@ Click [here](./docs/deployment-guide-walkthrough.md) to learn about each tab and For more detailed deployment instructions, see our deployment guides for [Bicep](docs/deployment-guide-bicep.md) and [Terraform](docs/deployment-guide-terraform.md). -## Scope - -Mission LZ has the following scope: - -- Hub and spoke networking intended to comply with SCCA controls -- Predefined spokes for identity, operations, shared services, and workloads -- Ability to create multiple, isolated workloads or team subscriptions -- Remote access -- Compatibility with SCCA compliance (and other compliance frameworks) -- Security using standard Azure tools with sensible defaults -- Azure Policy initiatives - - - -A table of the components Mission LZ provisions in Azure beneath a rectangle labeled DISA Secure Cloud Computing Architecture Controls - - -## Networking - -Networking is set up in a hub and spoke design, separated by tiers: T0 (Identity and Authorization), T1 (Infrastructure Operations), T2 (DevSecOps and Shared Services), and multiple T3s (Workloads). Access control can be configured to allow separation of duties between all tiers. - - - -A diagram that depicts a hub with four spokes, each spoke pointing at the hub - - -Each virtual network has been given a default address prefix to ensure they fall within the default super network. Refer to the [Networking page](docs/networking.md) for all the default address prefixes. - -## Subscriptions - -Most customers will deploy each tier to a separate Azure subscription, but multiple subscriptions are not required. A single subscription deployment is good for a testing and evaluation, or possibly a small IT Admin team. - -## Firewall - -All network traffic is directed through the firewall residing in the Network Hub resource group. The firewall is configured as the default route for all the T0 (Identity and Authorization) through T3 (workload/team environments) resource groups as follows: - -| Name | Address prefix | Next hop type | Next hop IP address| -|---------------|----------------|-------------------|--------------------| -| default_route | 0.0.0.0/0 | Virtual Appliance | 10.0.128.68 | - -The default firewall configured for MLZ is [Azure Firewall Premium](https://docs.microsoft.com/en-us/azure/firewall/premium-features). The Azure Firewall Premium SKU includes the IDPS feature necessary to satisfy the SCCA VDSS requirement. However, if you do not require IDPS, you can optionally deploy Azure Firewall Standard by settings the `firewallSkuTier` parameter to `Standard`. - -Presently, there are two firewall rules configured to ensure access to the Azure Portal and to facilitate interactive logon via PowerShell and Azure CLI, all other traffic is restricted by default. Below are the collection of rules configured for Azure Commercial and Azure Government clouds: - -| Rule Collection Priority | Rule Collection Name | Rule Name | Source | Port | Protocol | -|--------------------------|---------------------------|-----------------|---------------|-----------|----------------------------------------| -| 100 | AllowAzureCloud | AzureCloud | * | * | Any | -| 110 | AzureAuth | msftauth | * | Https:443 | aadcdn.msftauth.net, aadcdn.msauth.net | -| 200 | AllowTrafficBetweenSpokes | AllSpokeTraffic | 10.0.128.0/18 | * | Any | - -To deploy Mission LZ using Azure Stack Hub and an F5 BIG-IP Virtual Edition instead of Azure Firewall Premium, there is an alternate repository with instructions [found here](https://github.com/Azure/missionlz-edge). - ## Getting Started See the [Deployment Guide for Bicep](docs/deployment-guide-bicep.md) and the [Deployment Guide for Terraform](docs/deployment-guide-terraform.md) in the [`docs`](docs) folder. -## Product Roadmap - -See the [Projects](https://github.com/Azure/missionlz/projects) page for the release timeline and feature areas. - -Here's a summary of what Mission Landing Zone deploys of as of April 2024: - - - -A diagram that depicts a hub and spoke network topology built with Azure resources - - -## Contributing - -This project welcomes contributions and suggestions. See our [Contributing Guide](CONTRIBUTING.md) for details. - -## Feedback, Support, and How to Contact Us - -Please see the [Support and Feedback Guide](SUPPORT.md). To report a security issue please see our [security guidance](./SECURITY.md). - -## Trademarks - -This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft -trademarks or logos is subject to and must follow -[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). -Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. -Any use of third-party trademarks or logos are subject to those third-party's policies. From 13a1114b201ef0767d30a1d4d495e9db14a4dd36 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:36:55 -0400 Subject: [PATCH 09/22] Update DESIGN.md --- DESIGN.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/DESIGN.md b/DESIGN.md index 15efb35c1..b305f2c36 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -1,5 +1,7 @@ # Mission LZ Design +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) + ## Scope Mission LZ has the following scope: From a5b3898701f59ca063da3be692ccf115492bac6b Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:37:57 -0400 Subject: [PATCH 10/22] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 434e99036..533a5060a 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Mission LZ -[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Accelerators**](./ACCELERATORS.md) | [**Resources**](./RESOURCES.md) Mission Landing Zone is a highly opinionated Infrastructure-as-Code (IaC) template which IT oversight organizations can use to create a cloud management system to deploy Azure environments for their workloads and teams. From d9897095a8fd702f241971dca9b64b268c6510f3 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:38:07 -0400 Subject: [PATCH 11/22] Update ACCELERATORS.md --- ACCELERATORS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ACCELERATORS.md b/ACCELERATORS.md index ff70888a4..8d4d404af 100644 --- a/ACCELERATORS.md +++ b/ACCELERATORS.md @@ -1,5 +1,7 @@ ## Mission Landing Zone Accelerators +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Accelerators**](./ACCELERATORS.md) | [**Resources**](./RESOURCES.md) + Azure Landing Zone Accelerators are architectural guidance, reference architecture, reference implementations, and automation packaged to deploy workload platforms on Azure at scale and aligned with industry proven practices. Built on top of Mission Landing Zone, each link below redirects to directories on this repository aimed to enable users to rapidly deploy each accelerator. From 2ae03994081b5c07fa2bbcee890cbfa9e2844d44 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:38:31 -0400 Subject: [PATCH 12/22] Update DESIGN.md --- DESIGN.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/DESIGN.md b/DESIGN.md index b305f2c36..514e1645e 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -1,7 +1,6 @@ # Mission LZ Design -[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) - +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Accelerators**](./ACCELERATORS.md) | [**Resources**](./RESOURCES.md) ## Scope Mission LZ has the following scope: From 55e9d3cbcbc35b4ff37157cf0c7deef67867aec2 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:38:39 -0400 Subject: [PATCH 13/22] Update RESOURCES.md --- RESOURCES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RESOURCES.md b/RESOURCES.md index 2abf2c5b9..8148a815e 100644 --- a/RESOURCES.md +++ b/RESOURCES.md @@ -1,6 +1,6 @@ # Mission LZ Resources -[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Resources**](./RESOURCES.md) +[**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Accelerators**](./ACCELERATORS.md) | [**Resources**](./RESOURCES.md) ## What is a Landing Zone? From d5dd5636f35bd981fced378db77cab3fd751c9e4 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:43:02 -0400 Subject: [PATCH 14/22] Update ACCELERATORS.md --- ACCELERATORS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ACCELERATORS.md b/ACCELERATORS.md index 8d4d404af..d723c10fb 100644 --- a/ACCELERATORS.md +++ b/ACCELERATORS.md @@ -1,4 +1,4 @@ -## Mission Landing Zone Accelerators +# Mission Landing Zone Accelerators [**Home**](./README.md) | [**Design**](./DESIGN.md) | [**Accelerators**](./ACCELERATORS.md) | [**Resources**](./RESOURCES.md) From 1335e0de895aea411304d4acdbd49c0a8e12151c Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:44:17 -0400 Subject: [PATCH 15/22] Update README.md --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 533a5060a..7f707efda 100644 --- a/README.md +++ b/README.md @@ -88,9 +88,8 @@ Click [here](./docs/deployment-guide-walkthrough.md) to learn about each tab and > Don't have Azure CLI? Here's how to get started with Azure Cloud Shell in your browser: -For more detailed deployment instructions, see our deployment guides for [Bicep](docs/deployment-guide-bicep.md) and [Terraform](docs/deployment-guide-terraform.md). ## Getting Started -See the [Deployment Guide for Bicep](docs/deployment-guide-bicep.md) and the [Deployment Guide for Terraform](docs/deployment-guide-terraform.md) in the [`docs`](docs) folder. +For more detailed deployment instructions, see the [Deployment Guide for Bicep](docs/deployment-guide-bicep.md) and the [Deployment Guide for Terraform](docs/deployment-guide-terraform.md) in the [`docs`](docs) folder. From bcc7254712c30f17e33499a77a36c0a6ffe72651 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:52:57 -0400 Subject: [PATCH 16/22] Update ACCELERATORS.md --- ACCELERATORS.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/ACCELERATORS.md b/ACCELERATORS.md index d723c10fb..168960735 100644 --- a/ACCELERATORS.md +++ b/ACCELERATORS.md @@ -5,14 +5,11 @@ Azure Landing Zone Accelerators are architectural guidance, reference architecture, reference implementations, and automation packaged to deploy workload platforms on Azure at scale and aligned with industry proven practices. Built on top of Mission Landing Zone, each link below redirects to directories on this repository aimed to enable users to rapidly deploy each accelerator. -### [ESRI ArcGIS Pro & Enterprise with AVD](./docs/esri.md) +## [ESRI ArcGIS Pro & Enterprise with AVD](./docs/esri.md) This accelerator allows for the deplayment of both ArcGIS Pro & Enterprise on Azure Virtual Desktop. -### [AVD (Azure Virtual Desktop)](./src/bicep/add-ons/azure-virtual-desktop/README.md) +## [AVD (Azure Virtual Desktop)](./src/bicep/add-ons/azure-virtual-desktop/README.md) This accelerator allows for the deployment of Zero Trust, SCCA compliant instances of Azure Virtual Desktop. -### [Zero Trust Imaging](./src/bicep/add-ons/imaging/README.md) +## [Zero Trust Imaging](./src/bicep/add-ons/imaging/README.md) This accelerator enables users to create customizable, zero trust images for use with Azure Virtual Desktop. - - - From b5fdf9771a7e640b0b4a460cd64cb302d0e796f4 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:53:39 -0400 Subject: [PATCH 17/22] Update ACCELERATORS.md From eb4bdc64ca0bbb2c3528c704ba2132f5a26c518e Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:53:58 -0400 Subject: [PATCH 18/22] Update README.md --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 7f707efda..656f8df36 100644 --- a/README.md +++ b/README.md @@ -92,4 +92,3 @@ Click [here](./docs/deployment-guide-walkthrough.md) to learn about each tab and ## Getting Started For more detailed deployment instructions, see the [Deployment Guide for Bicep](docs/deployment-guide-bicep.md) and the [Deployment Guide for Terraform](docs/deployment-guide-terraform.md) in the [`docs`](docs) folder. - From 8b16a6a63324d0565f7b9dcfcf4f108b7b2e07d3 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:54:14 -0400 Subject: [PATCH 19/22] Update DESIGN.md From 1ad14f5b9bd649262fa4786551b5d0b069956296 Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:54:23 -0400 Subject: [PATCH 20/22] Update ACCELERATORS.md From ec44c81ccd9169366825b23fb3997375e7e28cbb Mon Sep 17 00:00:00 2001 From: tajablonski Date: Thu, 27 Jun 2024 16:54:31 -0400 Subject: [PATCH 21/22] Update RESOURCES.md From bff49ed3932a95e430a854526c79f9d497f9b335 Mon Sep 17 00:00:00 2001 From: Jason Masten Date: Fri, 5 Jul 2024 09:11:13 -0400 Subject: [PATCH 22/22] Removed trailing space --- ACCELERATORS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ACCELERATORS.md b/ACCELERATORS.md index 168960735..355f953e2 100644 --- a/ACCELERATORS.md +++ b/ACCELERATORS.md @@ -6,7 +6,7 @@ Azure Landing Zone Accelerators are architectural guidance, reference architectu each link below redirects to directories on this repository aimed to enable users to rapidly deploy each accelerator. ## [ESRI ArcGIS Pro & Enterprise with AVD](./docs/esri.md) -This accelerator allows for the deplayment of both ArcGIS Pro & Enterprise on Azure Virtual Desktop. +This accelerator allows for the deplayment of both ArcGIS Pro & Enterprise on Azure Virtual Desktop. ## [AVD (Azure Virtual Desktop)](./src/bicep/add-ons/azure-virtual-desktop/README.md) This accelerator allows for the deployment of Zero Trust, SCCA compliant instances of Azure Virtual Desktop.