Skip to content

Whats new

Jump to bottom
github-actions edited this page Dec 10, 2024 · 198 revisions

In this Section

Enterprise Scale/Azure Landing Zones is updated regularly. This page is where you'll find out about the latest updates to Enterprise Scale/Azure Landing Zones for:

Note: Please check the latest release notes for each of the tools, as these will contain more detailed notes relating to changes in each of the tools.

This article will be updated as and when changes are made to the above and anything else of relevance for Enterprise Scale/Azure Landing Zones. Make sure to check back here often to keep up with new updates and changes.

Important: Previous changes to the above in relation to Enterprise Scale will not be listed here. However going forward, this page will be updated.

Updates

Here's what's changed in Enterprise Scale/Azure Landing Zones:

December 2024

Tooling

  • Updated the Baseline alerts and monitoring integration section in the portal accelerator to deploy the latest release of AMBA (2024-12-10). To read more on the changes, see the What's new page in the AMBA documentation.

November 2024

Tooling

  • A bug was resolved in the Portal Accelerator that caused deployment validation to fail with the error message "The 'location' property must be specified for 'amba-id-amba-prod-001'". This event happened when a Log Analytics Workspace was not deployed, but Azure Monitor Baseline Alerts were enabled. This issue occurred because Azure Monitor Baseline Alerts depend on the management subscription, which is not provided if the Log Analytics Workspace is not deployed. To address this scenario, an additional section was implemented in the Baseline alerts and monitoring tab allowing the selection of a Management subscription when not deploying a Log Analytics Workspace.
  • Updated the Baseline alerts and monitoring integration section in the portal accelerator to deploy the latest release of AMBA (2024-11-01). To read more on the changes, see the What's new page in the AMBA documentation.

Documentation

  • Link for the Bicep Subscription Vending changed to AVM (Azure Verified Modules)

🔃 Policy Refresh Q1 FY25

  • Updated ALZ custom policies enforcing minimum TLS versions to properly evaluate the minimum TLS version, ensuring services configured to deploy TLS 1.3 will successfully evaluate.
  • Updated the initiative Deploy-MDFC-Config_20240319 to the the newer version of DCSPM: Configure Microsoft Defender CSPM plan
  • Updated Deploy-Private-DNS-Generic policy to include the ability to configure the location/region.
  • Removed duplicate assignment and portal option of Deploy Azure Policy Add-on to Azure Kubernetes Service clusters at Landing Zones scope, as this policy is assigned in the initiative Deploy Microsoft Defender for Cloud configuration at Intermediate Root scope.
  • Updated the Deny-vNet-Peer-Cross-Sub.json definition policy to include a parameter for allowed virtual networks (vNets) in other subscriptions. For vNets to be permitted to peer, both vNet IDs must be added to the allowed list.
  • Added new built-in policy assignment and portal option for Subnets should be private assigned at Platform and Landing Zones management groups. This policy's assignment effect is defaulted to "Audit" in this release, giving the community time to adopt the good practice and address subnet compliance. We will default to the "Deny" effect as part of the next Policy Refresh.
  • Added option to select Diagnostic Settings category for logging to Log Analytics in the portal experience. You can now select between the recommended "All Logs" which covers almost all Azure resources, or "Audit Only" which is limited to resources that support this category.
  • Added additional built-in policies to initiatives for the following Azure AI Services:
    • Azure OpenAI
    • Cognitive Services/Search -> AI Services
    • Machine Learning
    • Bot Service (new) -> AI Bot Services
  • Updated the initiative Deploy-MDFC-Config_20240319 to include an additional parameter that allows you to specify if the Defender for Cloud export to Log Analytics should create a new resource group. This is useful when you want to specify the resource group name or requires tags on resource groups. Will be used by other RIs - Terraform and Bicep (portal accelerator will use default values).
  • Updated Automation Account to disable local authentication by default.
  • Updated the initiative Deploy-Private-DNS-Zones to reduce the number of parameters required while retaining backward compatibility. The initiative now only requires the subscription ID, resource group name, and location for the private DNS zone. The DNS zone resource id is now generated based on those inputs. This simplifies usage in the upstream Terraform and Bicep modules.

Known Issue

Note: there a known issue when re-deploying ALZ using the portal accelerator with CMK enabled. For details please see Known Issues.

October 2024

Tooling

  • Resolved a bug in the Portal Accelerator related to deploying the single platform subscription setup. Incorrect parameter settings led to the failure of AMBA, as it erroneously attempted to deploy to a standard management group structure instead of a single platform management group as needed.
  • Increasing Policy assignment delay by a couple of minutes to help reduce assignment errors using the portal accelerator experience (the infamous "please wait 30 minutes and try again" error).
  • An issue with the Portal Accelerator regarding the Azure Monitor Baseline Alerts notifications settings was resolved. The problem occurred when no Email Address or Service Hook was specified on the Baseline alerts and monitoring tab. In this scenario, an empty string was converted to an array, resulting in the format [""] instead of []. This caused errors during the remediation of the Notification Assets initiative.

September 2024

Documentation

  • The ALZ Policies and ALZ Deprecated Services documentation has been updated to reflect changes in AMBA. To provide more flexibility for future growth AMBA is transitioning from a single Landing Zone policy initiative and instead is adopting a modular approach by splitting the Landing Zone initiative into the following distinct components (initiatives):
    • Key Management
    • Load Balancing
    • Network Changes
    • Recovery Services
    • Storage
    • VM
    • Web
  • Guidance for updating and implementing these changes in existing environments is available on the AMBA website.
  • Updated the Azure Monitoring Baseline Alerts (AMBA) integration section in the portal accelerator to include new features exposed by the AMBA solution. To read more on the changes https://azure.github.io/azure-monitor-baseline-alerts/patterns/alz/Whats-New/

Other

  • The September community call recording and slides have been uploaded to YouTube and wiki, all available from aka.ms/alz/community

August 2024

NOTE TO CONTRIBUTORS: Due to security compliance requirements, we've made core changes that mean we no longer automatically build the policies, initiatives and roles templates after changes in the src folder are committed. This means that you as a contributor must run the bicep build commands to generate the required outputs as part of your pull request. Depending on the files you've updated these are the commands (assuming you have bicep installed):

  • bicep build ./src/templates/policies.bicep --outfile ./eslzArm/managementGroupTemplates/policyDefinitions/policies.json
  • bicep build ./src/templates/initiatives.bicep --outfile ./eslzArm/managementGroupTemplates/policyDefinitions/initiatives.json
  • bicep build ./src/templates/roles.bicep --outfile ./eslzArm/managementGroupTemplates/roleDefinitions/customRoleDefinitions.json

Other

  • Cleaned up the Log Analytics "solutions" in portal ARM template, as these are no longer required and deployed by ALZ.
  • Re-introduced the option to enable "Sentinel" in the portal accelerator.
  • Updated Microsoft Sentinel onboarding (enablement) using the new mechanism that fixes issues after 1 July 2024. Microsoft Sentinel is enabled by default through the portal accelerator as a best practice - we do not however configure any data connectors, we only enable the service. Should you wish to remove this, you can delete the association from the Azure Portal after deployment from the "Sentinel" feature blade.
  • Fixed a bug that would result in a failed deployment if deploying an Express Route Gateway and Basic Firewall SKU through the portal accelerator.
  • Fixed a bug that would result in a failed deployment for some multi-region Virtual WAN scenarios with identity networks and gateways.
  • Fixed a bug that had ALZ-LITE deployments try to connect DNS zones twice for single regions deployment.

July 2024

Policy

June 2024

Documentation

  • As the Log Analytics agent is set to be retired on August 31, 2024, it is crucial for users to plan their migration to avoid any disruption in their monitoring services. The migration involves understanding the current setup, including agents, workspaces, solutions, insights, and data collections, and then configuring the new data collections to ensure a smooth transition. Tools like the AMA Migration Helper and DCR Config Generator can assist in automating and tracking the migration process. We've now made available migration guidance to assist in the process.
  • Developed a script to facilitate the transition from Microsoft Monitoring Agent (MMA) to Azure Monitor Agent (AMA) within Azure landing zones. Review the migration guidance for additional information on how the script can be used.
  • General update AMA documentation ALZ AMA Update

Policy

  • Added new custom policy Do not allow deletion of specified resource and resource type that provides a safeguard against accidental removal of the User Assigned Managed Identity used by AMA. Assigned at the Platform Management Group, it blocks delete calls using the deny action effect.
  • Updated the custom policy Deploy-ASC-SecurityContacts as part of the Deploy-MDFC-Config initiative to use the new API and revised construct for the Security Contact API in Defender for Cloud (alertNotications alias has been deprecated, and replaced by notificationSources).

Other

  • 12th June 2024 ALZ External Community Call recording and slides uploaded and shared here

🆕 AMA Updates

The ALZ Portal Accelerator has been enhanced with the latest AMA updates, ensuring a seamless and efficient management experience. 🚀

Key updates include:

🔃 Policy Refresh H2 FY24

We've missed Q3 timelines completely, but for good reason. We've held back this cycle of Policy Refresh in order to address some key initiatives that we feel are critical to the success of our customers. This is the single largest update to the ALZ Policy since the inception of the project. We're excited to share these updates with you, and we're confident that they will provide significant value to your deployments and the compliance of your Azure Landing Zones.

Special Note: Existing consumers of ALZ will notice that some "assigned by default" initiative assignments have been replaced/renamed to avoid breaking changes to existing assignments. Therefore the below original assignments will need to be deleted, and have the new version assigned instead:

Initiative Display Name Original Assignment Name New Assignment Name Scope of Assignment
Deploy-MDFC-Deploy Deploy Microsoft Defender for Cloud configuration Deploy-MDFC-Deploy Deploy-MDFC-Config-H224 Intermediate Root Management Group
Deploy-EncryptTransit Deny or Deploy and append TLS requirements and SSL enforcement on resources without Encryption in transit Enforce-TLS-SSL Enforce-TLS-SSL-H224 Landing Zones Management Group
Deploy-Diagnostics-LogAnalytics Deploy Diagnostic Settings to Azure Services Deploy-Resource-Diag Deploy-Diag-Logs Intermediate Root Management Group

May 2024

Documentation

  • Archived the readme content in the eslzArm folder as it is no longer relevant. Please refer to the ALZ Wiki for the latest information on how to deploy Enterprise-Scale Landing Zones. To view the content that was previously here, refer to the archive.
  • Added new instructions for deploying hub and spoke network topology in multiple regions.
  • Added new instructions for deploying additional vWAN hubs in multiple regions.

Tooling

  • Added functionality to deploy platform resources into multiple regions. In the Core settings, you will have the option to deploy resources in a secondary region. If you select Yes you will have new options:
    • In the Networking topology and connectivity tab:
      • If you select Hub and spoke with Azure Firewall you will deploy a second hub in a secondary region. You can configure the IP space, VPN Gateway settings, ExpressRoute Gateway settings, and Azure Firewall settings for this region. Both of the hubs will be peered, with routing for the hubs to the Azure Firewalls being deployed. If you select DDoS protection or to select the creation of Azure Private DNS Zones, these will be linked to the second hub as well.
      • If you select Hub and spoke with your third-party NVA you will deploy a second hub in a secondary region. You can configure the IP space, VPN Gateway settings, and ExpressRoute Gateway settings for this region. Both of the hubs will be peered, but no routing configured. If you select DDoS protection or to select the creation of Azure Private DNS Zones, these will be linked to the second hub as well.
      • If you select Virtual WAN you will deploy a second virtual hub in a secondary region, as part of your virtual WAN deployment. You can configure the IP space, VPN Gateway settings, ExpressRoute Gateway settings, and Azure Firewall settings for this region. Both of the hubs will be peered, with routing for the hubs to the Azure Firewalls being deployed.
    • In the Identity tab, if you have selected a topology to deploy, you will have the option to deploy an Identity virtual network to the secondary region, peered to the hub in that region.

April 2024

Tooling

  • Add additional, optional, telemetry to help the ALZ team identify styles of deployments.

March 2024

Documentation

Tooling

  • Add new Regulatory Compliance Policy Assignment flexibility feature
  • Added ARM template to enable Microsoft Defender for Cloud as part of the deployment. Policies will still remediate additional subscriptions added to ALZ after deployment.
  • Resolved an issue that prevented the policy remediation from working properly for VM Insights, Change Tracking, Azure Update Manager policies. The root cause was a too restrictive access configuration for the Managed Identity that performs the remediation tasks.
    • New deployments will now:
      • Add an additional role assignment for VMInsights Policies that are assigned at Landing Zone management group scope, granting the Managed Identity the Reader role on the Platform management group.
      • Add an additional role assignment for ChangeTracking Policies that are assigned at Landing Zone management group scope, granting the Managed Identity the Reader role on the Platform management group.
      • Add an additional role assignment to Azure Update Manger Policies, granting Managed Identity Operator at the same scope as the assignment.
    • To update an existing deployment:

      • This script Set-RBACAmaPolicyAssignment.ps1 will update the required role assignments. The enterpriseScaleCompanyPrefix parameter is required for running the script and should contain the intermediate root management group name.

        .\Set-RBACAmaPolicyAssignment.ps1 -enterpriseScaleCompanyPrefix contoso

February 2024

Tooling

  • Disabled a Policy in the Microsoft Defender for SQL initiative. As it is not required at this stage. See ALZ AMA FAQ for more details.
  • Changed enforcementMode of the assignment of Policy "Deploy-UserAssignedManagedIdentity-VMInsights" to Default. This is to ensure that a Resource Group and a User Assigned Managed Identity are created on new subscriptions (subscriptions that are added after the initial deployment).
  • Bug fix for Portal Accelerator. userAssignedIdentityResourceGroup has been added as output for the Portal UI, this fixes deploying the Resource Group with a custom name.
  • Bug fix for Portal Accelerator. subscriptionIds now uses lambda function to obtain the subscription IDs from corpConnectedLzSubscriptionId. This fixes the Invalid Template error when selecting a corp connected landing zone deployment.
  • Bug fix for Portal Accelerator. connectivitySubscriptionId is now skipped when no networking components are deployed. This fixes an InvalidTemplateDeployment error deploying the Resource Group for UAMI.
  • From Portal Accelerator: removed the options to select VM vulnerability assessment provider and to select Defender for Cloud for DNS. These are now default to the recommended settings.

AMA Update for the Portal Accelerator

The Azure Monitor Agent (AMA) is the new way to collect and send data to Azure Monitor. The Log Analytics agent, or the Microsoft Monitoring Agent (MMA), will no longer be supported after August 2024. To adapt to this change, the ALZ Portal Accelerator has been updated to use AMA instead of MMA.

This update currently applies to Greenfield Portal Deployment Scenarios. Brownfield guidance as well as Bicep and Terraform updates to follow in short-term.

We are happy to announce that we have added a new section in the documentation for AMA. Please visit ALZ AMA Update for a detailed overview of the changes made to the ARM templates and Policies, as well as the deprecated policy assignments.

IMPORTANT We've added an ALZ AMA FAQ with important information about key changes in AMA. Please read the ALZ AMA FAQ for more information.

🔃 Policy Refresh Q2 FY24

Yes, the Q2 Policy Refresh has been delayed due to a light past quarter and some very important initiatives that we feel had to make it into this refresh.

Policy

IMPORTANT We've updated the ALZ Policy FAQ with important information about the new Diagnostic Settings v2 policies and initiatives that are will be landing soon. Please read the ALZ Policy FAQ and Tips for more information.

IMPORTANT Take special note of additional steps, in the docs page listed above, that are required to offboard the legacy Qualys solution from your environment.

January 2024

Tooling

  • Bug fix for Portal Accelerator, removing region restrictions for VPN Gateways when deploying regional (not AZ).
  • Bug fix for Portal Accelerator deployment when deploying using a single platform subscription. Previously, a single tenant deployment would have three failed deployments for diagnostic settings which were looking for non-existent management groups (Management, Identity and Connectivity). This has been fixed and the deployment will now succeed.
  • Added drop down selection option for Azure Private Link Private DNS Zones as part of portal based ALZ deployment experience where you can select to deploy or not to deploy a subset of Private Link Private DNS zones.
  • Updated ALZ policy testing framework on pull request to only test new or changed policies, drastically speeding up the testing process.

Documentation

December 2023

Tooling

  • Added a new policy/initiative submission form template for GitHub Issues. This will help us to better understand the policy/initiative you are submitting and will help us to review and approve the submission faster. Please use this template when submitting new policies/initiatives to the ALZ GitHub Issues page.

Docs

  • Added new section to the ALZ Wiki FAQ to provide guidance around Private DNS Zone/Privatelink issues - read here.

Other

November 2023

Tooling

  • Added virtual hub routing preference support to Portal Accelerator for scenarios where you need to influence routing decisions in virtual hub router towards on-premises. For existing ALZ customers please visit Configure virtual hub routing preference for details on how to configure virtual hub routing preference settings.
  • Added virtual hub capacity option to Portal Accelerator which provides an option to select the number of routing infrastructure units. Please visit Virtual hub capacity for more details on Azure vWAN Virtual Hub Capacity configuration.
  • Fixed a bug in the portal accelerator experience when deploying with single platform subscription and selecting virtual WAN networking topology - Invalid Template error.
  • Updated the ALZ Portal Accelerator and default assignments for Microsoft Defender for Cloud (MDFC) VM Vulnerability Assessment provider to default to use the PG recommended Microsoft Defender for Endpoint Threat/Vulnerability Management (mdeTVM) provider, instead of the Qualys provider.

Docs

  • Fixed in ALZ Azure Setup the bash command to assign at root scope Owner role to a Service Principal.
  • Added a new section to describe ALZ Policy Testing Framework for ALZ custom policies Policies Testing Framework.

October 2023

Policy

Tooling

  • Fixed a bug in the portal accelerator experience when deploying a VPN Gateway and Azure Firewall (Basic SKU) - IP address overlap error.
  • Added vWAN Hub Routing Intent support to Portal Accelerator for scenarios that include Azure Firewall deployment. For existing ALZ customers please visit How to configure Virtual WAN Hub routing intent and routing policies for details on how to add routing intent to your environment.
  • Enhanced the ALZ Portal Accelerator to provide the ability to deploy the Azure VPN Gateway in Active/Active mode as per feedback from #655.

Docs

  • Updated the ALZ Wiki FAQ to include a section on why we've enabled GitHub Releases - read here.
  • Updated the ALZ Wiki FAQ to include a section on why some solutions may not deploy in an ALZ governed environment and how to work around it.

September 2023

Policy

Important: For existing ALZ deployments, you will need to redeploy the below assignments with least privilege RBAC roles, and review and remove existing service principals Owner role assignments. The below list includes the scope that needs to be reviewed. For new deployments, the below assignments will be deployed with least privilege RBAC roles.

Where to find RBAC roles to cleanup

  • Remediating default policy/initiative assignments using Owner role to be least privilege where possible. Updated assignments:
    • Deploy-AzActivity-Log (Management Group: Intermediate Root)
    • Deploy-AKS-Policy (added additional required role)
    • Deploy-Resource-Diag (Management Group: Intermediate Root)
    • Deploy-SQL-TDE (Management Group: Landing Zone)
    • Deploy-VM-Backup (Management Group: Landing Zone)
    • Deploy-VM-Monitoring (Management Group: Intermediate Root)
    • Deploy-VMSS-Monitoring (Management Group: Intermediate Root)

Other

August 2023

Policy

  • Updating custom policies using over permissive roles (Owner) to use resource scoped roles (e.g., Storage Account Contributor, Azure SQL Contributor, etc.):
    • Deploy-Storage-sslEnforcement
    • Deploy-SqlMi-minTLS
      • Added evaluationDelay as provisioning takes around 4 hours and policy remediation fails on create due to time outs (as it normally triggers after 10 minutes).
    • Deploy-SQL-minTLS
    • Deploy-MySQL-sslEnforcement (changed from Owner to Contributor role, no built in roles currently available)
    • Deploy-PostgreSQL-sslEnforcement (changed from Owner to Contributor role, no built in roles currently available)
  • Updated to the new Configure Microsoft Defender for Storage to be enabled built-in policy to the Deploy-MDFC-Config initiative and assignment.
    • Read more about the new Microsoft Defender for Storage here: aka.ms//DefenderForStorage.
    • NOTE: there are additional cost considerations associated with this feature - more info.

Other

  • Renamed Azure Active Directory to Microsoft Entra ID

July 2023

Major update in this release: introducing the Policy Testing Framework foundation, along with tests for all assigned infrastructure policies that use the DENY effect. This will allow us to test the policies in a more automated fashion, and will help us to ensure that we don't introduce any regressions in the future and maintain a higher level of quality for our policies. We will be adding additional tests for custom policies in the future.

Policy

  • Added additional initiative assignment for Enforce-Guardrails-KeyVault to the Platform Management Group to improve security coverage. Initially this assignment was only applied to the Landing Zone Management Group.
    • Update Portal RI to include the new assignment option for the Key Vault initiative under Platform Management.
  • Added new custom policy to audit Virtual Machines not using Azure Hybrid Benefit (Audit-AzureHybridBenefit)
  • Fixing bug in Deploy-Sql-vulnerabilityAssessments to achieve compliance if successfully remediated. NOTE: Due to the need to change parameters, this is a breaking change. The original policy will remain in place but will be deprecated and a new policy will be deployed for the fix Deploy-Sql-vulnerabilityAssessments_20230706 - please update assignments accordingly - many thanks @Matt-FFFFFF.
  • Bug fix for Management port access from the Internet should be blocked not enforcing deny effect when a deployment includes rules defined in network security group properties (i.e., when specifying rules when creating the NSG) - many thanks to @DavidRobson.
  • QoL updates: adding supersededBy metadata and adding links in the description to deprecated custom policies to point to the superseding policy - aligned with ALZ specific feature updates in AzAdvertizer.
  • Policy Testing Framework implemented for custom ALZ DENY policies (See Tooling section below).

Tooling

  • Enhanced the Azure Firewall Basic experience in the ALZ Portal Accelerator based on feedback from #1370 by removing the DNS proxy option when selecting the Basic SKU
  • Updated Sentinel deployment to use new simplified pricing tier
  • Established a Policy Testing Framework based on Pester, built on the work done by @fawohlsc in this repo azure-policy-testing

Docs

  • Updated contribution guide to include a new section to describe how to implement tooltips when adding new policies with default assignments that require updates to the portal reference implementation.
  • Adding text to the ALZ-Policies wiki page to clarify that we do use preview policies as part of initiatives in some default assignments.

June 2023

Policy

  • Fixed default assignment for SQLEncryption (DINE-SQLEncryptionPolicyAssignment) to use the correct policy definition.
  • Added new default assignment for SQLThreatDetection (DINE-SQLThreatPolicyAssignment) to use the previous policy definition from DINE-SQLEncryptionPolicyAssignment.
  • Updated the assignment DINE-LogAnalyticsPolicyAssignment (Deploy-Log-Analytics) to default enforcement mode to "DoNotEnforce". The Log Analytics workspace is deployed directly by the reference implementations, and as a result this policy is no longer required to deploy the Log Analytics workspace. Retaining the assignment for auditing purposes.
  • Added new custom policies for (many thanks @jeetgarg):

Tooling

  • Updated Portal Accelerator tooltips to provide more relevance and links to associated policies or initiatives.

Other

  • When the option to deploy Log Analytics workspace and enable monitoring is enabled (Yes) in the Platform management, security, and governance section, Diagnostic Settings for Management Groups are also deployed.

May 2023

Policy

  • Updated Deploy-Diagnostics-APIMgmt.json to support resource-specific destination table in the diagnostic setting for API Management.
  • Updated Deploy-Diagnostics-LogAnalytics.json policy initiative with new parameter to support resource-specific destination table in the diagnostic setting for API Management.
  • Updated Deploy-Diagnostics-Firewall.json to support resource-specific destination table in the diagnostic setting for Firewall
  • Updated Deploy-Diagnostics-LogAnalytics.json policy initiative with new parameter to support resource-specific destination table in the diagnostic setting for Firewall
  • Updated Deploy-Diagnostics-APIMgmt.json to support resource-specific destination table in the diagnostic setting for API Management
  • Updated Deploy-Diagnostics-LogAnalytics.json policy initiative with new parameter to support resource-specific destination table in the diagnostic setting for API Management
  • Bug fix for effect for the Key Vault setting (incorrect case) in Deploy-MDFC-Config.json initiative.
  • Bug fix for Management port access from the Internet should be blocked when a destination port array is submitted that contains port ranges that includes a denied port (22, 3389, and any others) when creating new NSG rules.
  • Bug fix for AppService append sites with minimum TLS version to enforce. where the policy was preventing the creation of connection strings via API. The fix revises the policy rule logic to address the blocking issue.
  • Fixed minor grammatical errors in two policy assignments.
  • Deprecated policy Deny-MachineLearning-PublicNetworkAccess.
  • Update initiative Deny-PublicPaaSEndpoints to replace deprecated policy Deny-MachineLearning-PublicNetworkAccess with builtin 438c38d2-3772-465a-a9cc-7a6666a275ce.
  • Deprecated policy Deny-PublicEndpoint-MariaDB.
  • Update initiative Deny-PublicPaaSEndpoints to replace deprecated policy Deny-PublicEndpoint-MariaDB with builtin fdccbe47-f3e3-4213-ad5d-ea459b2fa077 - special note: US Gov/Fairfax still uses the now deprecated policy as the builtin is not yet available.
  • Standardized denied network resources in policy assignments for Corp and Sandbox management groups as per GH #1333.
  • Added non-compliance message to Enforce-ALZ-Sandbox initiative assignment.

Docs

  • Updated wiki deployment guides for the four main scenarios to include the new Decommissioned and Sandbox step in the portal accelerator.
  • Updated ALZ Policies wiki to make the link to the Excel spreadsheet more prominent.
  • Updated ALZ Policies wiki images to reflect policy initiative assignments now included for Decommissioned and Sandbox management groups.
  • Updated the ALZ Policy Assignments Excel spreadsheet to include a release version column so users can track when those policies last changed and verified all assignments have a relevant AzAdvertizer link for policy details.
  • Azure Enablement Show: Updating your Azure landing zones published
  • Tech Community Blog: Azure Monitor Baseline Alerts (Preview) published
  • Updated wiki documentation to so reflect the removal of the "Platform DevOps and automation" section from ALZ Portal Accelerator
  • Added support for Azure Firewall Basic SKU to Hub & Spoke and Virtual WAN deployments in the ALZ Portal Accelerator
  • Updated wiki documentation towards Subscription Vending approach for landing zone (subscription) creation
  • A brand new ALZ Policy FAQ and Tips page has been added to the wiki to help answer some of the most common questions and provide some useful tips for working with ALZ policies.
  • Updated ALZ Contribution Guide to include new section on how to contribute to ALZ policies resulting in breaking changes, and some minor refactoring to make it more readable.

Tooling

Other

April 2023

We are pleased to announce that we are starting regular Azure Policy reviews for Azure Landing Zone. This includes a review of new built-in policies released and their suitability for ALZ, built-in policies that can replace custom ALZ policies, built-in policies that have been deprecated and addition of new ALZ custom policies and initiatives as identified based on best practices, issues raised and customer feedback. Most importantly, we have also provided default assignments for all the new policies at the appropriate ALZ Management Group level. This will ensure that all new policies are automatically assigned to the appropriate scope and will be in compliance with the ALZ baseline. This will also ensure that the ALZ is always up to date with the latest Azure Policy definitions.

This update includes many ALZ Azure Policies and Initiatives that have been added or updated to enhance the security, governance, and management of ALZ. As part of our commitment to continuous improvement, we have also enhanced our policy review process, with a focus on transitioning away from deprecated policies where possible, move from custom to built-in policies providing the same or enhanced functionality, and implementing new policies to keep ALZ as part of the current review cycle. We have also implemented non-compliance messages where supported to provide a better user experience when a policy is non-compliant.

This is the first major review and refresh of Azure Policy since ALZ was GA'd. Since GA many new built-in policies and initiatives have been released which has driven the need for this review. We believe that a regular review cycle will allow us to stay on top of emerging trends and new policies, ensuring that our Azure environment remains secure and compliant. Should you identify policies or initiatives that should be considered for ALZ, kindly submit an GitHub issue. For more information, please refer to the ALZ Policies or the new Excel spreadsheet version.

We strongly advise staying up-to-date to ensure the best possible security posture for your Azure environment, see Keep your Azure landing zone up to date. For those with existing deployments or policies, we have provided Brownfield guidance to help you navigate the process of updating to the latest policies. We recognize that there may be breaking changes when upgrading an existing deployment or policies and for details follow our recently released guidance to support you in this process:

Please note that, in some cases, moving to the new Built-In Policy definitions, deploying changes to existing custom policies or removing deprecated policies will require a new Policy Assignment and removing the previous Policy Assignment, which will mean compliance history for the Policy Assignment will be lost. However, if you have configured your Activity Logs and Security Center to export to a Log Analytics Workspace, Policy Assignment historic data will be stored here as per the retention duration configured. Thank you for your cooperation, and we look forward to continuing to work with you to ensure the security and compliance of our Azure environment. While we've made every effort to test the stability of this release, should you have any issues and the guidance provided does not resolve your issue, please open a GitHub issue so we can do our best to support you and document the fix for others.

Policy

Breaking Changes

Note that a number of initiatives have been updated that will fail to deploy if you have existing deployments. This is due to the fact that the number of parameters and default values have changed, as we've added or removed policies from the initiative. To resolve this, you will need to remove the existing initiative assignments and then redeploy the updated initiative.

Initiative Name Change Recommended Action
Deny or Deploy and append TLS requirements and SSL enforcement on resources without Encryption in transit (azadvertizer.net) Removed a deprecated policy, superceding policy is already in the initiative Remove existing initiative assignment, delete the custom initiative and remove the orphaned identity. Deploy the updated initiative.
New
  • New Initiative for the Decommissioned landingzones including policies:
    • Initiative name: Enforce-ALZ-Decomm
      • Allowed resource types - resources are not allowed to be deployed, however, authorization, lock and tag management are permitted.
      • New policy to deploy an auto shutdown policy for virtual machines - Deploy-Vm-autoShutdown
      • Portal accelerator updated with additional tab and options to enable this initiative.
  • New Initiative for the Sandboxes landingzones including policies:
  • Added initiative assignment [Preview]: Deploy Microsoft Defender for Endpoint agent to 'Intermediate Root' Management Group.
  • Added assignment of Network interfaces should not have public IPs built-in Policy to the 'Corp' Management Group.
  • Added new initiative and assignment to implement recommended guardrails for Azure Key Vault at the landing zones management group
    • Initiative name: ENFORCE-Guardrails-KeyVault
    • Policies included: ALZ Polices
    • Portal accelerator updated
  • Added two new policy assignments to govern Corp Management Group networking:
    • DENY-HybridNetworking - blocks the provisioning of vWAN/ER/VPN, including gateways, in Corp
    • AUDIT-PeDnsZones - audits the provisioning of Private Link Private DNS Zones in Corp
      • NOTE: The policy default values include all the static Private DNS Zones only. When assigned via the ALZ portal experience the assignment includes all the Private DNS Zones that are deployed as part of the ALZ Portal experience, including the geo code/regional zones for Azure Backup, AKS etc.
  • Added new policy assignment to audit WAF enabled on Application Gateways (Audit-AppGW-WAF)
  • Added new initiative and assignment to enable Azure Compute Security Baseline compliance auditing for Windows and Linux virtual machines (Enforce-ACSB)
  • Added new Diagnostic setting category for Host Pools Diagnostic Settings to Deploy-Diagnostics-WVDHostPools
    • ConnectionGraphicsData
  • Added new Diagnostic setting category for EventGrid Topics Diagnostic Settings to Deploy-Diagnostics-EventGridTopic
    • DataPlaneRequests
  • Added two new policy initiative assignments to enable Advanced Threat Detection for databases at intermediate root:
  • Add new Azure Policy Initiative and assignment (Audit-UnusedResourcesCostOptimization), at the intermediate root management group (e.g. contoso), to audit unused resources that are driving costs.
  • Added new assignment to deny deployment of virtual machines and virtual machine scale sets using unmanaged OS disks.
  • Added a policy assignment to deny Classic resources at the Intermediate Root management group
Update
Retire
  • Deprecated the custom ALZ policy Deploy SQL Database Transparent Data Encryption as there is now a built-in policy available in Azure Policy Deploy SQL DB transparent data encryption.
  • No longer assign Databricks custom policies at Corp management group scope. Policies:
    • Deny-Databricks-NoPublicIp
    • Deny-Databricks-Sku
    • Deny-Databricks-VirtualNetwork

If you are not using these policies, we advise you remove the assignment at Corp management group level, if you are not utilizing them.

Portal Accelerator

  • FIX: Updated the Fairfax (US Gov) portal accelerator experience so it now works as expected.
  • Service Map solution has been removed as an option to be deployed, as this has been superseded by VM Insights, as documented here. Guidance on migrating and removing the Service Map solution can be found here.

Other

March 2023

Docs

Tooling

  • Added additional deployment telemetry collection data point for Zero Trust Networking intent as documented here.
  • Defaulted Azure Firewall SKU/Tier to Premium from Standard. SKU/Tier can still be set back to Standard if desired

February 2023

Policy

  • Updated Deploy-Diagnostics-Databricks.json policy with missing log categories
  • Updated Deploy-Diagnostics-PostgreSQL.json policy to include setting Diagnostic Settings on PostgreSQL flexible server
  • Updated Deploy-Diagnostics-Website.json policy to set Diagnostic Settings based on the AppService plan, as the Premium Tier has more categories available.
  • Removed duplicated category entry from Deploy-Diagnostics-VNetGW.json policy.

Tooling

  • Added note to the portal experience on the "Platform DevOps and automation" blade warning that a management/platform subscription must be selected otherwise the blade will be blank

January 2023

Policy

  • Updated Deploy-SQLVulnerabilityAssessments.json policy to use Storage Account Contributor for storing the logs.
  • Updated the same policy parameter description for email recipients explaining string type and how to format input.
  • Fix typo in Deny-MachineLearning-PublicAccessWhenBehindVnet.json.

Other

  • ALZ External Community Call held. Recording and slides can be found here.

December 2022

Docs

Original URL New URL
docs/ESLZ-Policies.md wiki/ALZ-Policies
docs/EnterpriseScale-Architecture.md wiki/ALZ-Architecture
docs/EnterpriseScale-Contribution.md wiki/ALZ-Contribution
docs/EnterpriseScale-Deploy-landing-zones.md wiki/ALZ-Deploy-landing-zones
docs/EnterpriseScale-Deploy-reference-implentations.md wiki/ALZ-Deploy-reference-implementations
docs/EnterpriseScale-Deploy-workloads.md wiki/ALZ-Deploy-workloads
docs/EnterpriseScale-Known-Issues.md wiki/ALZ-Known-Issues
docs/EnterpriseScale-Roadmap.md wiki/ALZ-Roadmap
docs/EnterpriseScale-Setup-aad-permissions.md wiki/ALZ-Setup-aad-permissions
docs/EnterpriseScale-Setup-azure.md wiki/ALZ-Setup-azure

Tooling

  • Added ALZ Custom RBAC Role Definitions, as listed here to ALZ Portal Experience. Fixing #1079

Policy

  • Updated "Deploy Diagnostic Settings to Azure Services" initiative replacing deprecated policy for diagnostic settings on Storage Account
  • Removed all exclusions (parameters) from the Microsoft Cloud Security Benchmark (currently Azure Security Benchmark) initiative assignment to standardize across reference architectures and align with best practice. Impacted assignment: Deploy-ASC-Monitoring
  • Updated "**Deploy Diagnostic Settings for Data Factory to Log Analytics workspace" to include new categories of: SandboxPipelineRuns & SandboxActivityRuns
  • Add missing minimalSeverity parameter to Deploy-ASC-SecurityContacts Policy Definition

Tooling

  • Removed ActivityLog Solution as an option to be deployed into the Log Analytics Workspace. As this has been superseded by the Activity Log Insights Workbook, as documented here.

November 2022

Docs

Tooling

  • Updated ALZ Portal Accelerator to support all available Availability Zones as listed here
  • Update ALZ Portal Accelerator Private DNS Zones for Private Link, fixing issue #1073

Policy

  • "Deploy Diagnostic Settings for Log Analytics to Log Analytics workspace" definition added and also added to Deploy-Diagnostics-LogAnalytics initiative

  • "Deploy Diagnostic Settings for Databricks to Log Analytics workspace" definition update

    • Version 1.1.0 -> 1.2.0
    • Added missing log categories

  • "Deploy SQL Database security Alert Policies configuration with email admin accounts" definition update

    • Version 1.0.0 -> 1.1.1
    • Changed email addresses from hardcoding to array parameter

  • "Deploy SQL Database Transparent Data Encryption" definition update

    • Version 1.0.0 -> 1.1.0
    • Added system databases master, model, tempdb, msdb, resource to exclusion parameter as default values
    • Added as Policy Rule 'notIn' which will exclude the above databases from the policy

  • Updated "Deploy-Private-DNS-Zones" Custom initiative for Azure Public Cloud, with latest built-in Policies. Policies were added for the following Services:

    • Azure Automation
    • Azure Cosmos DB (all APIs: SQL, MongoDB, Cassandra, Gremlin, Table)
    • Azure Data Factory
    • Azure HDInsight
    • Azure Migrate (missing Private DNS Zone also added)
    • Azure Storage (Blob, Queue, File, Static Web, DFS and all relative secondaries)
    • Azure Synapse Analytics
    • Azure Media Services
    • Azure Monitor

  • Minor fixes related to "Deploy-Private-DNS-Zones" Custom Initiative and respective Assignment:

    • Added missing Zones for "WebPubSub" and "azure-devices-provisioning", so Initiative Assignment works correctly
    • Minor correction related to ASR Private DNS Zone variable, so Initiative Assignment works correctly
    • Conversion of "Azure Batch" Private DNS Zone (from regional to global), to properly align with latest respective documentation and functionality

  • Renamed Azure DDoS Standard Protection references to Azure DDoS Network Protection.

  • Incremented version for policy Deploy-DDoSProtection from "version":"1.0.0" to "version": "1.0.1"

  • Added Configure Microsoft Defender for Azure Cosmos DB to be enabled to the Deploy Microsoft Defender for Cloud configuration initiative and updated version to 3.1.0 - Fixing issue issue #1081

  • Added AZFWFlowTrace category for Azure Firewall in associated Diagnostic Policy

  • Deprecated the following ALZ policies

    in favour of Azure built-in policies with the same or enhanced functionality.

ALZ Policy ID(s) Azure Builti-in Policy ID(s)
Deploy-Nsg-FlowLogs-to-LA e920df7f-9a64-4066-9b58-52684c02a091
Deploy-Nsg-FlowLogs e920df7f-9a64-4066-9b58-52684c02a091
Deny-PublicIp 6c112d4e-5bc7-47ae-a041-ea2d9dccd749

  • ""Deploy-ASC-SecurityContacts"" definition update

    • displayName and description update to "Deploy Microsoft Defender for Cloud Security Contacts"
    • Added new parameter minimalSeverity with settings
      • Default value High
      • Allowed values: High, Medium, Low

  • ""Deploy-MDFC-Config"" definition update

    • Updated policy definitions set Deploy-MDFC-Config, Deploy-MDFC-Config(US Gov), Deploy-MDFC-Config (China)
      • added new parameter minimalSeverity.
      • added default value for multiple parameters.

Other

  • No updates, yet.

October 2022

Docs

Tooling

  • Release v2.4.1 of the Azure landing zones Terraform module adds a new diagnostic category for Azure Firewall, as reported in issue #1063
  • Update the Azure landing zone portal accelerator to use Resource Graph with a generic drop down UI element to improve user experience for subscription selection.
  • Update the Azure landing zone portal accelerator to have more unique naming for deployment names in same tenant, using utcNow() function in deploymentSuffix variable - fixes #1077
  • Update the Azure landing zone portal accelerator to have more unique naming for vNet names - fixes #881
    • vNet naming pattern changed:
      • From:
        • Identity vNet: <Subscription ID>-<Root ID Prefix>-vnet-<Region Short Name>
        • Corp vNets: <Subscription ID>-<Root ID Prefix>-vnet-<Region Short Name>
      • To:
        • Identity vNet: <Root ID Prefix>-vnet-<Region Short Name>-<Subscription ID> (then trimmed to 64 characters, using take() function, starting at front - so Subscription ID will get trimmed)
        • Corp vNets: <Root ID Prefix>-vnet-<Region Short Name>-<Subscription ID> (then trimmed to 64 characters, using take() function, starting at front - so Subscription ID will get trimmed)
    • ⚠️This is a breaking change, only if you attempt to redeploy the Azure landing zone portal accelerator over the top of an existing Azure landing zone portal accelerator deployment that was deployed prior to 12/10/2022 (12th October 2022)⚠️
      • The outcome if you do this will be that new vNets will be created based on what you input into the Azure landing zone portal accelerator form when you fill it out. Even if you input exactly the same inputs and details as the first time you deployed it.
        • However, this is a very uncommon action and if you are impacted please raise an issue on the repo and we can assist further
  • Release of various ALZ-Bicep versions:
  • Updated Azure landing zone portal accelerator with a note around existing Management Group Name/IDs on "Azure core setup" blade linking to FAQ Q&As

Policy

  • Added Configure Microsoft Defender for Azure Cosmos DB to be enabled to the Deploy Microsoft Defender for Cloud configuration initiative and updated version to 3.1.0 - Fixing issue issue #1081
  • Updated the Diagnostic Settings Policies to leverage the profileName parameter properly, rather than hardcoded value (setByPolicy) - Fixing issue issue #478

Other

  • No updates, yet.

September 2022

Docs

Tooling

Policy

  • No updates, yet.

Other

  • No updates, yet.

August 2022

Docs

  • No updates, yet.

Tooling

  • Updated the eslzArm implementation (Portal accelerator) to use a new policies.json file. This file is now programmatically generated from a library of individual resource definitions using a Bicep template, and was introduced to:
    • Simplify maintenance of individual policies
    • Improve traceability and testability of policy changes
    • Provide universal support across multiple cloud environments, including AzureCloud (public), AzureChinaCloud and AzureUSGovernment
    • As a bonus, we have also improved consistency of metadata implemented across the policies
  • Updated Azure Backup geo codes for new regions across ARM, Bicep and Terraform implementation options

Policy

  • No updates, yet.

Other

  • No updates, yet.

July 2022

Docs

  • Updated the ALZ Terraform module Wiki to reflect the latest fixes.
  • Various updates to CAF ALZ Docs
    • Identity and Access Management
    • Network Topology and Connectivity
    • Management
    • Platform Automation and DevOps

Tooling

  • ALZ Terraform module hotfix release v2.1.2, for regional private endpoint DNS zones
  • ALZ Bicep modules release v0.9.2 released
    • Added Landing Zone Management Group Children Flexibility
    • Added Policy Assignments for Mooncake (Azure China)
    • Fixed Azure Backup Private DNS Zone Geo Codes bug, fixing issue #279
  • ALZ Accelerator (Portal Experience) updated to fix Azure Backup Private DNS Zone Geo Codes, fixing issue #1004

Policy

  • No updates, yet.

Other

  • No updates, yet.

June 2022

Docs

Tooling

  • Fixed issue #979 by adding support for the additional Log Analytics Solutions of SQLVulnerabilityAssessment and SQLAdvancedThreatProtection to the Azure Landing Zone Accelerator (portal experience)
  • ALZ Terraform module minor release v2.1.0, to provide feature parity on the fix for issue #979
  • ALZ Terraform module hotfix release v2.1.1 (see release notes for more information).

Policy

  • Renamed Diagnostic Settings Policies from WVD to AVD - Fixing issue issue #962
    • displayName and description updated only. name left as WVD to avoid in-place update issues for existing deployments
    • Add 2 new categories for Host Pools Diagnostic Settings
      • NetworkData
      • SessionHostManagement
  • Added AVD Scaling Plans Diagnostic Settings called Deploy-Diagnostics-AVDScalingPlans for Azure Public only - as not supported in Fairfax or Mooncake as per https://learn.microsoft.com/azure/virtual-desktop/autoscale-scaling-plan - Fixing issue issue #962
    • Added to Deploy-Diagnostics-LogAnalytics Policy Initiative
  • Added additional log categories to Deploy-Diagnostics-Firewall for Azure Firewall Diagnostic Settings Policy - Fixing issue issue #985
  • Added additional log categories to Deploy-Diagnostics-APIMgmt for Azure API Management Diagnostic Settings Policy - Fixing issue issue #986
  • Added new Policy for for Azure Bastion Diagnostic Settings Policy called Deploy-Diagnostics-Bastion - Fixing issue issue #968
    • Added to Deploy-Diagnostics-LogAnalytics Policy Initiative
  • Updated Deny-MachineLearning-ComputeCluster-RemoteLoginPortPublicAccess mode from Indexed to All - Fixing issue issue #978
  • Updated Deploy-Storage-sslEnforcement existence condition - Fixing issue issue #971
  • Updated Deploy-Diagnostics-MlWorkspace metrics and categories - Fixing issue issue #893

Other

  • No updates, yet.

May 2022

Docs

Tooling

Policy

  • No updates, yet.

Other

  • Published resources from the third Azure Landing Zones Community Call - held on the 2nd May 2022

April 2022

Docs

Tooling

  • Azure Landing Zones Terraform Module v2.0.0 released 🥳
    • Adds support for Virtual WAN plus much more
    • Checkout release notes for details on all the changes and fixes
    • Checkout upgrade guide for details on how to upgrade to the latest release
  • Updated Private DNS Zones that are created for Private Link/Endpoints in Portal Experience as per documentation here: Azure Private Endpoint DNS configuration
  • Added Telemetry to Portal Experience. More info here Telemetry Tracking Using Customer Usage Attribution (PID)
  • Increase preparingToLaunch deployment delay in portal experience to improve scenario in issue 902
  • Added warnings to use dedicated Subscriptions for platform services when selecting the dedicated model to help avoid deployment failures seen when selecting the same Subscription in the dedicated platform Subscription model for Management, Identity and Connectivity
    • Improving experience as suggested in issue 910
    • Customers wanting a single subscription for platform services should select the 'Single' option on the 'Azure Core Setup' blade

Policy

  • Added new custom policy definition called Deny vNet peering to non-approved vNets
    • This is useful in scenarios where you only want to allow vNet peering to say a central hub vNet and not allow other vNet peerings between landing zones to be enabled.

Other

  • No updates, yet.

February 2022

Docs

Tooling

  • The Bicep version of Azure Landing Zone (formerly Enterprise-scale) is here! 🥳
  • Updated accelerator (portal) experience to deploy an Azure Firewall Policy Premium SKU instead of Standard when Premium is selected for the Azure Firewall in a Hub & Spoke VNet Connectivity model.
  • Updated accelerator (portal) experience to deploy an Azure Firewall Policy for customers using the Virtual WAN connectivity model.

Policy

  • Renamed Deploy-ASCDF-Config to Deploy-MDFC-Config and updated version to 3.0.0 - fixing issue 923

Other

  • No updates, yet.

January 2022

Docs

  • No updates, yet.

Tooling

  • New release v1.1.0 of the caf-enterprise-scale Terraform module, providing updates to the published policies and a number of bug fixes.

Policy

  • Updated Deny-Subnet-Without-Nsg & Deny-Subnet-Without-Udr to version 2.0.0
    • Fixes scenario described in issue issue #407
  • Updated Deploy-ASCDF-Config policy initiative with changes relating to new Microsoft Defender for Cloud Containers plan as documented in issue #874
    • Updated in Public (Commercial), Fairfax (Gov) and Mooncake (China)
    • Updated portal experiences for Public and Fairfax
Policy Definition Display Name Policy Definition ID Note
[Deprecated]: Configure Azure Defender for container registries to be enabled d3d1e68e-49d4-4b56-acff-93cef644b432 REMOVED - Old ACR policy
[Deprecated]: Configure Azure Defender for Kubernetes to be enabled 133047bf-1369-41e3-a3be-74a11ed1395a REMOVED - Old AKS Policy
Configure Microsoft Defender for Containers to be enabled c9ddb292-b203-4738-aead-18e2716e858f ADDED - New grouped containers policy for the new plan

Other

  • No updates, yet.

December 2021

Docs

Updated TOC

  • Updated DIY instructions for deploying Enterprise-Scale in Azure China with:
    • Additional details of some deployment steps
    • Microsoft Defender for Cloud configuration policy set definition and policy assignment specific to Azure China
    • Differentiate between Az VM Backup policy assignment for identity management group, and landing zone management group in the DIY guidance

Policy

  • The following policy definitions for Microsoft Defender for Cloud configurations are not available as built-in in Azure China. The policy set definition will be updated as when these policy definitions are available:
    • defenderForOssDb, defenderForSqlServerVirtualMachines, defenderForAppServices, defenderForAppServices, defenderForStorageAccounts, defenderForKeyVaults, defenderForDns, defenderForArm

November 2021

Docs

  • No updates, yet.

Tooling

  • New release v1.1.0 of the caf-enterprise-scale Terraform module, providing updates to the published policies and a number of bug fixes.

Policy

  • Replaced Deploy-Default-Udr policy with Deploy-Custom-Route-Table that allows deploying custom route tables with an arbitrary set of UDRs (including a 0/0 default route if needed). See here for usage details.

  • Updated Deploy-Budget policy, to v1.1.0, adding new parameter of budgetName that defaults to: budget-set-by-policy - closing issue #842

    • Including Fairfax
    • Also Mooncake (Azure China) even though not in use yet

  • Added AuditEvent to Deploy-Diagnostics-AA Policy Definition to ensure correct compliance reporting on Automation Account used for diagnostics - closing issue #864

Other

  • Published resources from the second Enterprise Scale Community Call - held on the 17th November 2021

October 2021

Docs

Tooling

  • Terraform Enterprise Scale Module reaches GA (V1.0.0) - see release notes
  • ESLZ reference implementation updated with built-in (11) policies for Azure Security Center, enforcing (DeployIfNotExists) Azure Security Center with Standard Tier for Azure Defender for the following services:
    • Kubernetes
    • App Services
    • VMs
    • Key Vault
    • Azure Resource Manager
    • DNS
    • Open-source relational databases
    • SQL on VMs
    • SQL databases
    • Storage
    • Container Registries

Policy

  • No updates, yet.

Other

  • No updates, yet.

September 2021

Docs

Tooling

Policy

Custom ESLZ Policy Name Custom ESLZ Policy Display Name Custom Category Built-In Policy Name/ID Built-In Policy Display Name Built-In Category Notes
Deny-Databricks-NoPublicIp Deny public IPs for Databricks cluster Databricks Denies the deployment of workspaces that do not use the noPublicIp feature to host Databricks clusters without public IPs.
Deny-Databricks-Sku Deny non-premium Databricks sku Databricks Enforces the use of Premium Databricks workspaces to make sure appropriate security features are available including Databricks Access Controls, Credential Passthrough and SCIM provisioning for Microsoft Entra ID.
Deny-Databricks-VirtualNetwork Deny Databricks workspaces without Vnet injection Databricks Enforces the use of vnet injection for Databricks workspaces.
Deny-MachineLearning-PublicNetworkAccess Azure Machine Learning should have disabled public network access Machine Learning Denies public network access for Azure Machine Learning workspaces.

Other

  • No updates, yet.

August 2021

Docs

Tooling

Policy

  • Some minor changes to parameters and variables, tidying up some code.
  • Updated policy Deploy-VNET-HubSpoke to address #726 and #728

Other

  • Published resources from the first Enterprise Scale Community Call - held on the 25th August 2021

July 2021

Docs

Tooling

  • Portal Experience Updated
    • Merged Contoso, AdventureWorks, and Wingtip into one ESLZ deployment experience via first-party deployment in the portal ("Deploy To Azure" button) experience
      • Support "N" network topologies in same experience (Hub and Spoke, Virtual WAN, Hub and Spoke with NVA)
      • Added option for VNET Peering the Identity subscription's VNET to the Connectivity subscription's Hub VNET
      • Added option for VNET peering Landing Zones to Connectivity subscription when Hub & Spoke is the selected topology (Virtual WAN is excluded due to concurrency issues, at this time) - closing issue #517
      • Navigate policy assignment for identity, when using single vs dedicated subscriptions for platform purposes
      • Optimized the execution graph
  • Re-structured the ARM templates for all resource deployments
    • eslzArm.json is used to orchestrate the E2E composition of ESLZ, and subsequent resource deployments based on user input from the portal ("Deploy To Azure" button) experience
    • The composite ARM templates can be sequenced on their own, independently of each other (although strict sequencing is required to ensure the same outcome)
      • Guidance coming soon for this
    • Customers can deploy from private repository if they want to sequence at their own pace.
  • AzOps release v1.3.0
  • AzOps release v1.3.1
  • AzOps release v1.4.0

Policy

  • Various custom ESLZ Azure Policies have moved to Built-In Azure Policies, see below table for more detail:

You may continue to use the ESLZ custom Azure Policy as it will still function as it does today. However, we recommend you move to assigning the new Built-In version of the Azure Policy.

Please note that moving to the new Built-In Policy Definition will require a new Policy Assignment and removing the previous Policy Assignment, which will mean compliance history for the Policy Assignment will be lost. However, if you have configured your Activity Logs and Security Center to export to a Log Analytics Workspace; Policy Assignment historic data will be stored here as per the retention duration configured.

Policy Definitions Updates

Custom ESLZ Policy Name Custom ESLZ Policy Display Name Custom Category Built-In Policy Name/ID Built-In Policy Display Name Built-In Category Notes
Deny-PublicEndpoint-Aks Public network access on AKS API should be disabled Kubernetes 040732e8-d947-40b8-95d6-854c95024bf8 Azure Kubernetes Service Private Clusters should be enabled Kubernetes
Deny-PublicEndpoint-CosmosDB Public network access should be disabled for CosmosDB SQL 797b37f7-06b8-444c-b1ad-fc62867f335a Azure Cosmos DB should disable public network access Cosmos DB
Deny-PublicEndpoint-KeyVault Public network access should be disabled for KeyVault Key Vault 55615ac9-af46-4a59-874e-391cc3dfb490 [Preview]: Azure Key Vault should disable public network access Key Vault
Deny-PublicEndpoint-MySQL Public network access should be disabled for MySQL SQL c9299215-ae47-4f50-9c54-8a392f68a052 Public network access should be disabled for MySQL flexible servers SQL
Deny-PublicEndpoint-PostgreSql Public network access should be disabled for PostgreSql SQL 5e1de0e3-42cb-4ebc-a86d-61d0c619ca48 Public network access should be disabled for PostgreSQL flexible servers SQL
Deny-PublicEndpoint-Sql Public network access on Azure SQL Database should be disabled SQL 1b8ca024-1d5c-4dec-8995-b1a932b41780 Public network access on Azure SQL Database should be disabled SQL
Deny-PublicEndpoint-Storage Public network access onStorage accounts should be disabled Storage 34c877ad-507e-4c82-993e-3452a6e0ad3c Storage accounts should restrict network access Storage
Deploy-Diagnostics-AKS Deploy Diagnostic Settings for Kubernetes Service to Log Analytics workspace Monitoring 6c66c325-74c8-42fd-a286-a74b0e2939d Deploy - Configure diagnostic settings for Azure Kubernetes Service to Log Analytics workspace Kubernetes
Deploy-Diagnostics-Batch Deploy Diagnostic Settings for Batch to Log Analytics workspace Monitoring c84e5349-db6d-4769-805e-e14037dab9b5 Deploy Diagnostic Settings for Batch Account to Log Analytics workspace Monitoring
Deploy-Diagnostics-DataLakeStore Deploy Diagnostic Settings for Azure Data Lake Store to Log Analytics workspace Monitoring d56a5a7c-72d7-42bc-8ceb-3baf4c0eae03 Deploy Diagnostic Settings for Data Lake Analytics to Log Analytics workspace Monitoring
Deploy-Diagnostics-EventHub Deploy Diagnostic Settings for Event Hubs to Log Analytics workspace Monitoring 1f6e93e8-6b31-41b1-83f6-36e449a42579 Deploy Diagnostic Settings for Event Hub to Log Analytics workspace Monitoring
Deploy-Diagnostics-KeyVault Deploy Diagnostic Settings for Key Vault to Log Analytics workspace Monitoring bef3f64c-5290-43b7-85b0-9b254eef4c47 Deploy Diagnostic Settings for Key Vault to Log Analytics workspace Monitoring
Deploy-Diagnostics-LogicAppsWF Deploy Diagnostic Settings for Logic Apps Workflow runtime to Log Analytics workspace Monitoring b889a06c-ec72-4b03-910a-cb169ee18721 Deploy Diagnostic Settings for Logic Apps to Log Analytics workspace Monitoring This is currently not assigned as per #691
Deploy-Diagnostics-RecoveryVault Deploy Diagnostic Settings for Recovery Services vaults to Log Analytics workspace Monitoring c717fb0c-d118-4c43-ab3d-ece30ac81fb3 Deploy Diagnostic Settings for Recovery Services Vault to Log Analytics workspace for resource specific categories Backup
Deploy-Diagnostics-SearchServices Deploy Diagnostic Settings for Search Services to Log Analytics workspace Monitoring 08ba64b8-738f-4918-9686-730d2ed79c7d Deploy Diagnostic Settings for Search Services to Log Analytics workspace Monitoring
Deploy-Diagnostics-ServiceBus Deploy Diagnostic Settings for Service Bus namespaces to Log Analytics workspace Monitoring 04d53d87-841c-4f23-8a5b-21564380b55e Deploy Diagnostic Settings for Service Bus to Log Analytics workspace Monitoring
Deploy-Diagnostics-SQLDBs Deploy Diagnostic Settings for SQL Databases to Log Analytics workspace Monitoring b79fa14e-238a-4c2d-b376-442ce508fc84 Deploy - Configure diagnostic settings for SQL Databases to Log Analytics workspace SQL
Deploy-Diagnostics-StreamAnalytics Deploy Diagnostic Settings for Stream Analytics to Log Analytics workspace Monitoring 237e0f7e-b0e8-4ec4-ad46-8c12cb66d673 Deploy Diagnostic Settings for Stream Analytics to Log Analytics workspace Monitoring
Deploy-DNSZoneGroup-For-Blob-PrivateEndpoint Deploy DNS Zone Group for Storage-Blob Private Endpoint Network TBC TBC TBC This policy is still rolling out to the Built-In Definitions at this time. We'll be here very soon!
Deploy-DNSZoneGroup-For-File-PrivateEndpoint Deploy DNS Zone Group for Storage-File Private Endpoint Network TBC TBC TBC This policy is still rolling out to the Built-In Definitions at this time. We'll be here very soon!
Deploy-DNSZoneGroup-For-KeyVault-PrivateEndpoint Deploy DNS Zone Group for Key Vault Private Endpoint Network ac673a9a-f77d-4846-b2d8-a57f8e1c01d4 [Preview]: Configure Azure Key Vaults to use private DNS zones Key Vault
Deploy-DNSZoneGroup-For-Queue-PrivateEndpoint Deploy DNS Zone Group for Storage-Queue Private Endpoint Network TBC TBC TBC This policy is still rolling out to the Built-In Definitions at this time. We'll be here very soon!
Deploy-DNSZoneGroup-For-Sql-PrivateEndpoint Deploy DNS Zone Group for SQL Private Endpoint Network TBC TBC TBC This policy is still rolling out to the Built-In Definitions at this time. We'll be here very soon!
Deploy-DNSZoneGroup-For-Table-PrivateEndpoint Deploy DNS Zone Group for Storage-Table Private Endpoint Network TBC TBC TBC This policy is still rolling out to the Built-In Definitions at this time. We'll be here very soon!
Deploy-LA-Config Deploy the configurations to the Log Analytics in the subscription Monitoring Policy Removed Policy Removed TBC This policy has been removed as it is handled as a resource deployment in the ARM templates, portal experience and Terraform module.
Deploy-Log-Analytics Deploy the Log Analytics in the subscription Monitoring 8e3e61b3-0b32-22d5-4edf-55f87fdb5955 Configure Log Analytics workspace and automation account to centralize logs and monitoring Monitoring

Policy Initiatives Updates

Custom ESLZ Policy Name Custom ESLZ Policy Display Name Custom Category New Policy Name/ID New Policy Display Name New Category Notes
Deploy-Diag-LogAnalytics Deploy Diagnostic Settings to Azure Services N/A Deploy-Diagnostics-LogAnalytics Deploy Diagnostic Settings to Azure Services Monitoring Moved to using a mix of Built-In (as above) and custom policy definitions
Deny-PublicEndpoints Public network access should be disabled for PAAS services Network Deny-PublicPaaSEndpoints Public network access should be disabled for PaaS services N/A Moved to using Built-In policy definitions only (as above)
New Policy New Policy N/A Deploy-Private-DNS-Zones Configure Azure PaaS services to use private DNS zones Network
  • Moved several of the diagnostics Policies to built-in, and updating the diagnostics Initiative
    • This means there's a new resource name as update of existing one is not be allowed due to removal of parameters
  • Added Policy Initiative for enforcing Private DNS Zone Association with Private Link (using built-in)
  • Added Policy Initiative for denying Public Endpoints (using built-in)
  • Updated description and display name for all Policy Assignments

Other

No updates, yet.

June 2021

Docs

Tooling

Policy

  • Updated Deny-Subnet-Without-UDR policy, to v1.1.0, to allow exclusion of subnets like the AzureBastionSubnet - closing issue #604
  • Updated Deny-Subnet-Without-Nsg policy, to v1.1.0, to allow exclusion of subnets like the GatewaySubnet, AzureFirewallSubnet and AzureFirewallManagementSubnet - closing issue #456
  • Updated Deny-VNet-Peering and Deny-VNET-Peer-Cross-Sub policies mode to All from Indexed. - closing issue #583

Other

  • Contoso Reference Implementation Update - Virtual WAN Hub default CIDR changed from /16 to /23 - closing issue #440

This wiki is being actively developed

If you discover any documentation bugs or would like to request new content, please raise them as an issue.

Contributions to this wiki are done through the main repo under docs/wiki.

Wiki content

Clone this wiki locally