Skip to content

Commit 635064c

Browse files
author
Mandi Ohlinger
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/memdocs-pr into ado36009095
2 parents dbbc10c + 2a180f7 commit 635064c

269 files changed

Lines changed: 6758 additions & 4125 deletions

File tree

Some content is hidden

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

.openpublishing.redirection.intune.json

Lines changed: 157 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,120 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "intune/analytics/adoption-score.md",
5+
"redirect_url": "/intune/endpoint-analytics/adoption-score",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "intune/analytics/app-reliability.md",
10+
"redirect_url": "/intune/endpoint-analytics/app-reliability",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "intune/analytics/configure.md",
15+
"redirect_url": "/intune/endpoint-analytics/configure",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "intune/analytics/data-collection.md",
20+
"redirect_url": "/intune/endpoint-analytics/data-collection",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "intune/analytics/get-support.md",
25+
"redirect_url": "/intune/endpoint-analytics/get-support",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "intune/analytics/index.md",
30+
"redirect_url": "/intune/endpoint-analytics",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "intune/analytics/restart-frequency.md",
35+
"redirect_url": "/intune/endpoint-analytics/startup-perfomance#restart-frequency",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "intune/analytics/scores.md",
40+
"redirect_url": "/intune/endpoint-analytics/scores",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "intune/analytics/startup-performance.md",
45+
"redirect_url": "/intune/endpoint-analytics/startup-performance",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "intune/analytics/troubleshoot.md",
50+
"redirect_url": "/intune/endpoint-analytics/faq",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "intune/analytics/work-from-anywhere.md",
55+
"redirect_url": "/intune/endpoint-analytics/work-from-anywhere",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "intune/analytics/advanced-analytics.md",
60+
"redirect_url": "/intune/advanced-analytics",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "intune/analytics/data-platform-schema.md",
65+
"redirect_url": "/intune/advanced-analytics/data-platform-schema",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "intune/analytics/anomaly-detection.md",
70+
"redirect_url": "/intune/advanced-analytics/anomalies",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "intune/analytics/battery-health.md",
75+
"redirect_url": "/intune/advanced-analytics/battery-health",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "intune/analytics/advanced-analytics-deploy.md",
80+
"redirect_url": "/intune/advanced-analytics/deploy",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "intune/analytics/device-query-multiple-devices.md",
85+
"redirect_url": "/intune/advanced-analytics/device-query-multiple-devices",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "intune/analytics/device-query.md",
90+
"redirect_url": "/intune/advanced-analytics/device-query",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "intune/analytics/device-scopes.md",
95+
"redirect_url": "/intune/advanced-analytics/device-scopes",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "intune/analytics/enhanced-device-timeline.md",
100+
"redirect_url": "/intune/advanced-analytics/device-timeline",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "intune/analytics/advanced-analytics-plan.md",
105+
"redirect_url": "/intune/advanced-analytics/plan",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "intune/analytics/resource-performance-report.md",
110+
"redirect_url": "/intune/advanced-analytics/resource-performance-report",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "intune/analytics/advanced-analytics-troubleshooting-faqs.md",
115+
"redirect_url": "/intune/advanced-analytics/troubleshoot",
116+
"redirect_document_id": false
117+
},
3118
{
4119
"source_path": "intune/intune-service/protect/vulnerability-remediation-agent.md",
5120
"redirect_url": "/intune/agents/vulnerability-remediation-agent",
@@ -17,17 +132,17 @@
17132
},
18133
{
19134
"source_path": "intune/analytics/enroll-configmgr.md",
20-
"redirect_url": "/intune/intune-service/analytics/set-up?pivots=cm#enroll-devices",
135+
"redirect_url": "/intune/endpoint-analytics/configure?pivots=cm",
21136
"redirect_document_id": false
22137
},
23138
{
24139
"source_path": "intune/analytics/enroll-intune.md",
25-
"redirect_url": "/intune/intune-service/analytics/set-up?pivots=intune#enroll-devices",
140+
"redirect_url": "/intune/endpoint-analytics/configure?pivots=intune",
26141
"redirect_document_id": false
27142
},
28143
{
29144
"source_path": "intune/analytics/settings.md",
30-
"redirect_url": "/intune/intune-service/analytics/set-up",
145+
"redirect_url": "/intune/endpoint-analytics/configure",
31146
"redirect_document_id": false
32147
},
33148
{
@@ -37,7 +152,7 @@
37152
},
38153
{
39154
"source_path": "intune/analytics/overview.md",
40-
"redirect_url": "/intune/analytics",
155+
"redirect_url": "/intune/endpoint-analytics",
41156
"redirect_document_id": false
42157
},
43158
{
@@ -432,12 +547,42 @@
432547
},
433548
{
434549
"source_path": "intune/intune/apps/mamedge-5-end-user-experience.md",
435-
"redirect_url": "/intune/intune-service/apps/mamedge-5-end-user-experience",
550+
"redirect_url": "/intune/intune-service/apps/mamedge-7-end-user-experience",
551+
"redirect_document_id": false
552+
},
553+
{
554+
"source_path": "intune/intune/apps/mamedge-5-settings-catalog.md",
555+
"redirect_url": "/intune/intune-service/apps/mamedge-5-settings-catalog",
556+
"redirect_document_id": false
557+
},
558+
{
559+
"source_path": "intune/intune/apps/mamedge-6-security-baseline.md",
560+
"redirect_url": "/intune/intune-service/apps/mamedge-6-security-baseline",
436561
"redirect_document_id": false
437562
},
438563
{
439564
"source_path": "intune/intune/apps/mamedge-6-troubleshoot.md",
440-
"redirect_url": "/intune/intune-service/apps/mamedge-6-troubleshoot",
565+
"redirect_url": "/intune/intune-service/apps/mamedge-8-troubleshoot",
566+
"redirect_document_id": false
567+
},
568+
{
569+
"source_path": "intune/intune-service/apps/mamedge-5-end-user-experience.md",
570+
"redirect_url": "/intune/intune-service/apps/mamedge-7-end-user-experience",
571+
"redirect_document_id": false
572+
},
573+
{
574+
"source_path": "intune/intune-service/apps/mamedge-6-troubleshoot.md",
575+
"redirect_url": "/intune/intune-service/apps/mamedge-8-troubleshoot",
576+
"redirect_document_id": false
577+
},
578+
{
579+
"source_path": "intune/intune/apps/mamedge-7-end-user-experience.md",
580+
"redirect_url": "/intune/intune-service/apps/mamedge-7-end-user-experience",
581+
"redirect_document_id": false
582+
},
583+
{
584+
"source_path": "intune/intune/apps/mamedge-8-troubleshoot.md",
585+
"redirect_url": "/intune/intune-service/apps/mamedge-8-troubleshoot",
441586
"redirect_document_id": false
442587
},
443588
{
@@ -2662,7 +2807,12 @@
26622807
},
26632808
{
26642809
"source_path": "intune/intune/protect/data-leak-prevention.md",
2665-
"redirect_url": "/intune/intune-service/protect/data-leak-prevention",
2810+
"redirect_url": "/intune/intune-service/fundamentals/deployment-guide-enrollment-mamwe",
2811+
"redirect_document_id": false
2812+
},
2813+
{
2814+
"source_path": "intune/intune-service/protect/data-leak-prevention.md",
2815+
"redirect_url": "/intune/intune-service/fundamentals/deployment-guide-enrollment-mamwe",
26662816
"redirect_document_id": false
26672817
},
26682818
{

.openpublishing.redirection.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1276,7 +1276,7 @@
12761276
},
12771277
{
12781278
"source_path": "intune/analytics/whats-new.md",
1279-
"redirect_url": "/intune/analytics/overview",
1279+
"redirect_url": "/intune/endpoint-analytics",
12801280
"redirect_document_id": false
12811281
},
12821282
{
@@ -1526,7 +1526,7 @@
15261526
},
15271527
{
15281528
"source_path": "intune/analytics/recommended-software.md",
1529-
"redirect_url": "/intune/analytics/work-from-anywhere",
1529+
"redirect_url": "/intune/endpoint-analytics/work-from-anywhere",
15301530
"redirect_document_id": true
15311531
},
15321532
{
@@ -1561,7 +1561,7 @@
15611561
},
15621562
{
15631563
"source_path": "intune/analytics/productivity-score.md",
1564-
"redirect_url": "/intune/analytics/adoption-score",
1564+
"redirect_url": "/intune/endpoint-analytics/adoption-score",
15651565
"redirect_document_id": false
15661566
},
15671567
{
@@ -1631,7 +1631,7 @@
16311631
},
16321632
{
16331633
"source_path": "intune/analytics/proactive-remediations.md",
1634-
"redirect_url": "/intune/analytics/remediations",
1634+
"redirect_url": "/intune/intune-service/fundamentals/remediations",
16351635
"redirect_document_id": false
16361636
},
16371637
{
@@ -2650,7 +2650,7 @@
26502650
},
26512651
{
26522652
"source_path": "intune/analytics/advanced-endpoint-analytics.md",
2653-
"redirect_url": "/intune/analytics/advanced-analytics",
2653+
"redirect_url": "/intune/advanced-analytics",
26542654
"redirect_document_id": false
26552655
},
26562656
{

autopilot/device-preparation/includes/reporting-monitoring.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,3 +57,6 @@ Headings are driven by article context. -->
5757
- **In progress** - The PowerShell script is currently running.
5858
- **Skipped** - Usually indicates that the PowerShell script was selected in the Windows Autopilot device preparation policy, but wasn't assigned to the device group specified in the Windows Autopilot device preparation policy.
5959
- **Failed** - The PowerShell script failed to run. Check logs for further details.
60+
61+
> [!Important]
62+
> Windows 365 devices that are reprovisioned after a failed deployment will not be deleted from Intune and will remain in the Autopilot device preparation report to allow for you to download the diagnostic logs when an error occurs. To clean up the stale records, use [Intune cleanup rules](/intune/intune-service/fundamentals/device-cleanup-rules) or delete manually.

autopilot/device-preparation/requirements.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -92,12 +92,10 @@ Additional configuration might be required to grant access to required services
9292
9393
Windows Autopilot device preparation relies on several different type of services to function properly. In order for these services to function properly, certain network configurations might need to be performed. These services and their required network configurations are as follows:
9494
95-
#### Windows Autopilot device preparation deployment service
95+
#### Windows Autopilot deployment service
9696
97-
After a network connection is in place, each Windows device will contact the Windows Autopilot device preparation deployment service. The following URLs are used:
97+
After a network connection is in place, each Windows device will contact the Windows Autopilot deployment service. The following URLs are used:
9898
99-
- `https://ztd.dds.microsoft.com`
100-
- `https://cs.dds.microsoft.com`
10199
- `https://login.live.com`
102100
103101
#### Windows activation
Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Anomalies Report in Advanced Analytics
3+
description: Discover how anomalies report in Microsoft Intune Advanced Analytics helps IT admins monitor device health, detect issues, and get actionable insights to improve endpoint reliability.
4+
ms.date: 12/01/2025
5+
ms.topic: concept-article
6+
---
7+
8+
# Anomalies report
9+
10+
[!INCLUDE [intune-add-on-note](../intune-service/includes/intune-add-on-note.md)]
11+
12+
The anomalies report in Advanced Analytics helps IT admins proactively identify device health issues before they affect users. It monitors for application hangs, crashes, and Stop Error Restarts, providing visibility into problems before they reach support channels.
13+
14+
The feature correlates deployment objects and configuration changes to speed troubleshooting and suggest root causes. Device correlation groups reveal patterns among affected devices and flag others that are at risk.
15+
16+
## Before you begin
17+
18+
> [!div class="checklist"]
19+
> - Review [Scores, baselines, and insights in endpoint analytics](../endpoint-analytics/scores.md) to understand these concepts.
20+
> - Confirm that your environment meets all [prerequisites](index.md#prerequisites).
21+
22+
## Review the report
23+
24+
1. In the [Microsoft Intune admin center][INT-AC], select **Reports** > **Endpoint analytics** > **Overview**.
25+
1. Select the **Anomalies** tab, which provides an overview of the anomalies detected in your organization.
26+
27+
:::image type="content" source="images/anomaly-detection/anomalies-tab.png" lightbox="images/anomaly-detection/anomalies-tab.png" alt-text="Screenshot of the Anomaly tab in Overview section of endpoint analytics.":::
28+
29+
- Use sorting and filtering capabilities to refine the list of anomalies.
30+
- To view more information about a specific anomaly, select it from the list. Review details such as the app name, affected devices, when the issue was first detected and last occurred, and any device groups that might be contributing to the problem.
31+
:::image type="content" source="images/anomaly-detection/details-of-anomaly.png" lightbox="images/anomaly-detection/details-of-anomaly.png" alt-text="Screenshot of details displayed when you select an anomaly displayed in the Anomaly tab.":::
32+
- Select a device correlation group from the list to see common factors among devices. Devices are correlated by shared attributes such as app version, driver update, OS version, or device model. You can view the number of devices currently affected and those at risk. The **prevalence rate** shows the percentage of affected devices in a correlation group.
33+
:::image type="content" source="images/anomaly-detection/select-corelation-group.png" lightbox="images/anomaly-detection/select-corelation-group.png" alt-text="Screenshot showing Device correlation groups.":::
34+
- Select **View Affected Devices** to display a list of devices with key attributes. Filter to view devices in specific correlation groups or show all devices affected by the anomaly. The device timeline also shows additional anomalous events.
35+
:::image type="content" source="images/anomaly-detection/affected-devices.png" lightbox="images/anomaly-detection/affected-devices.png" alt-text="Screenshot showing a list of affected devices.":::
36+
37+
## Review anomaly detection data
38+
39+
Investigate flagged device correlation groups using the device timeline and resource reports to determine root causes. Device correlation groups help identify root causes for high and medium severity anomalies, as well as at-risk devices that may be impacted in the future.
40+
41+
**Best practices:**
42+
- Periodically review the anomalies dashboard to understand the current baseline and prioritize investigations and resolutions for new issues.
43+
- Investigate new reported issues to identify common factors, such as device hardware, as shown in advanced analytics.
44+
- Prioritize anomalies to investigate based on severity and internal knowledge, such as application criticality.
45+
- Use the [device timeline](device-timeline.md) report to check for patterns, such as device restarts or updates tied to anomalies.
46+
- Work with IT teams to identify other factors, such as recent application updates, that could impact anomalies.
47+
- Review possible remediation actions noted in the anomaly report (for example, driver or application updates).
48+
- Integrate resolutions into L1/L2 support to keep teams aware of current known issues. Consider working with your ITSM team to record known anomalies under investigation.
49+
- Test remediation actions on a subset of devices and monitor results before rolling out to more devices. After remediation, proactively roll out to at-risk devices.
50+
- Review anomalies reports after major updates or incidents to check for new issues that need investigation and resolution.
51+
- To better understand detection methods, review the [statistical models](#statistical-models-for-determining-anomalies) used by anomaly detection.
52+
53+
54+
## Statistical models for determining anomalies
55+
56+
The analytical model detects device cohorts facing anomalous sets of Stop Error Restarts and application hangs or crashes that need admin attention. Patterns identified from sensor telemetry and diagnostics logs determine these device cohorts.
57+
58+
- **Threshold-based heuristic model**: This model sets one or more threshold values for application hangs, crashes, or Stop Error Restarts. Devices are flagged as anomalous if they breach the set threshold. The model is simple and effective for surfacing prominent or static issues. Thresholds are currently predetermined and not customizable.
59+
- **Paired t-tests model**: Paired t-tests compare pairs of observations in a dataset, looking for statistically significant differences between their means. For example, comparing Stop Error Restarts on the same device before and after a policy change, or app crashes after an OS update.
60+
- **Population Z-score model**: This model calculates the standard deviation and mean of a dataset, then uses those values to determine which data points are anomalous. The Z-score for each data point represents the number of standard deviations from the mean. Data points outside a certain range are considered anomalous. This model is well suited for highlighting outlier devices or apps but requires large datasets to be accurate.
61+
- **Time series Z-score model**: This variation of the Z-score model is designed for detecting anomalies in time series data—sequences of data points collected at regular intervals, such as Stop Error Restarts over time. Standard deviation and mean are calculated for a sliding window, allowing the model to adapt to temporal patterns and changes in data distribution.
62+
63+
> [!NOTE]
64+
> Device cohorts are only identified for medium and high-severity anomalies.
65+
66+
<!--links-->
67+
68+
[INT-AC]: https://go.microsoft.com/fwlink/?linkid=2109431

0 commit comments

Comments
 (0)