Skip to content

Commit 33467dc

Browse files
committed
review updates
1 parent bf883c7 commit 33467dc

2 files changed

Lines changed: 9 additions & 6 deletions

File tree

memdocs/solutions/cloud-native-endpoints/cloud-native-endpoints-planning-guide.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,10 @@ To be successful, consider the key areas described in this article for your plan
5050

5151
Managing your endpoints, including cloud-native endpoints, is an important task for all organizations. With cloud-native endpoints, the management tools you use must manage the endpoints wherever they go.
5252

53-
If you don't currently use a mobile device management (MDM) solution, or want to move to a Microsoft solution, then look at [What is Microsoft Intune?](../../intune/fundamentals/what-is-intune.md) and [Get started with Microsoft Intune](../../intune/fundamentals/get-started-with-intune.md).
53+
If you don't currently use a mobile device management (MDM) solution, or want to move to a Microsoft solution, then the following articles are good resources:
54+
55+
- [What is Microsoft Intune?](../../intune/fundamentals/what-is-intune.md)
56+
- [Get started with Microsoft Intune](../../intune/fundamentals/get-started-with-intune.md)
5457

5558
With the Microsoft Intune family of products and services, you have the following endpoint management options:
5659

@@ -302,7 +305,7 @@ The following phases are a high-level approach for organizations to move their e
302305

303306
### ✅ Phase 1: Define endpoints, dependencies, and milestones
304307

305-
This phase is the first step for your organization migration to be fully cloud-native. Look at what you currently have, define success criteria, and start planning how your devices will be added to Azure AD.
308+
This phase is the first step for your organization migration to be fully cloud-native. Review what you currently have, define success criteria, and start planning how your devices will be added to Azure AD.
306309

307310
1. **Define the endpoints that require a cloud identity**
308311

memdocs/solutions/cloud-native-endpoints/cloud-native-windows-endpoints.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ This feature applies to:
4343
- Windows cloud-native endpoints
4444

4545
> [!TIP]
46-
> If you’re looking for a Microsoft recommended, standardized solution to build on top of, then you might be interested in [Windows in cloud configuration](https://www.microsoft.com/microsoft-365/windows/cloud-configuration). In Intune, you can configure Windows in cloud configuration using a [Guided Scenario](../../intune/fundamentals/guided-scenarios-overview.md).
46+
> If you want a Microsoft recommended, standardized solution to build on top of, then you might be interested in [Windows in cloud configuration](https://www.microsoft.com/microsoft-365/windows/cloud-configuration). In Intune, you can configure Windows in cloud configuration using a [Guided Scenario](../../intune/fundamentals/guided-scenarios-overview.md).
4747
>
4848
> The follow table describes the key difference between this guide and *Windows in cloud configuration*:
4949
>
@@ -87,7 +87,7 @@ If your wireless network requires certificates, you can start with an Ethernet c
8787

8888
### Step 2 - Enrollment and Licensing
8989

90-
Before you can join Azure AD and enroll in Intune, there are a few things you need to check. You could create a new Azure AD group, such as the name **Intune MDM Users**). Then, add specific test user accounts and target each of the following configurations at that group to limit who can enroll devices while you set up your configuration. To create an Azure AD group, go to [Create a basic group and add members](/azure/active-directory/fundamentals/active-directory-groups-create-azure-portal).
90+
Before you can join Azure AD and enroll in Intune, there are a few things you need to check. You could create a new Azure AD group, such as the name **Intune MDM Users**. Then, add specific test user accounts and target each of the following configurations at that group to limit who can enroll devices while you set up your configuration. To create an Azure AD group, go to [Create a basic group and add members](/azure/active-directory/fundamentals/active-directory-groups-create-azure-portal).
9191

9292
- **Enrollment restrictions**
9393
Enrollment restrictions allow you to control what types of devices can enroll into management with Intune. For this guide to be successful, make sure *Windows (MDM)* enrollment is allowed, which is the default configuration.
@@ -265,8 +265,8 @@ Before you enable synchronization in the Intune console, you must configure your
265265
- If you don't specifically have **Microsoft Intune** available as a mobile device management tool, choose **Add management tool** to add **Microsoft Intune**.
266266
- If you don't have **Microsoft Intune** activated as your mobile device management tool, select **Activate** next to **Microsoft Intune**.
267267

268-
> **[!NOTE]**
269-
> Pay careful attention to the exact names used - you should activate **Microsoft Intune** rather than **Microsoft Intune Enrollment**.
268+
> [!NOTE]
269+
> Pay careful attention to the exact names used - you should activate **Microsoft Intune** rather than **Microsoft Intune Enrollment**.
270270
271271
### Step 10 - Create and assign some applications
272272

0 commit comments

Comments
 (0)