Integrating Microsoft Defender with requires the following Microsoft Entra ID information:
-
Tenant ID (the existing Directory ID for the Entra customer).
-
Application ID (a configured application Client ID for the Entra customer).
-
Client Secret (a configured authentication for content sharing between OneSite Patch and Entra).
To integrate Microsoft Defender with , begin with registering an application with Microsoft Entra ID and creating a service principle.
-
Sign in to your entra.microsoft.com account as an administrator.
-
Browse to
, and then select . -
Enter the following details into the form:
-
Enter a Name that identifies the Adaptiva integration.
-
Select Accounts in this organization directory only under .
-
Skip both Redirect URI and Service Tree ID. If you must enter something for the Redirect URI, select .
-
-
Select
to create the application.
After creating the new Entra application, use the following steps to add the Vulnerability.Read.All
permission from Add registrations. Make sure you are logged in as an administrator.
-
Access the API Permissions workspace from the App registrations page:
-
Select the Name of the newly created application on the App registrations page. This opens the application and a new list of menu options.
-
Select Add a Permission.
on the left navigation menu, and then clickThis opens the Request API Permissions workspace.
-
-
Select APIs my organization uses, and then locate WindowsDefenderATP in the list.
-
Select Application permissions.
, and then select -
Scroll down to and expand Vulnerability Read All.
, and then select -
Select
. If prompted, follow the required steps to provide administrator consent to make the change. -
Create a Client Secret ID for the application.
After creating an application and adding permissions, use the following steps to create a shared secret ID. The secret ID enables authentication between OneSite Patch and Windows Defender for the application you created.
-
Select Manage menu for the open application.
on the -
Select Client secrets.
-
Select + New client secret. This opens the Add a client secret dialog:
-
Enter a Description of the secret.
-
Select an Expires timeline.
-
Select Add to save your changes and return to the Certificates & secrets workspace.
-
-
Copy and save the Value and Secret ID information.
Important
The system does not save this information when you leave this window. Be sure to record these numbers and save them to an accessible location for later use.
-
Gather the integration details you have created.
-
Sign in to your entra.microsoft.com account as an administrator.
-
From the Home page, navigate to Applications > App Registrations, and then open the application you created for integration.
-
Select Overview on the left navigation of the application workspace, and then expand the Essentials section.
-
Record the following identification information:
-
Client ID
-
Tenant ID (Directory (tenant) ID)
-
Secret ID
-
-
Complete the integration with Adaptiva OneSite Patch.
-
Select Windows Defender Endpoint on the left navigation menu of the OneSite Patch dashboard.
This opens the Defender Access Settings workspace.
-
Enter the ID information gathered from Microsoft Entra, and then click Save on the upper left.
View, create, or modify Administrators and Roles. Changes made here effect all licensed OneSite products.
After integrating Defender with OneSite Patch, you can view your list of Microsoft Defender users and assigned roles for your integrated hosts. To make any changes to Administrators or Roles, you must use the Microsoft Defender product.
-
Select
on the upper right of the OneSite Admin Portal dashboard.
-
Select Settings > Security > Administrator to open the Settings page with the Administrators tab selected. To open to a different tab, select a different item from the final menu.
-
Select Show All to view existing administrators.
-
Select an Administrators folder from the Administrators tab of Security Settings.
-
Select Show All to list all Administrators in the selected folder.
To make any changes to Administrators, you must use the Defender product.
-
Select an Administrators folder from the Administrators tab of Security Settings, and then select + NEW to open the new administrator template.
-
Enter the Administrator Details:
-
Select the Admin Type login from the list. Adaptiva recommends Windows Active Directory.
-
Enter the email address and login details for the new administrator.
-
-
Enter the User Details:
-
Add the Name and contact details for the new administrator.
-
Choose country codes from the drop-down lists for phone numbers.
-
-
Assign Direct Roles:
-
Select + Manage Roles.
-
Select one or more roles for the new administrator:
-
High level roles include All Admin Role, Read-only Admin Role, and Super Admin Role.
-
Patch Express roles include Patch Express Administrator.
-
To create additional roles, you must use the Defender product.
-
-
Select Manage Roles on the bottom-left corner of the dialog to return to the .
-
-
Select Save at the top left to save the new administrator.
-
Select a Roles folder from the Roles tab of Access Security Settings.
-
Select Show All to list all Roles in the selected folder.
To make any changes to Roles, you must use the Microsoft Defender product.
-
Select a Roles folder from the Roles tab of Security Settings, and then select + NEW to open a new Role template.
-
Enter a Role Name and a detailed Role Description in the Role Properties workspace.
-
Add one or more Direct Administrators in the Role Membership section:
-
Select Add Administrators to open the Add Administrators dialog.
-
Select one or more administrators from the table for the new role.
-
Select Add Administrators to return to the Role template.
-
-
Add an existing AD Group (Active Directory):
-
Select Add AD Group to open the Active Directory Group dialog.
-
Enter the the Domain Name and Group Name, and then select Check Group to locate. If it exists, the group name appears in the data table.
-
Select Add AD Group to return to the Role template.
-
-
Select Save at the top left to save the new role:
Comments
0 comments
Article is closed for comments.