Skip to content

Commit fef1d7a

Browse files
committed
bookmark
1 parent 917892e commit fef1d7a

3 files changed

Lines changed: 5 additions & 5 deletions

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ ms.collection: M365-identity-device-management
3232

3333
Get answers to common questions when working with device profiles and policies in Intune. This article also lists the check-in time intervals, provides more detains on conflicts, and more.
3434

35-
## How long does it take for devices to get a policy, profile, or app after it's assigned?
35+
## How long does it take for devices to get a policy, profile, or app after they are assigned?
3636

3737
Intune notifies the device to check in with the Intune service. The notification times vary, including immediately up to a few hours. These notification times also vary between platforms.
3838

memdocs/intune/configuration/tutorial-walkthrough-administrative-templates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ This feature applies to:
6666
6767
## Prerequisites
6868

69-
- A Microsoft 365 E3 or E5 subscription, which includes Intune and Azure Active Directory (AD) premium. If you don't have an E3 or E5 subscription, [try it for free](/office365/admin/try-or-buy-microsoft-365?view=o365-worldwide).
69+
- A Microsoft 365 E3 or E5 subscription, which includes Intune and Azure Active Directory (AD) premium. If you don't have an E3 or E5 subscription, [try it for free](/office365/admin/try-or-buy-microsoft-365).
7070

7171
For more information on what you get with the different Microsoft 365 licenses, see [Transform your Enterprise with Microsoft 365](https://www.microsoft.com/microsoft-365/compare-all-microsoft-365-plans).
7272

@@ -447,7 +447,7 @@ At this point, you created some administrative templates, and assigned them to g
447447
This section uses the following resources. We'll install these resources in this section.
448448

449449
- [Intune PowerShell SDK](https://github.com/microsoft/Intune-PowerShell-SDK)
450-
- [Microsoft Graph API for Intune](/graph/api/resources/intune-graph-overview?view=graph-rest-1.0)
450+
- [Microsoft Graph API for Intune](/graph/api/resources/intune-graph-overview)
451451

452452
1. On the **Admin computer**, open **Windows PowerShell** as administrator:
453453

memdocs/intune/fundamentals/migrate-to-intune.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ ms.collection: M365-identity-device-management
3333

3434
This article will help you migrate your mobile device management (MDM) from Basic Mobility and Security (Office 365) to the Microsoft Endpoint Manager portal (Intune).
3535

36-
Moving to Intune combines all your MDM in one solution. It lets all your users benefit from the wider set of features offered by Intune. To see a comparison of the features available in the two services, see [Choose between Basic Mobility and Security or Intune]( https://docs.microsoft.com/microsoft-365/admin/basic-mobility-security/choose-between-basic-mobility-and-security-and-intune).
36+
Moving to Intune combines all your MDM in one solution. It lets all your users benefit from the wider set of features offered by Intune. To see a comparison of the features available in the two services, see [Choose between Basic Mobility and Security or Intune](/microsoft-365/admin/basic-mobility-security/choose-between-basic-mobility-and-security-and-intune).
3737

3838
After migrating to Intune, the existing device security policies deployed with Basic Mobility and Security will be permanently frozen.
3939

@@ -103,7 +103,7 @@ To migrate policies from Basic Mobility and Security to Intune, follow these ste
103103
The policy recommendation on this page isn’t itself an Intune policy. It’s only a read-only report documenting the suggested settings and assignments to use. While reviewing the recommendations, keep these points in mind:
104104
- If the groups listed in the recommendation already have Intune policies assigned to them, these may conflict with the recommended settings. To learn how conflicts are handled for a specific setting, refer to the documentation for [device configuration](../configuration/device-profiles.md) or [device compliance](../protect/device-compliance-get-started.md).
105105
> [!NOTE]
106-
> If you make any changes to the migrated email profiles or fail to assign them to recommended groups, users may be asked to re-enter their username and password to access email on their devices when the device migrates to Intune. See [policy mapping for Configuration](https://docs.microsoft.com/mem/intune/fundamentals/policy-map-configurations
106+
> If you make any changes to the migrated email profiles or fail to assign them to recommended groups, users may be asked to re-enter their username and password to access email on their devices when the device migrates to Intune. See [policy mapping for Configuration](policy-map-configurations.md)
107107
- If there are already Intune-licensed users in the recommended groups, verify that the recommended policies will also be appropriate for them. After you assign the policies to these groups, all Intune licensed users will receive them, even users not previously managed by Basic Mobility and Security.
108108
6. If you want to implement the recommended policy, choose **Open policy**. This opens the actual policy page. Initially, the policy doesn’t have any groups assigned to it. This means that it’s not affecting any users who are licensed for Intune and happened to be in the same groups assigned to the original device security policy. You’ll need to assign the recommended groups to the Intune policy to replace the device settings configured in Basic Mobility and Security. If you don’t, devices managed by Basic Mobility and Security could lose settings and email configuration when their users are licensed for Intune causing their devices to migrate.
109109
> [!NOTE]

0 commit comments

Comments
 (0)