Skip to content

Commit 43e3ee3

Browse files
authored
Merge pull request #250705 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 9a4b899 + 3c55ba2 commit 43e3ee3

File tree

7 files changed

+57
-42
lines changed

7 files changed

+57
-42
lines changed

articles/active-directory/cloud-infrastructure-entitlement-management/product-statistical-anomalies.md

Lines changed: 22 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Create and view statistical anomalies and anomaly triggers in Permissions Management
3-
description: How to create and view statistical anomalies and anomaly triggers in the Statistical Anomaly tab in Permissions Management.
2+
title: Create and view statistical anomaly alerts and alert triggers in Permissions Management
3+
description: How to create and view statistical anomaly alerts and alert triggers in the Statistical Anomaly tab in Permissions Management.
44
services: active-directory
55
author: jenniferf-skc
66
manager: amycolannino
@@ -12,13 +12,23 @@ ms.date: 02/23/2022
1212
ms.author: jfields
1313
---
1414

15-
# Create and view statistical anomalies and anomaly triggers
15+
# Create and view statistical anomaly alerts and alert triggers
1616

17-
Statistical anomalies can detect outliers in an identity's behavior if recent activity is determined to be unusual based on models defined in an activity trigger. The goal of this anomaly trigger is a high recall rate.
17+
Statistical anomalies can detect outliers in an identity's behavior if the recent activity is determined to be unusual based on models defined in an activity trigger. The goal of this alert trigger is a high recall rate.
18+
19+
You can configure statistical anomaly alert triggers for the following scenarios:
20+
- **Identity Performed High Number of Tasks**: The identity performs higher than their usual volume of tasks. For example, an identity typically performs 25 tasks per day, and now it is performing 100 tasks per day.
21+
- **Identity Performed Low Number of Tasks**: The identity performs lower than their usual volume of tasks. For example, an identity typically performs 100 tasks per day, and now it is performing 25 tasks per day.
22+
- **Identity Performed Tasks with Unusual Results**: The identity performing an action gets a different result than usual, such as most tasks end in a successful result and are now ending in a failed result or vice versa.
23+
- **Identity Performed Tasks with Unusual Timing**: The identity does tasks at unusual times as established by their baseline in the observance period. Times are grouped by the following UTC 4-hour windows.
24+
- **Identity Performed Tasks with Unusual Types**: The identity performs unusual types of tasks as established by their baseline in the observance period. For example, an identity performs read, write, or delete tasks they wouldn't ordinarily perform.
25+
- **Identity Performed Tasks with Multiple Unusual Patterns**: The identity has several unusual patterns in the tasks performed by the identity as established by their baseline in the observance period.
26+
27+
Alert triggers are based on data collected. All alerts, if triggered, are shown every hour under the Alerts subtab.
1828

1929
## View statistical anomalies in an identity's behavior
2030

21-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
31+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
2232
1. Select **Statistical Anomaly**, and then select the **Alerts** subtab.
2333

2434
The **Alerts** subtab displays the following information:
@@ -39,9 +49,9 @@ Statistical anomalies can detect outliers in an identity's behavior if recent ac
3949
- **View Trigger**: Displays the current trigger settings and applicable authorization system details
4050
- **View Trigger**: Displays the current trigger settings and applicable authorization system details
4151

42-
## Create a statistical anomaly trigger
52+
## Create a statistical anomaly alert trigger
4353

44-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
54+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
4555
1. Select **Statistical Anomaly**, select the **Alerts** subtab, and then select **Create Alert Trigger**.
4656
1. Enter a name for the alert in the **Alert Name** box.
4757
1. Select the **Authorization System**, Amazon Web Services (**AWS**), Microsoft **Azure**, or Google Cloud Platform (**GCP**).
@@ -72,9 +82,9 @@ Statistical anomalies can detect outliers in an identity's behavior if recent ac
7282

7383
1. Select **Save**.
7484

75-
## View statistical anomaly triggers
85+
## View statistical anomaly alert triggers
7686

77-
1. In the Permissions Management home page, select **Activity triggers** (the bell icon).
87+
1. In the Permissions Management home page, select **Alerts** (the bell icon).
7888
1. Select **Statistical Anomaly**, and then select the **Alert Triggers** subtab.
7989

8090
The **Alert Triggers** subtab displays the following information:
@@ -115,7 +125,7 @@ Statistical anomalies can detect outliers in an identity's behavior if recent ac
115125

116126
## Next steps
117127

118-
- For an overview on activity triggers, see [View information about activity triggers](ui-triggers.md).
128+
- For an overview on alerts and alert triggers, see [View information about alerts and alert triggers](ui-triggers.md).
119129
- For information on activity alerts and alert triggers, see [Create and view activity alerts and alert triggers](how-to-create-alert-trigger.md).
120-
- For information on rule-based anomalies and anomaly triggers, see [Create and view rule-based anomalies and anomaly triggers](product-rule-based-anomalies.md).
121-
- For information on permission analytics triggers, see [Create and view permission analytics triggers](product-permission-analytics.md).
130+
- For information on rule-based anomaly alerts and alert triggers, see [Create and view rule-based anomaly alerts and alert triggers](product-rule-based-anomalies.md).
131+
- For information on permission analytics alerts and alert triggers, see [Create and view permission analytics alerts and alert triggers](product-permission-analytics.md).

articles/azure-functions/functions-how-to-custom-container.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ To learn more about deployments to Azure Container Apps, see [Azure Container Ap
3434

3535
## Creating containerized function apps
3636

37-
Functions makes it easy to deploy and run your function apps as Linux containers, which you create and maintain. Functions maintains a set of [lanuage-specific base images](https://mcr.microsoft.com/catalog?search=functions) that you can use when creating containerized function apps.
37+
Functions makes it easy to deploy and run your function apps as Linux containers, which you create and maintain. Functions maintains a set of [language-specific base images](https://mcr.microsoft.com/catalog?search=functions) that you can use when creating containerized function apps.
3838

3939
[!INCLUDE [functions-linux-custom-container-note](../../includes/functions-linux-custom-container-note.md)]
4040

articles/azure-vmware/request-host-quota-azure-vmware-solution.md

Lines changed: 30 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ In this how-to, you'll request host quota/capacity for [Azure VMware Solution](i
1717
If you have an existing Azure VMware Solution private cloud and want more hosts allocated, you'll follow the same process.
1818

1919
>[!IMPORTANT]
20-
>It can take up to five business days to allocate the hosts, depending on the number requested.
20+
>It can take up to five business days to allocate the hosts, depending on the number requested. Therefore, request what you need for provisioning to avoid the delays associated with making additional quota increase requests.
2121
2222
## Eligibility criteria
2323

@@ -30,22 +30,24 @@ You'll need an Azure account in an Azure subscription that adheres to one of the
3030
## Request host quota for EA and MCA customers
3131

3232
1. In your Azure portal, under **Help + Support**, create a **[New support request](https://rc.portal.azure.com/#create/Microsoft.Support)** and provide the following information:
33-
- **Issue type:** Service and subcscription limits (quotas)
33+
- **Issue type:** Technical
3434
- **Subscription:** Select your subscription
35-
- **Quota type:** Azure VMware Solution
36-
37-
1. Got to **Next**. On the **Additional details** tab, under **Request details** > Enter details form:
38-
39-
- Region
40-
- SKU
41-
- Number of nodes
42-
43-
Select **Save and continue**.
35+
- **Service:** All services > Azure VMware Solution
36+
- **Resource:** General question
37+
- **Summary:** Need capacity
38+
- **Problem type:** Capacity Management Issues
39+
- **Problem subtype:** Customer Request for Additional Host Quota/Capacity
40+
41+
1. In the **Description** of the support ticket, on the **Details** tab, provide information for:
42+
43+
- Region Name
44+
- Number of hosts
45+
- Any other details, including Availability Zone requirements for integrating with other Azure services (e.g. Azure NetApp Files, Azure Blob Storage)
4446

4547
>[!NOTE]
4648
>Azure VMware Solution requires a minimum of three hosts and recommends redundancy of N+1 hosts.
4749
48-
1. Select **Next** > Under **Review + Create** > validate and click **Create to submit the request.
50+
1. Select **Review + Create** to submit the request.
4951

5052

5153
## Request host quota for CSP customers
@@ -80,22 +82,25 @@ Access the Azure portal using the **Admin On Behalf Of** (AOBO) procedure from P
8082
1. Expand customer details and select **Microsoft Azure Management Portal**.
8183

8284
1. In the Azure portal, under **Help + Support**, create a **[New support request](https://rc.portal.azure.com/#create/Microsoft.Support)** and provide the following information:
83-
- **Issue type:** Service and subcscription limits (quotas)
85+
- **Issue type:** Technical
8486
- **Subscription:** Select your subscription
85-
- **Quota type:** Azure VMware Solution
86-
87-
1. Got to **Next**. On the **Additional details** tab, under **Request details** > Enter details form:
88-
89-
- Region
90-
- SKU
91-
- Number of nodes
92-
93-
Select **Save and continue**.
94-
87+
- **Service:** All services > Azure VMware Solution
88+
- **Resource:** General question
89+
- **Summary:** Need capacity
90+
- **Problem type:** Capacity Management Issues
91+
- **Problem subtype:** Customer Request for Additional Host Quota/Capacity
92+
93+
1. In the **Description** of the support ticket, on the **Details** tab, provide information for:
94+
95+
- Region Name
96+
- Number of hosts
97+
- Any other details, including Availability Zone requirements for integrating with other Azure services (e.g. Azure NetApp Files, Azure Blob Storage)
98+
- Is intended to host multiple customers?
99+
95100
>[!NOTE]
96101
>Azure VMware Solution requires a minimum of three hosts and recommends redundancy of N+1 hosts.
97-
98-
1. Select **Next** > Under **Review + Create** > validate and click **Create** to submit the request.
102+
103+
1. Select **Review + Create** to submit the request.
99104

100105

101106
## Next steps

articles/communication-services/samples/chat-hero-sample.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ You can test the sample locally by opening multiple browser sessions with the UR
8080
8181
## Publish the sample to Azure
8282
83-
1. Under the root director, run these commands:
83+
1. Under the root directory, run these commands:
8484
```
8585
npm run setup
8686
npm run build

articles/container-registry/container-registry-helm-repos.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ The following resources are needed for the scenario in this article:
6565

6666
- **An Azure container registry** in your Azure subscription. If needed, create a registry using the [Azure portal](container-registry-get-started-portal.md) or the [Azure CLI](container-registry-get-started-azure-cli.md).
6767
- **Helm client version 3.7 or later** - Run `helm version` to find your current version. For more information on how to install and upgrade Helm, see [Installing Helm][helm-install]. If you upgrade from an earlier version of Helm 3, review the [release notes](https://github.com/helm/helm/releases).
68-
- **A Kubernetes cluster** where you will install a Helm chart. If needed, create an AKS cluster [using the Azure CLI][./learn/quick-kubernetes-deploy-cli], [using Azure PowerShell][./learn/quick-kubernetes-deploy-powershell], or [using the Azure portal][./learn/quick-kubernetes-deploy-portal].
68+
- **A Kubernetes cluster** where you will install a Helm chart. If needed, create an AKS cluster [using the Azure CLI](../aks/learn/quick-kubernetes-deploy-cli.md), [using Azure PowerShell](../aks/learn/quick-kubernetes-deploy-powershell.md), or [using the Azure portal](../aks/learn/quick-kubernetes-deploy-portal.md).
6969
- **Azure CLI version 2.0.71 or later** - Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli-install].
7070

7171
## Set up Helm client

articles/service-bus-messaging/service-bus-federation-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ These scenarios are the focus of this article.
1919

2020
There are numerous potential motivations for why you may want to move messages between Service Bus entities like Queues or Topics, or between Service Bus and other sources and targets.
2121

22-
Compared with the similar set of patterns for [Event Hubs](../service-bus-messaging/service-bus-federation-overview.md), federation for queue-like entities is more complex because message queues promise their consumers exclusive ownership over any single message, are expected to preserve arrival order in message delivery, and for the broker to coordinate fair distribution of messages between [competing consumers](/azure/architecture/patterns/competing-consumers).
22+
Compared with the similar set of patterns for [Event Hubs](../event-hubs/event-hubs-federation-overview.md), federation for queue-like entities is more complex because message queues promise their consumers exclusive ownership over any single message, are expected to preserve arrival order in message delivery, and for the broker to coordinate fair distribution of messages between [competing consumers](/azure/architecture/patterns/competing-consumers).
2323

2424
There are practical impediments, including the constraints of the [CAP theorem](https://en.wikipedia.org/wiki/CAP_theorem), that make it difficult to provide a unified view of a queue that is simultaneously available in multiple regions, and which allows for regionally distributed, [competing consumers](/azure/architecture/patterns/competing-consumers) to take exclusive ownership of messages. Such a geo-distributed queue would require fully consistent replication not only of messages, but also of the delivery state of every message before messages can be made available to consumers. A goal of a full consistency for a hypothetical, regionally distributed queue is in direct conflict with the key goal that practically all Azure Service Bus customers have when considering federation scenarios: Maximum availability and reliability for their solutions.
2525

articles/virtual-desktop/users/client-features-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ If you want to use different display settings to those specified by your admin,
6767

6868
1. Open the **Remote Desktop** application on your device.
6969

70-
1. Right-click the name of a desktop or app, for example **SessionDesktop**, then select **Settings**.
70+
1. Right-click the name of a desktop connection, for example **SessionDesktop**, then select **Settings**.
7171

7272
1. Toggle **Use default settings** to off.
7373

0 commit comments

Comments
 (0)