Skip to content

Commit a6f6d1b

Browse files
acrolinx
1 parent ca305eb commit a6f6d1b

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

intune/intune-service/configuration/device-profile-troubleshoot.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -29,11 +29,11 @@ This article applies to the following policies:
2929

3030
## Policy refresh intervals
3131

32-
When a device syncs with Intune, it checks for configuration for the current user/device context, receiving any pending actions, policies and apps assigned to it.
32+
When a device syncs with Intune, it checks for configuration for the current user or device context, and receives any pending actions, policies, and apps assigned to it.
3333

3434
For app protection policy refresh intervals, go to [App Protection Policy delivery timing](../apps/app-protection-policy-delivery.md).
3535

36-
There are 3 main types of device syncs - change-based, client initiated, and single device.
36+
There are three main types of device syncs - change-based, client initiated, and single device.
3737

3838
### Change-based
3939

@@ -48,7 +48,7 @@ An offline device, like when it's powered off, or a disconnected device, might n
4848

4949
> [!NOTE]
5050
>
51-
> - It might take additional time for Intune reports to reflect the latest status of the policy on the device in the Intune portal.
51+
> - It can take more time for Intune reports to reflect the latest status of the policy on the device in the Intune portal.
5252
> - To receive push notifications, devices must connect to specific network endpoints. For a list of network endpoints, see [Network endpoints for Microsoft Intune](../fundamentals/intune-endpoints.md#intune-dependencies).
5353
>
5454
> - [Windows dependencies](../fundamentals/intune-endpoints.md#windows-push-notification-services-wns-dependencies)
@@ -57,24 +57,24 @@ An offline device, like when it's powered off, or a disconnected device, might n
5757
5858
### Client initiated
5959

60-
Thee following client syncs happen in response to a device event or state change, like when a user signs into the device or if the malware status changes:
60+
The following client syncs happen in response to a device event or state change, like when a user signs into the device or if the malware status changes:
6161

62-
- **Maintenance syncs** - These syncs include a large amount of client-initiated syncs and they occur at predetermined intervals. They can be initiated by the client or service depending on the platform. The estimated check-in schedule for all platforms is about every 8 hours.
62+
- **Maintenance syncs** - These syncs include a large number of client-initiated syncs and they occur at predetermined intervals. The client or service can initiate the sync, depending on the platform. The estimated check-in schedule for all platforms is about every 8 hours.
6363

64-
Independent of the client schedule, devices are only allowed 1 maintenance sync every 6.5 hours.
64+
Independent of the client schedule, devices are only allowed one maintenance sync every 6.5 hours.
6565

66-
- **Newly enrolled devices** - When devices first enroll, syncs run more frequently to run configuration, compliance, and non-compliance checks. The check-ins are estimated at:
66+
- **Newly enrolled devices** - When devices first enroll, syncs run more frequently to run configuration, compliance, and noncompliance checks. The check-ins are estimated at:
6767

6868
| Platform | Estimated refresh cycle|
6969
| --- | --- |
7070
| Android, AOSP | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
7171
| iOS/iPadOS | Every 15 minutes for 1 hour, and then around every 8 hours |
7272
| macOS | Every 15 minutes for 1 hour, and then around every 8 hours |
73-
| Windows PCs enrolled as devices | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
73+
| Windows | Every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, and then around every 8 hours |
7474

7575
### Single device
7676

77-
These check-ins are driven by admins or end users when they run certain actions on a single device:
77+
Admins or end users initiate these check-ins when they run certain actions on a single device:
7878

7979
- **End-users actions** - Includes actions made by users in the Company Portal website or app, like [checking the compliance status](../user-help/check-status-company-portal-website.md), syncing for policy or profile updates, or [installing apps](../user-help/manage-apps-cpweb.md#available-and-required-apps).
8080

@@ -180,7 +180,7 @@ For more information on dynamic groups, go to:
180180

181181
On Windows devices, when trying to sync in the **Settings** app > **Accounts** > **Access work or school**, you might see a `The sync could not be initiated (0x80072f9a)` error.
182182

183-
If the Trusted Platform Module (TPM) was reset to factory settings, then the device must reenrolled to resume syncing. The device's Microsoft Entra identity is stored in the TPM. So, if the ID is removed, then reenrollment is the only way to reestablish the Microsoft Entra identity.
183+
If the Trusted Platform Module (TPM) was reset to factory settings, then the device must reenroll to resume syncing. The device's Microsoft Entra identity is stored in the TPM. So, if the ID is removed, then reenrollment is the only way to reestablish the Microsoft Entra identity.
184184

185185
## Related articles
186186

0 commit comments

Comments
 (0)