Skip to content

Commit 94beb2f

Browse files
authored
Merge pull request #191550 from MicrosoftDocs/main
merge main to live, 4 PM Sunday
2 parents ba9a0cc + 44ea2f9 commit 94beb2f

File tree

123 files changed

+701
-597
lines changed

Some content is hidden

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

123 files changed

+701
-597
lines changed

articles/active-directory-b2c/predicates.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 03/30/2020
12+
ms.date: 03/13/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -67,7 +67,7 @@ The **Parameter** element contains the following attributes:
6767

6868
#### IsLengthRange
6969

70-
The IsLengthRange method checks whether the length of a string claim value is within the range of minimum and maximum parameters specified. The predicate element supports the following parameters:
70+
The IsLengthRange method checks whether the length of a string claim value is within the range of minimum and maximum parameters specified. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/predicates#islengthrange-method) of this predicate method. The predicate element supports the following parameters:
7171

7272
| Parameter | Required | Description |
7373
| ------- | ----------- | ----------- |
@@ -87,7 +87,7 @@ The following example shows a IsLengthRange method with the parameters `Minimum`
8787

8888
#### MatchesRegex
8989

90-
The MatchesRegex method checks whether a string claim value matches a regular expression. The predicate element supports the following parameters:
90+
The MatchesRegex method checks whether a string claim value matches a regular expression. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/predicates#matchesregex-method) of this predicate method. The predicate element supports the following parameters:
9191

9292
| Parameter | Required | Description |
9393
| ------- | ----------- | ----------- |
@@ -105,7 +105,7 @@ The following example shows a `MatchesRegex` method with the parameter `RegularE
105105

106106
#### IncludesCharacters
107107

108-
The IncludesCharacters method checks whether a string claim value contains a character set. The predicate element supports the following parameters:
108+
The IncludesCharacters method checks whether a string claim value contains a character set. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/predicates#includescharacters-method) of this predicate method. The predicate element supports the following parameters:
109109

110110
| Parameter | Required | Description |
111111
| ------- | ----------- | ----------- |
@@ -123,7 +123,7 @@ The following example shows a `IncludesCharacters` method with the parameter `Ch
123123

124124
#### IsDateRange
125125

126-
The IsDateRange method checks whether a date claim value is between a range of minimum and maximum parameters specified. The predicate element supports the following parameters:
126+
The IsDateRange method checks whether a date claim value is between a range of minimum and maximum parameters specified. Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/predicates#isdaterange-method) of this predicate method. The predicate element supports the following parameters:
127127

128128
| Parameter | Required | Description |
129129
| ------- | ----------- | ----------- |

articles/active-directory-b2c/session-behavior.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: CelesteDG
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 02/25/2022
11+
ms.date: 03/13/2022
1212
ms.custom: project-no-code
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
@@ -147,7 +147,7 @@ To configure the session behavior in your custom policy, follow these steps:
147147

148148
## Enable Keep me signed in (KMSI)
149149

150-
You can enable the KMSI feature for users of your web and native applications who have local accounts in your Azure AD B2C directory. When you enable the feature, users can opt to stay signed in so the session remains active after they close the browser. The session is maintained by setting a [persistent cookie](cookie-definitions.md). Users who select KMSI, can reopen the browser without being prompted to reenter their username and password. This access (persistent cookie) is revoked when a user signs out.
150+
You can enable the KMSI feature for users of your web and native applications who have local accounts in your Azure AD B2C directory. When you enable the feature, users can opt to stay signed in so the session remains active after they close the browser. The session is maintained by setting a [persistent cookie](cookie-definitions.md). Users who select KMSI, can reopen the browser without being prompted to reenter their username and password. This access (persistent cookie) is revoked when a user signs out. For more information, check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/session#enable-keep-me-signed-in-kmsi).
151151

152152
![Example sign-up sign-in page showing a Keep me signed in checkbox](./media/session-behavior/keep-me-signed-in.png)
153153

@@ -401,7 +401,7 @@ To require an ID Token in logout requests:
401401

402402
::: zone pivot="b2c-custom-policy"
403403

404-
To require an ID Token in logout requests, add a **UserJourneyBehaviors** element inside of the [RelyingParty](relyingparty.md) element. Then set the **EnforceIdTokenHintOnLogout** of the **SingleSignOn** element to `true`. Your **UserJourneyBehaviors** element should look like this example:
404+
To require an ID Token in logout requests, add a **UserJourneyBehaviors** element inside of the [RelyingParty](relyingparty.md) element. Then set the **EnforceIdTokenHintOnLogout** of the **SingleSignOn** element to `true`. For more information, check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/session#enforce-id-token-hint-on-logout). Your **UserJourneyBehaviors** element should look like this example:
405405

406406
```xml
407407
<UserJourneyBehaviors>

articles/aks/gpu-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 08/06/2021
1010

1111
# Use GPUs for compute-intensive workloads on Azure Kubernetes Service (AKS)
1212

13-
Graphical processing units (GPUs) are often used for compute-intensive workloads such as graphics and visualization workloads. AKS supports the creation of GPU-enabled node pools to run these compute-intensive workloads in Kubernetes. For more information on available GPU-enabled VMs, see [GPU optimized VM sizes in Azure][gpu-skus]. For AKS node pools, we recommend a minimum size of *Standard_NC6*.
13+
Graphical processing units (GPUs) are often used for compute-intensive workloads such as graphics and visualization workloads. AKS supports the creation of GPU-enabled node pools to run these compute-intensive workloads in Kubernetes. For more information on available GPU-enabled VMs, see [GPU optimized VM sizes in Azure][gpu-skus]. For AKS node pools, we recommend a minimum size of *Standard_NC6*. Note that the NVv4 series (based on AMD GPUs) are not yet supported with AKS.
1414

1515
> [!NOTE]
1616
> GPU-enabled VMs contain specialized hardware that is subject to higher pricing and region availability. For more information, see the [pricing][azure-pricing] tool and [region availability][azure-availability].
@@ -435,4 +435,4 @@ For information on using Azure Kubernetes Service with Azure Machine Learning, s
435435
[azureml-aks]: ../machine-learning/how-to-deploy-azure-kubernetes-service.md
436436
[azureml-gpu]: ../machine-learning/how-to-deploy-inferencing-gpus.md
437437
[azureml-triton]: ../machine-learning/how-to-deploy-with-triton.md
438-
[aks-container-insights]: monitor-aks.md#container-insights
438+
[aks-container-insights]: monitor-aks.md#container-insights

articles/attestation/overview.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: references_regions
1212
---
1313
# Microsoft Azure Attestation
1414

15-
Microsoft Azure Attestation is a unified solution for remotely verifying the trustworthiness of a platform and integrity of the binaries running inside it. The service supports attestation of the platforms backed by Trusted Platform Modules (TPMs) alongside the ability to attest to the state of Trusted Execution Environments (TEEs) such as [Intel® Software Guard Extensions](https://www.intel.com/content/www/us/en/architecture-and-technology/software-guard-extensions.html) (SGX) enclaves, [Virtualization-based Security](/windows-hardware/design/device-experiences/oem-vbs) (VBS) enclaves, [Trusted Platform Modules (TPMs)](/windows/security/information-protection/tpm/trusted-platform-module-overview), [Trusted launch for Azure VMs](/azure/virtual-machines/trusted-launch#microsoft-defender-for-cloud-integration) and [Azure confidential VMs](/azure/confidential-computing/confidential-vm-overview).
15+
Microsoft Azure Attestation is a unified solution for remotely verifying the trustworthiness of a platform and integrity of the binaries running inside it. The service supports attestation of the platforms backed by Trusted Platform Modules (TPMs) alongside the ability to attest to the state of Trusted Execution Environments (TEEs) such as [Intel® Software Guard Extensions](https://www.intel.com/content/www/us/en/architecture-and-technology/software-guard-extensions.html) (SGX) enclaves, [Virtualization-based Security](/windows-hardware/design/device-experiences/oem-vbs) (VBS) enclaves, [Trusted Platform Modules (TPMs)](/windows/security/information-protection/tpm/trusted-platform-module-overview), [Trusted launch for Azure VMs](/azure/virtual-machines/trusted-launch) and [Azure confidential VMs](/azure/confidential-computing/confidential-vm-overview).
1616

1717
Attestation is a process for demonstrating that software binaries were properly instantiated on a trusted platform. Remote relying parties can then gain confidence that only such intended software is running on trusted hardware. Azure Attestation is a unified customer-facing service and framework for attestation.
1818

@@ -24,9 +24,9 @@ Azure Attestation receives evidence from compute entities, turns them into a set
2424

2525
Azure Attestation provides comprehensive attestation services for multiple environments and distinctive use cases.
2626

27-
### SGX attestation
27+
### SGX enclave attestation
2828

29-
SGX refers to hardware-grade isolation, which is supported on certain Intel CPUs models. SGX enables code to run in sanitized compartments known as SGX enclaves. Access and memory permissions are then managed by hardware to ensure a minimal attack surface with proper isolation.
29+
[Intel® Software Guard Extensions](https://www.intel.com/content/www/us/en/architecture-and-technology/software-guard-extensions.html) (SGX) refers to hardware-grade isolation, which is supported on certain Intel CPUs models. SGX enables code to run in sanitized compartments known as SGX enclaves. Access and memory permissions are then managed by hardware to ensure a minimal attack surface with proper isolation.
3030

3131
Client applications can be designed to take advantage of SGX enclaves by delegating security-sensitive tasks to take place inside those enclaves. Such applications can then make use of Azure Attestation to routinely establish trust in the enclave and its ability to access sensitive data.
3232

@@ -35,14 +35,14 @@ Intel® Xeon® Scalable processors only support [ECDSA-based attestation solutio
3535
> [!NOTE]
3636
> To perform attestation of Intel® Xeon® Scalable processor-based server platforms using Azure Attestation, users are expected to install [Azure DCAP version 1.10.0](https://github.com/microsoft/Azure-DCAP-Client) or higher.
3737
38-
### Open Enclave
38+
### Open Enclave attestation
3939
[Open Enclave](https://openenclave.io/sdk/) (OE) is a collection of libraries targeted at creating a single unified enclaving abstraction for developers to build TEE-based applications. It offers a universal secure app model that minimizes platform specificities. Microsoft views it as an essential stepping-stone toward democratizing hardware-based enclave technologies such as SGX and increasing their uptake on Azure.
4040

4141
OE standardizes specific requirements for verification of an enclave evidence. This qualifies OE as a highly fitting attestation consumer of Azure Attestation.
4242

4343
### TPM attestation
4444

45-
Trusted Platform Module (TPM) based attestation is critical to provide proof of a platforms’ state. TPM acts as the root of trust and the security coprocessor to provide cryptographic validity to the measurements(evidence). Devices with a TPM, can rely on attestation to prove that boot integrity is not compromised along with using the claims to detect feature states enablement’s during boot.
45+
[Trusted Platform Modules (TPM)](/windows/security/information-protection/tpm/trusted-platform-module-overview) based attestation is critical to provide proof of a platforms’ state. TPM acts as the root of trust and the security coprocessor to provide cryptographic validity to the measurements(evidence). Devices with a TPM, can rely on attestation to prove that boot integrity is not compromised along with using the claims to detect feature states enablement’s during boot.
4646

4747
Client applications can be designed to take advantage of TPM attestation by delegating security-sensitive tasks to only take place after a platform has been validated to be secure. Such applications can then make use of Azure Attestation to routinely establish trust in the platform and its ability to access sensitive data.
4848

articles/azure-monitor/alerts/alerts-action-rules.md

Lines changed: 38 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -171,11 +171,25 @@ For example, to create a rule that adds an action group to all alerts in a subsc
171171
az monitor alert-processing-rule create \
172172
--name 'AddActionGroupToSubscription' \
173173
--rule-type AddActionGroups \
174-
--scopes "/subscriptions/MySubscriptionId" \
175-
--action-groups "/subscriptions/MySubscriptionId/resourcegroups/MyResourceGroup1/providers/microsoft.insights/actiongroups/ActionGroup1" \
174+
--scopes "/subscriptions/sub1" \
175+
--action-groups "/subscriptions/sub1/resourcegroups/rg1/providers/microsoft.insights/actiongroups/ag1" \
176176
--enabled true \
177-
--resource-group alertscorrelationrg \
178-
--description "Add ActionGroup1 to all alerts in the subscription"
177+
--resource-group rg1 \
178+
--description "Add action group ag1 to all alerts in the subscription"
179+
```
180+
181+
The [CLI documentation](/cli/azure/monitor/alert-processing-rule#az-monitor-alert-processing-rule-create) include more examples and an explanation of each parameter.
182+
183+
### [PowerShell](#tab/powershell)
184+
185+
### Create an alert processing rule using PowerShell
186+
187+
Use the `Set-AzAlertProcessingRule` command to create alert processing rules.
188+
For example, to create a rule that adds an action group to all alerts in a subscription, run:
189+
190+
```powershell
191+
Set-AzAlertProcessingRule -ResourceGroupName rg1 -Name AddActionGroupToSubscription -Scope /subscriptions/MySubId -Description "Add action group ag1 to all alerts in the subscription" -AlertProcessingRuleType AddActionGroups -ActionGroupId /subscriptions/sub1/resourcegroups/rg1/providers/microsoft.insights/actiongroups/ag1
192+
179193
```
180194

181195
The [CLI documentation](/cli/azure/monitor/alert-processing-rule#az-monitor-alert-processing-rule-create) include more examples and an explanation of each parameter.
@@ -212,6 +226,26 @@ az monitor alert-processing-rules update --resource-group MyResourceGroupName --
212226
az monitor alert-processing-rules delete --resource-group MyResourceGroupName --name MyRule
213227
```
214228

229+
### [PowerShell](#tab/powershell)
230+
231+
You can view and manage your alert processing rules using the [\*-AzAlertProcessingRule](/powershell/module/az.alertsmanagement) commands from Azure CLI.
232+
233+
Before you manage alert processing rules with the Azure CLI, prepare your environment using the instructions provided in [Configuring an alert processing rule](#configuring-an-alert-processing-rule).
234+
235+
```powershell
236+
# List all alert processing rules for a subscription
237+
Get-AzAlertProcessingRule
238+
239+
# Get details of an alert processing rule
240+
Get-AzAlertProcessingRule -ResourceGroupName MyResourceGroupName -Name MyRule | Format-List
241+
242+
# Update an alert processing rule
243+
Update-AzAlertProcessingRule -ResourceGroupName MyResourceGroupName -Name MyRule -Enabled False
244+
245+
# Delete an alert processing rule
246+
Remove-AzAlertProcessingRule -ResourceGroupName MyResourceGroupName -Name MyRule
247+
```
248+
215249
* * *
216250

217251
## Next steps

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Reference table for all Microsoft Defender for Cloud recommendations for AWS resources
33
description: This article lists Microsoft Defender for Cloud's security recommendations that help you harden and protect your AWS resources.
44
ms.topic: reference
5-
ms.date: 01/12/2022
5+
ms.date: 03/13/2022
66
ms.custom: generated
77
---
88
# Security recommendations for AWS resources - a reference guide

articles/defender-for-cloud/release-notes.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,8 @@ Updates in March include:
2525
- [Defender for Containers can now scan for vulnerabilities in Windows images (preview)](#defender-for-containers-can-now-scan-for-vulnerabilities-in-windows-images-preview)
2626
- [New alert for Microsoft Defender for Storage (preview)](#new-alert-for-microsoft-defender-for-storage-preview)
2727
- [Configure email notifications settings from an alert](#configure-email-notifications-settings-from-an-alert)
28-
28+
- [Deprecated preview alert: ARM.MCAS_ActivityFromAnonymousIPAddresses](#deprecated-preview-alert-armmcas_activityfromanonymousipaddresses)
29+
2930
### Deprecated the recommendations to install the network traffic data collection agent
3031

3132
Changes in our roadmap and priorities have removed the need for the network traffic data collection agent. Consequently, the following two recommendations and their related policies were deprecated.
@@ -62,6 +63,18 @@ A new section has been added to the alert User Interface (UI) which allows you t
6263

6364
Learn how to [Configure email notifications for security alerts](configure-email-notifications.md).
6465

66+
### Deprecated preview alert: ARM.MCAS_ActivityFromAnonymousIPAddresses
67+
68+
The following preview alert has been deprecated:
69+
70+
|Alert name| Description|
71+
|----------------------|---------------------------|
72+
|**PREVIEW - Activity from a risky IP address**<br>(ARM.MCAS_ActivityFromAnonymousIPAddresses)|Users activity from an IP address that has been identified as an anonymous proxy IP address has been detected.<br>These proxies are used by people who want to hide their device's IP address, and can be used for malicious intent. This detection uses a machine learning algorithm that reduces false positives, such as mis-tagged IP addresses that are widely used by users in the organization.<br>Requires an active Microsoft Defender for Cloud Apps license.|
73+
74+
A new alert has been created that provides this information and adds to it. In addition, the newer alerts (ARM_OperationFromSuspiciousIP, ARM_OperationFromSuspiciousProxyIP) doesn't require a license for Microsoft Defender for Cloud Apps (formerly known as Microsoft Cloud App Security).
75+
76+
See more alerts for [Resource Manager](alerts-reference.md#alerts-resourcemanager).
77+
6578
## February 2022
6679

6780
Updates in February include:

0 commit comments

Comments
 (0)