Merge branch 'main' into release-win365-reports

Author: v-alje

memdocs/analytics/restart-frequency.md

@@ -46,21 +46,21 @@ The difference between **Shutdown (no update)** and **Restart (no update)** is t
 
 ## Device performance tab
 
-In the device performance tab, two default columns have been added so you can review the total number of restarts and the number of Stop errors (blue screen errors) each device had in the last 14 days. Sort by these columns to find problematic devices. You can also use this tab to review the total number of devices that have sent restart records. For example, the screenshot below has 31 records, meaning 31 devices have sent restart data.
+In the device performance tab, two default columns have been added so you can review the total number of restarts and the number of Stop errors (blue screen errors) each device had in the last 30 days. Sort by these columns to find problematic devices. You can also use this tab to review the total number of devices that have sent restart records. For example, the screenshot below has 31 records, meaning 31 devices have sent restart data.
 
 ## Model performance tab
 
-In the model performance tab, two default columns have been added so you can review both the average number of restarts and the average number of Stop errors (blue screen errors) per model over the last 14 days. Sort by these columns to find problematic device models. Only models with at least 10 devices are shown to ensure the averages are done across enough devices to be meaningful.
+In the model performance tab, two default columns have been added so you can review both the average number of restarts and the average number of Stop errors (blue screen errors) per model over the last 30 days. Sort by these columns to find problematic device models. Only models with at least 10 devices are shown to ensure the averages are done across enough devices to be meaningful.
 
 ## Restart frequency tab
 
-The new restart frequency tab shows aggregates of restart frequency counts for each of the [restart categories](#restart-categories) over the last 14 days. For each restart category, the following information is displayed:
+The new restart frequency tab shows aggregates of restart frequency counts for each of the [restart categories](#restart-categories) over the last 30 days. For each restart category, the following information is displayed:
 
 - Number of devices that have had at least one restart in that category
 - The average number of restarts per device across all devices, to understand the total impact.
   - This average is all devices, not just the ones that had at least one restart in the category.
 
-The trend chart indicates how the rolling 14-day average changes over time. If there is a regression you'll be able to see it and identify when it started. Clicking through the metrics table will take you to the [**Device performance** tab](#device-performance-tab), sorted by number of restarts, so you can quickly identify the devices with the most restarts.
+The trend chart indicates how the rolling 30-day average changes over time. If there is a regression you'll be able to see it and identify when it started. Clicking through the metrics table will take you to the [**Device performance** tab](#device-performance-tab), sorted by number of restarts, so you can quickly identify the devices with the most restarts.
 
 :::image type="content" source="media/restart-frequency-tab.png" alt-text="Restart frequency tab under Startup Performance" lightbox="media/restart-frequency-tab.png":::
 
@@ -76,13 +76,13 @@ The **OS restart history** table has the following information:
 
 :::image type="content" source="media/device-page-os-restart-history.png" alt-text="OS restart history under the Device page" lightbox="media/device-page-os-restart-history.png":::
 
-The **OS restart history** table is truncated to the 10 most recent restarts that occurred in the last 2 months. The table is low latency, so new restarts typically show up here before they appear in the daily aggregates shown in the **Device performance** tab.
+The **OS restart history** table is truncated to the 10 most recent restarts that occurred in the last 30 days. The table is low latency, so new restarts typically show up here before they appear in the daily aggregates shown in the **Device performance** tab.
 
 ## Known issues
 
 - The count of restarts in a device's restart history in the [**Devices page**](#devices-page) may not match the count shown in the **Device performance** tab. This is by design. The differences are: 
-   - The aggregates in the [**Device performance** tab](#device-performance-tab) are computed daily to show counts for the last 14 days
-	- The restart history in the [**Devices page**](#devices-page) is truncated to the 10 most recent restarts and goes back up to the last 2 months. This page also has low latency, so new restarts will typically show up here before they make their way into the daily aggregates shown in the **Device performance** tab. The [**Device performance** tab](#device-performance-tab) doesn't have that truncation and goes back for the last 14 days.
+   - The aggregates in the [**Device performance** tab](#device-performance-tab) are computed daily to show counts for the last 30 days
+   - The restart history in the [**Devices page**](#devices-page) is truncated to the 10 most recent restarts
 
 - Currently, there isn't an aggregation of Stop errors (blue screen errors) by *driver* or *failure bucket ID*.
 

memdocs/intune/fundamentals/reports.md

@@ -201,7 +201,7 @@ To view the **Feature update failures** report, use the following steps:
 > [!IMPORTANT]  
 > To get a complete picture of Windows feature updates status, use the following feature updates reports:
 >
-> - **[Windows 10 and later feature updates (Organizational)](#windows-10-and-later-feature-updates-organizational)**
+> - **[Windows 10 feature updates (Organizational)](#windows-10-feature-updates-organizational)**
 > - **Feature update failures report (Operational)** *(this report)*  
 >
 > Together, these reports provide insight into the update state and compliance of Windows devices in your organization and can help you troubleshoot problems with feature update deployment.  
@@ -387,24 +387,24 @@ Other reports for Microsoft Defender Antivirus include:
 - [Antivirus agent status report](#antivirus-agent-status-report-organizational), an organizational report detailed in this article.
 - [Antivirus policy reports](../protect/endpoint-security-antivirus-policy.md#antivirus-policy-reports), which are available in the Antivirus node under Endpoint security in the Microsoft Endpoint Manager admin center.
 
-## Windows 10 and later feature updates (Organizational)
+## Windows 10 feature updates (Organizational)
 
-A Windows update report, the **Windows 10 and later feature updates** report provides an overall view of compliance for devices that are targeted with a **Feature updates for Windows 10 and later** policy. This report provides the update status based on update state. You can also see specific device update details. The data found in these reports is timely, calls out the device name and state, and other update related details. A summary report is available in the **Windows updates** workload. This report also provides filtering, searching, paging, and sorting.
+A Windows update report, the **Windows 10 feature updates** report provides an overall view of compliance for devices that are targeted with a **Feature updates for Windows 10 and later** policy. This report provides the update status based on update state. You can also see specific device update details. The data found in these reports is timely, calls out the device name and state, and other update related details. A summary report is available in the **Windows updates** workload. This report also provides filtering, searching, paging, and sorting.
 
 For information about how to use this report to resolve update failures, see [Reports for Windows 10 and later feature updates policy](../protect/windows-10-feature-updates.md).
 
-You can view the **Windows 10 and later feature updates** report using the following steps:
+You can view the **Windows 10 feature updates** report using the following steps:
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
 2. Select **Reports** > **Windows updates** to view the summary report.
-3. Select the **Reports** tab and select the **Windows Feature Update Report** to see the **Windows 10 and later feature updates** report.
+3. Select the **Reports** tab and select the **Windows Feature Update Report** to see the **Windows 10 feature updates** report.
 4. Select the **Update aggregated status** and **Ownership** filters to refine your report.
 5. Select **Generate report** (or **Generate again**) to retrieve current data.
 
 > [!IMPORTANT]  
 > To get a complete picture of Windows feature updates status, use the following feature updates reports:
 >
-> - Windows 10 and later feature updates (Organizational) *(this report)*
+> - Windows 10 feature updates (Organizational) *(this report)*
 > - [Feature update failures report (Operational)](#feature-update-failures-report-operational)
 >
 > Together, these reports provide insight into the update state and compliance of Windows devices in your organization and can help you troubleshoot problems with feature update deployment.  

memdocs/intune/fundamentals/specialty-devices-with-intune.md

@@ -0,0 +1,57 @@
+---
+# required metadata
+
+title: Managing Specialty devices with Microsoft Intune
+titleSuffix: 
+description: What are specialty devices and how can you manage them with Microsoft Intune?
+keywords:
+author: Smritib17
+ms.author: smbhardwaj
+manager: dougeby
+ms.date: 10/04/2022
+ms.topic: conceptual
+ms.service: microsoft-intune
+ms.subservice: fundamentals
+ms.localizationpriority: high
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: priyar
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-classic; get-started; seodec18
+ms.collection: 
+  - M365-identity-device-management
+  - highpri
+---
+
+# Managing Specialty devices with Microsoft Intune
+
+The ability to manage specialty devices in Intune will require additional licensing when Microsoft launches the Intune premium suite and it’s related add-ons. To learn more, see [Premium add-ons for Microsoft Intune](premium-add-ons.md)
+
+## What are specialized devices in Intune  
+
+A device managed by Microsoft Intune will be classified as a specialized device if it meets at least one of the following requirements:
+
+- Large smart screen devices, over 30” in size
+- AR/VR headsets
+- Wearable headsets
+- Printers
+- Conference room meeting devices, a software-based room system that provides an integrated experience for audio conferencing, wireless screen sharing, or video conferencing
+- Excludes
+    - Laptops and tablet devices
+    - Foldable messaging devices
+    - Mobile devices extension such as wearables/watches where the data is managed through mobile apps on iOS and Android mobile phones
+    - Devices that are included in the plans for frontline workers. See [License Eligibility for Frontline Worker Licenses](https://www.microsoft.com/licensing/terms/en-US/productoffering/Microsoft365/EAEAS)
+    - IoT devices
+
+
+
+## Next Steps
+
+Learn about enrolling devices into Microsoft Intune here: 
+- [Enroll devices into Microsoft Intune](../enrollment/device-enrollment.md) 

memdocs/intune/fundamentals/toc.yml

@@ -214,6 +214,8 @@ items:
     href: ../fundamentals/policy-sets.md
   - name: Premium add-ons
     href: premium-add-ons.md
+  - name: Specialty devices with Intune
+    href: specialty-devices-with-intune.md    
   - name: Developer guidance
     href: ../developer/index.yml
   - name: Get help and support