You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-endpoint/api/api-hello-world.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.topic: reference
16
16
ms.subservice: reference
17
17
ms.custom: api
18
18
search.appverid: met150
19
-
ms.date: 06/24/2024
19
+
ms.date: 08/29/2024
20
20
---
21
21
22
22
# Microsoft Defender for Endpoint API - Hello World
@@ -47,7 +47,7 @@ It only takes 5 minutes done in two steps:
47
47
48
48
### Do I need a permission to connect?
49
49
50
-
For the Application registration stage, you must have the **Global administrator**role assigned in your Microsoft Entra tenant.
50
+
For the Application registration stage, you must have an appropriate role assigned in your Microsoft Entra tenant. For more details about roles, see [Permission options](../user-roles.md#permission-options).
Copy file name to clipboardExpand all lines: defender-endpoint/api/exposed-apis-create-app-partners.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.service: defender-endpoint
6
6
ms.author: siosulli
7
7
author: siosulli
8
8
ms.localizationpriority: medium
9
-
ms.date: 06/28/2024
9
+
ms.date: 08/29/2024
10
10
manager: deniseb
11
11
audience: ITPro
12
12
ms.collection:
@@ -61,7 +61,7 @@ The following steps guide you how to create a Microsoft Entra application, get a
61
61
62
62
## Create the multitenant app
63
63
64
-
1. Sign in to your [Azure tenant](https://portal.azure.com) with user that has **Global Administrator** role.
64
+
1. Sign in to your [Azure tenant](https://portal.azure.com).
65
65
66
66
2. Navigate to **Microsoft Entra ID**\>**App registrations**\>**New registration**.
67
67
@@ -122,17 +122,17 @@ In the following example we use **Read all alerts** permission:
122
122
123
123
You need your application to be approved in each customer tenant where you intend to use it. This approval is necessary because your application interacts with Microsoft Defender for Endpoint application on behalf of your customer.
124
124
125
-
A user with **Global Administrator** from your customer's tenant need to select the consent link and approve your application.
125
+
A user account with appropriate permissions for your customer's tenant must select the consent link and approve your application.
Copy file name to clipboardExpand all lines: defender-endpoint/api/offboard-machine-api.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.topic: reference
15
15
ms.subservice: reference
16
16
ms.custom: api
17
17
search.appverid: met150
18
-
ms.date: 06/28/2024
18
+
ms.date: 08/29/2024
19
19
---
20
20
21
21
# Offboard machine API
@@ -60,13 +60,13 @@ One of the following permissions is required to call this API. To learn more, in
60
60
> [!IMPORTANT]
61
61
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
62
62
63
-
> [!NOTE]
64
-
> When obtaining a token using user credentials:
65
-
>
66
-
> - The user must have a Global Administrator role.
67
-
> - The user must have access to the device, based on device group settings. For more information, see [Create and manage device groups](../machine-groups.md).
68
-
>
69
-
> Device group creation is supported in Defender for Endpoint Plan 1 and Plan 2.
63
+
When obtaining a token using user credentials:
64
+
65
+
- The user must have an appropriate role assigned (see [Permission options](../user-roles.md#permission-options)).
66
+
67
+
- The user must have access to the device, based on device group settings. For more information, see [Create and manage device groups](../machine-groups.md).
68
+
69
+
Device group creation is supported in Defender for Endpoint Plan 1 and Plan 2.
Copy file name to clipboardExpand all lines: defender-endpoint/configure-conditional-access.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,28 +31,26 @@ This section guides you through all the steps you need to take to properly imple
31
31
## Before you begin
32
32
33
33
> [!WARNING]
34
-
> It's important to note that Microsoft Entra registered devices aren't supported in this scenario.</br>
35
-
> Only Intune enrolled devices are supported.
34
+
> It's important to note that Microsoft Entra registered devices aren't supported in this scenario. Only Intune enrolled devices are supported.
36
35
37
36
You need to make sure that all your devices are enrolled in Intune. You can use any of the following options to enroll devices in Intune:
38
37
39
38
- IT Admin: For more information on how to enable auto-enrollment, see [Windows Enrollment](/intune/windows-enroll#enable-windows-10-automatic-enrollment)
40
-
- End-user: For more information on how to enroll your Windows 10 and Windows 11 device in Intune, see [Enroll your Windows 10 device in Intune](/intune/quickstart-enroll-windows-device)
39
+
- Enduser: For more information on how to enroll your Windows 10 and Windows 11 device in Intune, see [Enroll your Windows 10 device in Intune](/intune/quickstart-enroll-windows-device)
41
40
- End-user alternative: For more information on joining a Microsoft Entra domain, see [How to: Plan your Microsoft Entra join implementation](/azure/active-directory/devices/azureadjoin-plan).
42
41
43
42
There are steps you'll need to take in the Microsoft Defender portal, the Intune portal, and Microsoft Entra admin center.
44
43
45
44
It's important to note the required roles to access these portals and implement Conditional access:
46
45
47
-
-**Microsoft Defender portal** - You'll need to sign into the portal with a Global Administrator role to turn on the integration.
46
+
-**Microsoft Defender portal** - You'll need to sign into the portal with an appropriate role to turn on integration. See [Permission options](user-roles.md#permission-options).
48
47
-**Intune** - You'll need to sign in to the portal with Security Administrator rights with management permissions.
49
-
-**Microsoft Entra admin center** - You'll need to sign in as a Global Administrator, Security Administrator, or Conditional Access administrator.
48
+
-**Microsoft Entra admin center** - You'll need to sign in as a Security Administrator or Conditional Access administrator.
50
49
51
50
> [!IMPORTANT]
52
51
> Microsoft recommends that you use roles with the fewest permissions. This helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role.
53
52
54
-
> [!NOTE]
55
-
> You'll need a Microsoft Intune environment, with Intune managed and Microsoft Entra joined Windows 10 and Windows 11 devices.
53
+
You'll need a Microsoft Intune environment, with Intune managed and Microsoft Entra joined Windows 10 and Windows 11 devices.
56
54
57
55
Take the following steps to enable Conditional Access:
0 commit comments