Skip to content

Commit ed8aeac

Browse files
authored
Merge pull request #267234 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 2/26
2 parents 6635506 + 5df6c54 commit ed8aeac

File tree

46 files changed

+1729
-625
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

46 files changed

+1729
-625
lines changed

articles/aks/node-autoprovision.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,7 @@ NAP is based on the Open Source [Karpenter](https://karpenter.sh) project, and t
6868
- Windows and Azure Linux node pools aren't supported yet
6969
- Kubelet configuration through Node pool configuration is not supported
7070
- NAP can only be enabled on new clusters currently
71+
- It is not currently possible to stop nodepools or clusters which use the NAP feature
7172
7273
## Enable node autoprovisioning
7374

articles/aks/start-stop-cluster.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ This article assumes you have an existing AKS cluster. If you need an AKS cluste
2121
When using the cluster stop/start feature, the following conditions apply:
2222

2323
- This feature is only supported for Virtual Machine Scale Set backed clusters.
24+
- You can't stop clusters which use the [Node Autoprovisioning (NAP)](node-autoprovision.md) feature.
2425
- The cluster state of a stopped AKS cluster is preserved for up to 12 months. If your cluster is stopped for more than 12 months, you can't recover the state. For more information, see the [AKS support policies](support-policies.md).
2526
- You can only perform start or delete operations on a stopped AKS cluster. To perform other operations, like scaling or upgrading, you need to start your cluster first.
2627
- If you provisioned PrivateEndpoints linked to private clusters, they need to be deleted and recreated again when starting a stopped AKS cluster.

articles/aks/start-stop-nodepools.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ You might not need to continuously run your AKS workloads. For example, you migh
1717
* Spot node pools are supported.
1818
* Stopped node pools can be upgraded.
1919
* The cluster and node pool must be running.
20+
* You can't stop node pools from clusters which use the [Node Autoprovisioning (NAP)](node-autoprovision.md) feature.
2021

2122
## Before you begin
2223

articles/api-management/self-hosted-gateway-enable-azure-ad.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,8 @@ When configuring the custom roles, update the [`AssignableScopes`](../role-based
5757
"Actions": [
5858
"Microsoft.Authorization/denyAssignments/read",
5959
"Microsoft.Authorization/roleAssignments/read",
60-
"Microsoft.Authorization/roleDefinitions/read"
60+
"Microsoft.Authorization/roleDefinitions/read",
61+
"Microsoft.Authorization/checkAccess/read"
6162
],
6263
"NotActions": [],
6364
"DataActions": [],

articles/azure-arc/system-center-virtual-machine-manager/overview.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Overview of the Azure Connected System Center Virtual Machine Manager
33
description: This article provides a detailed overview of the Azure Arc-enabled System Center Virtual Machine Manager.
4-
ms.date: 02/23/2024
4+
ms.date: 02/26/2024
55
ms.topic: conceptual
66
ms.services: azure-arc
77
ms.subservice: azure-arc-scvmm
@@ -93,7 +93,8 @@ In addition, SCVMM requires the following exception:
9393

9494
| **Service** | **Port** | **URL** | **Direction** | **Notes**|
9595
| --- | --- | --- | --- | --- |
96-
| SCVMM management Server | 443 | URL of the SCVMM management server | Appliance VM IP and control plane endpoint need outbound connection. | Used by the SCVMM server to communicate with the Appliance VM and the control plane. |
96+
| SCVMM Management Server | 443 | URL of the SCVMM management server. | Appliance VM IP and control plane endpoint need outbound connection. | Used by the SCVMM server to communicate with the Appliance VM and the control plane. |
97+
| WinRM | WinRM Port numbers (Default: 5985 and 5986). | URL of the WinRM service. | IPs in the IP Pool used by the Appliance VM and control plane need connection with the VMM server. | Used by the SCVMM server to communicate with the Appliance VM. |
9798

9899
[!INCLUDE [network-requirement-principles](../includes/network-requirement-principles.md)]
99100

articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: jsuri
77
ms.topic: quickstart
88
ms.services: azure-arc
99
ms.subservice: azure-arc-scvmm
10-
ms.date: 2/23/2024
10+
ms.date: 2/26/2024
1111
ms.custom: references_regions
1212

1313
# Customer intent: As a VI admin, I want to connect my VMM management server to Azure Arc.
@@ -29,7 +29,7 @@ This Quickstart shows you how to connect your SCVMM management server to Azure A
2929
| **Requirement** | **Details** |
3030
| --- | --- |
3131
| **Azure** | An Azure subscription <br/><br/> A resource group in the above subscription where you have the *Owner/Contributor* role. |
32-
| **SCVMM** | You need an SCVMM management server running version 2019 or later.<br/><br/> A private cloud or a host group with a minimum free capacity of 32 GB of RAM, 4 vCPUs with 100 GB of free disk space. <br/><br/> A VM network with internet access, directly or through proxy. Appliance VM will be deployed using this VM network.<br/><br/> Only Static IP allocation is supported and VMM Static IP Pool is required. Follow [these steps](/system-center/vmm/network-pool?view=sc-vmm-2022&preserve-view=true) to create a VMM Static IP Pool and ensure that the Static IP Pool has at least four IP addresses. Dynamic IP allocation using DHCP isn't supported. <br/><br/> A library share with write permission for the SCVMM admin account through which Resource Bridge deployment is going to be performed. |
32+
| **SCVMM** | You need an SCVMM management server running version 2019 or later.<br/><br/> A private cloud or a host group with a minimum free capacity of 32 GB of RAM, 4 vCPUs with 100 GB of free disk space. <br/><br/> A VM network with internet access, directly or through proxy. Appliance VM will be deployed using this VM network.<br/><br/> Only Static IP allocation is supported and VMM Static IP Pool is required. Follow [these steps](/system-center/vmm/network-pool?view=sc-vmm-2022&preserve-view=true) to create a VMM Static IP Pool and ensure that the Static IP Pool has at least four IP addresses. If your SCVMM server is behind a firewall, all IPs in this IP Pool and the Control Plane IP should be allowed to communicate through WinRM ports. The default WinRM ports are 5985 and 5986. <br/><br/> Dynamic IP allocation using DHCP isn't supported. <br/><br/> A library share with write permission for the SCVMM admin account through which Resource Bridge deployment is going to be performed. |
3333
| **SCVMM accounts** | An SCVMM admin account that can perform all administrative actions on all objects that VMM manages. <br/><br/> The user should be part of local administrator account in the SCVMM server. If the SCVMM server is installed in a High Availability configuration, the user should be a part of the local administrator accounts in all the SCVMM cluster nodes. <br/><br/>This will be used for the ongoing operation of Azure Arc-enabled SCVMM and the deployment of the Arc Resource bridge VM. |
3434
| **Workstation** | The workstation will be used to run the helper script.<br/><br/> A Windows/Linux machine that can access both your SCVMM management server and internet, directly or through proxy.<br/><br/> The helper script can be run directly from the VMM server machine as well.<br/><br/> To avoid network latency issues, we recommend executing the helper script directly in the VMM server machine.<br/><br/> Note that when you execute the script from a Linux machine, the deployment takes a bit longer and you might experience performance issues. |
3535

articles/defender-for-cloud/configure-email-notifications.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ description: Learn how to fine-tune the Microsoft Defender for Cloud security al
44
ms.topic: quickstart
55
ms.author: dacurwin
66
author: dcurwin
7-
ms.date: 07/23/2023
7+
ms.date: 02/25/2024
88
ms.custom: mode-other
99
---
10-
# Quickstart: Configure email notifications for security alerts
10+
# Quickstart: configure email notifications for security alerts
1111

1212
Security alerts need to reach the right people in your organization. By default, Microsoft Defender for Cloud emails subscription owners whenever a high-severity alert is triggered for their subscription. This page explains how to customize these notifications.
1313

@@ -16,13 +16,13 @@ Use Defender for Cloud's **Email notifications** settings page to define prefere
1616
- ***who* should be notified** - Emails can be sent to select individuals or to anyone with a specified Azure role for a subscription.
1717
- ***what* they should be notified about** - Modify the severity levels for which Defender for Cloud should send out notifications.
1818

19-
To avoid alert fatigue, Defender for Cloud limits the volume of outgoing mails. For each subscription, Defender for Cloud sends:
19+
To avoid alert fatigue, Defender for Cloud limits the volume of outgoing emails. For each email address, Defender for Cloud sends:
2020

2121
- approximately **four emails per day** for **high-severity** alerts
2222
- approximately **two emails per day** for **medium-severity** alerts
2323
- approximately **one email per day** for **low-severity** alerts
2424

25-
:::image type="content" source="./media/configure-email-notifications/email-notification-settings.png" alt-text="Configuring the details of the contact who is to receive emails about security alerts." :::
25+
:::image type="content" source="./media/configure-email-notifications/email-notification-settings.png" alt-text="Configuring the details of the contact who is to receive emails about security alerts." lightbox="media/configure-email-notifications/email-notification-settings.png":::
2626

2727
## Availability
2828

articles/defender-for-cloud/defender-for-storage-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Malware Scanning is charged on a per-gigabyte basis for scanned data. To ensure
102102
By default, the limit is set to 5,000 GB per month per storage account. Once this threshold is exceeded, scanning will cease for the remaining blobs, with a 20-GB confidence interval. For configuration details, refer to [configure Defender for Storage](../storage/common/azure-defender-storage-configure.md).
103103

104104
> [!IMPORTANT]
105-
> Malware scanning in Defender for Storage is not included for free in the first 30 day trial and will be charged from the first day in accordance with the pricing scheme available on the Defender for Cloud [pricing page](https://azure.microsoft.com/pricing/details/defender-for-cloud/).
105+
> Malware scanning in Defender for Storage is not included for free in the first 30 day trial and will be charged from the first day in accordance with the pricing scheme available on the Defender for Cloud [pricing page](https://azure.microsoft.com/pricing/details/defender-for-cloud/). Malware scanning will also incur additional charges for other Azure services - Azure Storage read operations, Azure Storage blob indexing and Azure Event Grid notifications.
106106
107107
### Enablement at scale with granular controls
108108

articles/defender-for-cloud/recommendations-reference-devops.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ DevOps recommendations don't affect your [secure score](secure-score-security-co
118118

119119
### [GitHub repositories should have dependency vulnerability scanning findings resolved](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/945f7b1c-8def-4ab3-a44d-1416060104b3/showSecurityCenterCommandBar~/false)
120120

121-
**Description**: GitHub repositories should have dependency vulnerability scanning findings resolved
121+
**Description**: GitHub repositories should have dependency vulnerability scanning findings resolved.
122122

123123
**Severity**: Medium
124124

@@ -192,7 +192,7 @@ DevOps recommendations don't affect your [secure score](secure-score-security-co
192192

193193
### [GitLab projects should have dependency vulnerability scanning findings resolved](https://ms.portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/1bc53aae-c92e-406b-9693-d46caf3934fa/showSecurityCenterCommandBar~/false)
194194

195-
**Description**: GitHub repositories should have dependency vulnerability scanning findings resolved
195+
**Description**: GitHub repositories should have dependency vulnerability scanning findings resolved.
196196

197197
**Severity**: Medium
198198

@@ -213,7 +213,7 @@ DevOps recommendations don't affect your [secure score](secure-score-security-co
213213

214214
### [Code repositories should have secret scanning findings resolved](https://portal.azure.com/#view/Microsoft_Azure_Security/GenericRecommendationDetailsWithRulesBlade/assessmentKey/4e07c7d0-e06c-47d7-a4a9-8c7b748d1b27/showSecurityCenterCommandBar~/false)
215215

216-
**Description**: DevOps security in Defender for Cloud has found a secret in code repositories.  This should be remediated immediately to prevent a security breach.  Secrets found in repositories can be leaked or discovered by adversaries, leading to compromise of an application or service. For Azure DevOps, the Microsoft Security DevOps CredScan tool only scans builds on which it has been configured to run. Therefore, results may not reflect the complete status of secrets in your repositories.
216+
**Description**: DevOps security in Defender for Cloud has found a secret in code repositories. This should be remediated immediately to prevent a security breach. Secrets found in repositories can be leaked or discovered by adversaries, leading to compromise of an application or service. For Azure DevOps, the Microsoft Security DevOps CredScan tool only scans builds on which it has been configured to run. Therefore, results might not reflect the complete status of secrets in your repositories.
217217
(No related policy)
218218

219219
**Severity**: High

0 commit comments

Comments
 (0)