Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Portal Accelerator MDFC VM Vulnerability Assessment to use mdeTVM by default #1476

Merged
merged 4 commits into from
Nov 20, 2023
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/wiki/Whats-new.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,12 @@ Here's what's changed in Enterprise Scale/Azure Landing Zones:
#### 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](https://learn.microsoft.com/azure/virtual-wan/howto-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 infrastracture units. Please visit [Virtual hub capacity](https://learn.microsoft.com/azure/virtual-wan/hub-settings#capacity) for more details on Azure vWAN Virtual Hub Capacity configuration.
- 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](https://learn.microsoft.com/azure/virtual-wan/hub-settings#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 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.

### October 2023
Expand Down
6 changes: 3 additions & 3 deletions eslzArm/eslz-portal.json
Original file line number Diff line number Diff line change
Expand Up @@ -659,17 +659,17 @@
"name": "vulnerabilityAssessmentProvider",
"type": "Microsoft.Common.OptionsGroup",
"label": "Choose the Microsoft Defender for Cloud for servers vulnerability assessments provider",
"defaultValue": "Microsoft Defender for Cloud integrated Qualys scanner (recommended)",
"defaultValue": "Microsoft Defender vulnerability management (recommended)",
"toolTip": "Choose the preferred vulnerability assessment provider for Microsoft Defender for Cloud for servers vulnerability assessments.<br>Uses the custom initiative <a href=\"https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Deploy-MDFC-Config.html\">Deploy Microsoft Defender for Cloud configuration</a>.",
"visible": "[and(equals(steps('management').enableAsc,'Yes'), equals(steps('management').enableAscForServersVulnerabilityAssessments,'DeployIfNotExists'))]",
"constraints": {
"allowedValues": [
{
"label": "Microsoft Defender for Cloud integrated Qualys scanner (recommended)",
"label": "Microsoft Defender for Cloud integrated Qualys scanner",
"value": "default"
},
{
"label": "Microsoft Defender vulnerability management",
"label": "Microsoft Defender vulnerability management (recommended)",
"value": "mdeTvm"
}
]
Expand Down