Merge pull request #10062 from MicrosoftDocs/main

Publish 03/03/2023 3:30 PM PT

Author: Angela Fleischmann

memdocs/analytics/app-reliability.md

@@ -87,6 +87,9 @@ The **Device performance** tab displays application reliability insights for eac
 
 Selecting a device name opens the **Application reliability** tab for that device. This tab displays a timeline of app crash and app unresponsive events for the device over a specified period of time, up to 14 days. Use the **Filter** option at the top of the timeline to select a custom time range.
 
+> [!Note]
+> In the **Device performance** tabs of Endpoint analytics, admins will only see devices they have access to according to their assigned Scope tags. To learn more about Scope tags, see [Scope tags for distributed IT](../intune/fundamentals/scope-tags.md). Aggregated insights, such as scores and summary views are calculated using all enrolled devices in the tenant. To apply Scope tags to aggregated insights, see [Device scopes in Endpoint analytics](device-scopes.md).
+
 ## Known issues
 
 [!INCLUDE [Endpoint analytics export to csv value mapping known issue](includes/known-issue-csv-mapping.md)]

memdocs/analytics/restart-frequency.md

@@ -48,6 +48,9 @@ The difference between **Shutdown (no update)** and **Restart (no update)** is t
 
 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.
 
+> [!Note]
+> In the **Device performance** tabs of Endpoint analytics, admins will only see devices they have access to according to their assigned Scope tags. To learn more about Scope tags, see [Scope tags for distributed IT](../intune/fundamentals/scope-tags.md). Aggregated insights, such as scores and summary views are calculated using all enrolled devices in the tenant. To apply Scope tags to aggregated insights, see [Device scopes in Endpoint analytics](device-scopes.md).
+
 ## 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 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.

memdocs/analytics/startup-performance.md

@@ -69,6 +69,9 @@ The **Startup performance** page has reporting tabs that provide support for the
 
 - **Model performance**. This tab lets you see the boot and sign-in performance by device model, which can help you identify if performance problems are isolated to particular models.
 - **Device performance**. This tab provides boot and sign-in metrics for all your devices. You can sort by a particular metric (for example, GP sign-in time) to see which devices have the worst scores for that metric to help with troubleshooting. You can also search for a device by name. If you click through a device you can see its boot and sign-in history, which can help you identify if there was a recent regression
+  > [!Note]
+  > In the **Device performance** tabs of Endpoint analytics, admins will only see devices they have access to according to their assigned Scope tags. To learn more about Scope tags, see [Scope tags for distributed IT](../intune/fundamentals/scope-tags.md). Aggregated insights, such as scores and summary views are calculated using all enrolled devices in the tenant. To apply Scope tags to aggregated insights, see [Device scopes in Endpoint analytics](device-scopes.md).
+
 - **Startup processes**. Startup processes can negatively impact the user experience by increasing the length of time that users must wait for the desktop to become responsive. This tab will show you which processes are impacting the sign-in "time to responsive desktop" phase, that is - keeping the CPU above 50% after the desktop has rendered. The table only lists processes that impact a minimum of 10 devices in your tenant. When reviewing startup processes, the following data calculations are displayed:
    - **Device count**: The count of devices that experienced a delay to a responsive desktop from the process.
    - **Median delay**: The median delay time of the process for the counted devices.

memdocs/analytics/work-from-anywhere.md

@@ -35,6 +35,10 @@ The following metrics are weighted and used to compute the **Work from anywhere
 - [Cloud provisioning](#bkmk_provisioning)
 
 :::image type="content" source="media/8668496-work-from-anywhere-score.png" alt-text="Screenshot of the Work from anywhere report showing the scores and metrics" lightbox="media/8668496-work-from-anywhere-score.png":::
+
+> [!Note]
+> In the device-level views of Work from anywhere, admins will only see devices they have access to according to their assigned Scope tags. To learn more about Scope tags, see [Scope tags for distributed IT](../intune/fundamentals/scope-tags.md). Aggregated insights, such as the Work from anywhere score, are calculated using all enrolled devices in the tenant. To apply Scope tags to aggregated insights, see [Device scopes in Endpoint analytics](device-scopes.md).
+
 ## Windows
 
 Newer versions of Windows provide a better user experience than older versions of Windows. The **Windows** metric measures the percent of devices on supported versions of Windows. The recommended remediation actions vary depending on how the devices are managed. For Intune and co-managed devices, use Intune to [move devices to an updated version of Windows](../intune/protect/windows-10-feature-updates.md). For Configuration Manager devices, create a deployment plan using [Desktop Analytics](../configmgr/desktop-analytics/overview.md). Your score is based on if these remediation actions have been completed or not.

memdocs/intune/fundamentals/whats-new.md

@@ -116,7 +116,13 @@ For licensing details see [Intune add-ons](../fundamentals/intune-add-ons.md).
 
 Applies to:  
 - Android
-- iOS
+- iOS  
+
+### Tenant administration  
+
+#### Organizational messages now support custom destination URLs <!-- 16576068  -->
+
+You can now add any custom destination URL to organizational messages in the taskbar, notifications area, and Get Started app. This feature applies to Windows 11. Messages created with Azure AD-registered domains that are in a scheduled or active state are still supported. For more information, see [Create organizational messages](../remote-actions/organizational-messages-create.md?tabs=taskbar#step-1-create-a-message). 
 
 ## Week of February 20, 2023 (Service release 2302)
 

memdocs/intune/remote-actions/collect-diagnostics.md

@@ -151,20 +151,20 @@ Event Viewers:
 
 Files:
 
-- %ProgramData%\Microsoft\DiagnosticLogCSP\Collectors\*.etl
-- %ProgramData%\Microsoft\IntuneManagementExtension\Logs\*.*
+- %ProgramData%\Microsoft\DiagnosticLogCSP\Collectors\\*.etl
+- %ProgramData%\Microsoft\IntuneManagementExtension\Logs\\\*.*
 - %ProgramData%\Microsoft\Windows Defender\Support\MpSupportFiles.cab
 - %ProgramData%\Microsoft\Windows\WlanReport\wlan-report-latest.html
-- %ProgramData Microsoft Update Health Tools\Logs\*.etl
+- %ProgramData Microsoft Update Health Tools\Logs\\*.etl
 - %temp%\MDMDiagnostics\battery-report.html
 - %temp%\MDMDiagnostics\energy-report.html
 - %temp%\MDMDiagnostics\mdmlogs-<Date/Time>.cab
 - %temp%\MDMDiagnostics\msinfo32.log
-- %windir%\ccm\logs\*.log
-- %windir%\ccmsetup\logs\*.log
+- %windir%\ccm\logs\\*.log
+- %windir%\ccmsetup\logs\\*.log
 - %windir%\logs\CBS\cbs.log
-- %windir%\logs\measuredboot\*.*
-- %windir%\Logs\WindowsUpdate\*.etl
+- %windir%\logs\measuredboot\\\*.*
+- %windir%\logs\WindowsUpdate\\*.etl
 - %windir%\temp\%computername%*.log
 - %windir%\temp\officeclicktorun*.log
 
@@ -176,7 +176,7 @@ The **Collect diagnostics** remote action is enabled by default. You can disable
 2. Navigate to **Tenant administration** > **Device diagnostics**.
 3. Change the control under **Device diagnostics are available for corporate-managed devices running Windows 10, version 1909 and later, or Windows 11.** to **Disabled**.
 
-     :::image type="content" source="./media/collect-diagnostics/disable-device-diagnostics.png" alt-text="Screenshot that shows the Device diagnostics pane with the highlighted control for device diagnostics set to Disabled.":::
+     :::image type="content" source="./media/collect-diagnostics/disable-device-diagnostics.png" alt-text="Screenshot that shows the Device diagnostics pane with the highlighted control for device diagnostics set to Disabled." lightbox="./media/collect-diagnostics/disable-device-diagnostics.png":::
 
 ## Disable Autopilot automatic collection of diagnostics
 <!--1895390-->
@@ -187,7 +187,7 @@ Autopilot automatic diagnostic capture is enabled by default. You can disable Au
 2. Navigate to **Tenant administration** > **Device diagnostics**.
 3. Change the control under **Automatically capture diagnostics when devices experience a failure during the Autopilot process on Windows 10 version 1909 or later and Windows 11. Diagnostics may include user identifiable information such as user or device name (preview).** to **Disabled**.
 
-     :::image type="content" source="./media/collect-diagnostics/disable-autopilot-diagnostics.png" alt-text="Screenshot that shows the Device diagnostics pane with the highlighted control for Autopilot automatic diagnostics collection set to Disabled.":::
+     :::image type="content" source="./media/collect-diagnostics/disable-autopilot-diagnostics.png" alt-text="Screenshot that shows the Device diagnostics pane with the highlighted control for Autopilot automatic diagnostics collection set to Disabled." lightbox="./media/collect-diagnostics/disable-autopilot-diagnostics.png":::
 
 ## WinGet troubleshooting using diagnostic files
 [WinGet](/windows/package-manager/winget/) is a command line tool that enables you to discover, install, upgrade, remove, and configure applications on Windows 10 and Windows 11 devices. When working with [Win32 app management in Intune](../apps/apps-win32-app-management.md), you can use the following files to help troubleshoot WinGet:

memdocs/intune/remote-actions/organizational-messages-create.md

@@ -6,7 +6,7 @@ keywords:
 author: Lenewsad
 ms.author: lanewsad
 manager: dougeby
-ms.date: 11/28/2022
+ms.date: 03/03/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -60,9 +60,8 @@ Create and configure a message for the taskbar area.
 4. Select **OK**.  
 5. On the **Message** page, select **Add a logo**, and then choose an image file. For requirements, see [Logo requirements](organizational-messages-prerequisites.md#logo-requirements).  
 6. (Optional) **Provide a link for the message**: To include a URL link in your message:  
-   * Select the domain you want to use. The list contains all Azure AD verified custom domain names in your tenant. Example: `www.contoso.com` 
-   * (Optional) Select **Add a link path, if needed** and add the path for your URL. Example: `/SoftwareUpdate`   
-   * Select the full generated link to make sure it works. Example: `www.contoso.com/SoftwareUpdate`     
+   1. Enter your custom URL. Example: `www.contoso.com/SoftwareUpdate`     
+   2. Select the full generated link to make sure it works.     
 7. **Choose language to preview**: Select a language to preview the localized version of your message. The message is shown to employees in the [display language](https://support.microsoft.com/windows/manage-the-input-and-display-language-settings-in-windows-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2) they've selected on their device. Organizational messages are supported in 15 languages. If the employee's preferred language isn't supported, the message will appear in their preferred fallback language.  
 8. **Preview the message in dark theme**: Turn on the toggle to view how your message appears in dark theme. Check to make sure your logo shows up correctly in both light and dark theme.  
 9. Select **Next: Schedule** to continue to scheduling options. 
@@ -83,9 +82,8 @@ Create and configure a message for the notification area.
 3. Select **OK**.  
 4. On the **Message** page, select **Add a logo**, and then choose an image file. For requirements, see [Logo requirements](organizational-messages-prerequisites.md#logo-requirements).  
 5. (Optional) **Provide a link for the message**: To include a URL link in your message:  
-      * Select the domain you want to use. The list contains all Azure AD verified custom domain names in your tenant. Example: `www.contoso.com` 
-      * (Optional) Select **Add a link path, if needed** and add the path for your URL. Example: `/SoftwareUpdate`   
-      * Select the full generated link to make sure it works. Example: `www.contoso.com/SoftwareUpdate`     
+    1. Enter your custom URL. Example: `www.contoso.com/SoftwareUpdate`     
+    2. Select the full generated link to make sure it works.  
 6. **Choose language to preview**: Select a language to preview the localized version of your message. The message is shown to employees in the [display language](https://support.microsoft.com/windows/manage-the-input-and-display-language-settings-in-windows-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2) they've selected on their device. Organizational messages are supported in 15 languages. If the employee's preferred language isn't supported, the message will appear in their preferred fallback language.  
 7. **Preview the message in dark theme**: Turn on the toggle to view how your message appears in dark theme. Check to make sure your logo shows up correctly in both light and dark theme.   
 8. Select **Next: Schedule** to continue to scheduling options.   
@@ -102,10 +100,9 @@ Create and configure a message for the Get Started app.
         * **Review benefits**
         * **Review organization**
         * **Get started with device**
-     3. **Provide a link for the message**: To include a URL link in your message:
-        * Select the domain you want to use. The list contains all Azure AD verified custom domain names in your tenant. Example: `www.contoso.com` 
-        * (Optional) Select **Add a link path, if needed** and add the path for your URL. Example: `/SoftwareUpdate`   
-        * Select the full generated link to make sure it works. Example: `www.contoso.com/SoftwareUpdate`      
+     3. **Provide a link for the message**: To include a URL link in your message:  
+          1. Enter your custom URL. Example: `www.contoso.com/SoftwareUpdate`     
+          2. Select the full generated link to make sure it works.     
      4. Select **OK**.  
      5. Select **Add your second message**. Options include: 
         * **Organizational training**

memdocs/intune/remote-actions/organizational-messages-prerequisites.md

@@ -6,7 +6,7 @@ keywords:
 author: Lenewsad
 ms.author: lanewsad
 manager: dougeby
-ms.date: 12/07/2022
+ms.date: 03/03/2023
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -68,9 +68,6 @@ Logos must meet these requirements:
     * Notification area messages: 48 x 48 pixels
     * Get Started app messages: 50 pixels long x 50 - 100 pixels wide  
 
-## URL requirements  
-The domain for your custom destination URLs must be added to your list of verified Azure AD custom domain names. For more information, see [Add your custom domain - Azure Active Directory](/azure/active-directory/fundamentals/add-custom-domain#add-your-custom-domain-name-to-azure-ad).  
-
 ## Policy requirements  
 There are certain experience and Windows Spotlight policies in Microsoft Intune that block the delivery of organizational messages. This section describes how to adjust all settings so that delivery is always allowed and works as intended. 
 

memdocs/intune/toc.yml

@@ -1329,6 +1329,14 @@ items:
           href: ./remote-actions/device-inventory.md
         - name: Collect diagnostics
           href: ./remote-actions/collect-diagnostics.md
+        - name: Send organizational messages  
+          items: 
+          - name: Overview 
+            href: ./remote-actions/organizational-messages-overview.md
+          - name: Prerequisites for organizational messages    
+            href: ./remote-actions/organizational-messages-prerequisites.md
+          - name: Create organizational messages  
+            href: ./remote-actions/organizational-messages-create.md
       - name: Bulk device actions
         href: ./remote-actions/bulk-device-actions.md
       - name: Troubleshooting