Merge pull request #7613 from MicrosoftDocs/main

Publish 05/16/2022 3:30 PM PT

Author: Angela Fleischmann

memdocs/intune/apps/store-apps-company-portal-autopilot.md

@@ -40,7 +40,7 @@ To manage devices and install apps, your users can use the Company Portal app. Y
 
 For Windows 10 Autopilot provisioned devices, it is recommended that you associate your Microsoft Store for Business account with Intune. For more information, see [How to manage volume purchased apps from the Microsoft Store for Business with Microsoft Intune](windows-store-for-business.md).
 
-You can choose to install the **Company Portal (Offline)** app using the steps below. The Company Portal app will be installed in device context when assigned to the Autopilot group and will be installed on the device before the user logs in. Offline apps are updated using Intune, whereas online apps are updated by the store. When synced from the Microsoft Store for Business and deployed as a Microsoft Store app, the Company Portal (Offline) updates will occur automatically to any required assignments. If you need to maintain a specific version of the Company Portal app, refer to [Manually add the Windows 10 company portal app](/mem/intune/apps/store-apps-company-portal-app) for details.
+You can choose to install the **Company Portal (Offline)** app using the steps below. The Company Portal app will be installed in device context when assigned to the Autopilot group and will be installed on the device before the user logs in. Offline apps are updated using Intune, whereas online apps are updated by the store. When synced from the Microsoft Store for Business and deployed as a Microsoft Store app, the Company Portal (Offline) updates will occur automatically to any required assignments. If you need to maintain a specific version of the Company Portal app, refer to [Manually add the Windows 10 company portal app](./store-apps-company-portal-app.md) for details.
 
 ## Configure the store settings to show the offline app
 
@@ -77,5 +77,4 @@ You can choose to install the **Company Portal (Offline)** app using the steps b
 
 ## Next steps
 
-- To learn more about assigning apps, see [Assign apps to groups](apps-deploy.md).
-
+- To learn more about assigning apps, see [Assign apps to groups](apps-deploy.md).

memdocs/intune/configuration/wired-network-settings-windows.md

@@ -87,7 +87,7 @@ This article describes the settings you can configure.
       - **PKCS certificate**: Select an existing PKCS **client certificate** profile and existing trusted **root certificate** that are also deployed to the device. The client certificate is the identity presented by the device to the server to authenticate the connection.
       - **PFX Import certificate**: Select an existing imported PFX certificate profile. The client certificate is the identity presented by the device to authenticate the connection.
 
-        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](/mem/intune/protect/certificates-imported-pfx-configure).
+        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](../protect/certificates-imported-pfx-configure.md).
 
       - **Derived credential**: Select an existing certificate profile that's derived from a user's smart card. For more information, see [Use derived credentials in Microsoft Intune](../protect/derived-credentials.md).
 
@@ -114,7 +114,7 @@ This article describes the settings you can configure.
 
       - **PFX Import certificate**: Select an existing imported PFX certificate profile. The client certificate is the identity presented by the device to authenticate the network connection.
 
-        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](/mem/intune/protect/certificates-imported-pfx-configure).
+        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](../protect/certificates-imported-pfx-configure.md).
 
         - **Identity privacy (outer identity)**: Enter the text sent in response to an EAP identity request. This text can be any value, such as `anonymous`. During authentication, this anonymous identity is initially sent, and then followed by the real identification sent in a secure tunnel.
 
@@ -150,7 +150,7 @@ This article describes the settings you can configure.
 
       - **PFX Import certificate**: Select an existing imported PFX certificate profile. The client certificate is the identity presented by the device to authenticate the network connection.
 
-        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](/mem/intune/protect/certificates-imported-pfx-configure).
+        For more information on imported PFX certificates, see [Configure and use imported PKCS certificates with Intune](../protect/certificates-imported-pfx-configure.md).
 
         - **Identity privacy (outer identity)**: Enter the text sent in response to an EAP identity request. This text can be any value, such as `anonymous`. During authentication, this anonymous identity is initially sent, and then followed by the real identification sent in a secure tunnel.
 
@@ -160,4 +160,4 @@ This article describes the settings you can configure.
 
 The profile is created, but it may not be doing anything. Be sure to [assign this profile](device-profile-assign.md), and [monitor its status](device-profile-monitor.md).
 
-[Wired network settings for macOS devices](wired-network-settings-macos.md)
+[Wired network settings for macOS devices](wired-network-settings-macos.md)

memdocs/intune/fundamentals/review-logs-using-azure-monitor.md

@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 04/25/2022
+ms.date: 05/16/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -94,19 +94,19 @@ Depending on where you want to route the audit log data, you need one of the fol
 
             [Azure log analytics workspace](/azure/azure-monitor/learn/quick-create-workspace) provides more details on these settings.
 
-    - **LOG** > **AuditLogs**: Choose this option to send the [Intune audit logs](monitor-audit-logs.md) to your storage account, event hub, or log analytics. The audit logs show the history of every task that generates a change in Intune, including who did it and when.
+    - **LOG** > **AuditLogs**: Choose this option to send the [Intune audit logs](monitor-audit-logs.md) to your storage account, event hub, or log analytics. The audit logs show the history of every task that generates a change in Intune, including who did it and when. For more reference information, go to [IntuneAuditLogs](/azure/azure-monitor/reference/tables/IntuneAuditLogs).
 
       If you choose to use a storage account, then also enter how many days you want to keep the data (retention). To keep data forever, set **Retention (days)** to `0` (zero).
 
-    - **LOG** > **OperationalLogs**: Operational logs show the success or failure of users and devices that enroll in Intune, as well as details on non-compliant devices. Choose this option to send the enrollment logs to your storage account, event hub, or log analytics.
+    - **LOG** > **OperationalLogs**: Operational logs show the success or failure of users and devices that enroll in Intune, as well as details on non-compliant devices. Choose this option to send the enrollment logs to your storage account, event hub, or log analytics. For more reference information, go to [IntuneOperationalLogs](/azure/azure-monitor/reference/tables/IntuneOperationalLogs).
 
       If you choose to use a storage account, then also enter how many days you want to keep the data (retention). To keep data forever, set **Retention (days)** to `0` (zero).
 
-    - **LOG** > **DeviceComplianceOrg**: Device compliance organizational logs show the organizational report for Device Compliance in Intune, and details of non-compliant devices. Choose this option to send the compliance logs to your storage account, event hub, or log analytics.
+    - **LOG** > **DeviceComplianceOrg**: Device compliance organizational logs show the organizational report for Device Compliance in Intune, and details of non-compliant devices. Choose this option to send the compliance logs to your storage account, event hub, or log analytics. For more reference information, go to [IntuneDeviceComplianceOrg](/azure/azure-monitor/reference/tables/IntuneDeviceComplianceOrg).
 
       If you choose to use a storage account, then also enter how many days you want to keep the data (retention). To keep data forever, set **Retention (days)** to `0` (zero).
 
-    - **LOG** > **IntuneDevices**: The Intune Device log shows device inventory and status information for Intune enrolled and managed devices. Choose this option to send the IntuneDevices logs to your storage account, event hub, or log analytics.
+    - **LOG** > **IntuneDevices**: The Intune Device log shows device inventory and status information for Intune enrolled and managed devices. Choose this option to send the IntuneDevices logs to your storage account, event hub, or log analytics. For more reference information, go to [IntuneDevices](/azure/azure-monitor/reference/tables/IntuneDevices).
 
       If you choose to use a storage account, then also enter how many days you want to keep the data (retention). To keep data forever, set **Retention (days)** to `0` (zero).
 

windows-365/enterprise/manage-cloud-pcs-using-configuration-manager.md

@@ -43,7 +43,7 @@ To manage Cloud PCs by using Configuration Manager co-management, you must meet
 - [Enable co-management in Configuration Manager](/mem/configmgr/comanage/how-to-enable).
 - Distribute the ccmsetup.msi installer as a Line-of-Business (LOB) client app from Microsoft Intune. For more information, see How to [Install the Configuration Manager client](/mem/configmgr/comanage/how-to-prepare-win10#install-the-configuration-manager-client).
 
-For an easier client application deployment, you can create an Azure AD group based on model type, using filters, or all devices of a Windows 365 provisioning profile.  For more information, see [Create a dynamic device group containing your Cloud PCs](/windows-365/enterprise/create-dynamic-device-group-all-cloudpcs).
+For an easier client application deployment, you can create an Azure AD group based on model type, using filters, or all devices of a Windows 365 provisioning profile.  For more information, see [Create a dynamic device group containing your Cloud PCs](./create-dynamic-device-group-all-cloudpcs.md).
 
 ## Co-management workloads for Windows 365 Cloud PCs
 
@@ -56,4 +56,4 @@ If you have a large number of applications to migrate to Microsoft Intune, consi
 <!-- ########################## -->
 ## Next steps
 
-For more information about co-management and how to set it up, see [What is co-management?]( /mem/configmgr/comanage/overview) 
+For more information about co-management and how to set it up, see [What is co-management?]( /mem/configmgr/comanage/overview)