• In the Admin Console, go to Applications
• Click the Add button next to it to begin configuration.

Setup Application

1. Select Data Ingestion method as Connector
2. Enter application Name
3. Enter the Application Owner email information
4. Search Connector in Featured Integrations and select Office 365
5. Agent is software that needs to be installed on your on premise environment to pull data from applications such as Active Directory, Databases and Custom Applications which are not cloud based.
   1. Select Remote if you already have the Agent Software installed.
      1. The server where the agent is currently installed needs to have connectivity to the on-premises application or database.
      2. If a new agent is required, contact your implementation consultant or submit a ticket via the SecurEnds Help Desk using the Report Issue link in the upper right corner of the SecurEnds application.  SecurEnds will need to provide files and instructions.
   2. Select Local if the application is cloud based. No agent install is required.
      1. You will need to whitelist the SecurEnds IP’s.  Your Implementation Consultant can provide these.
6. Select Match By logic as Default(Email or FirstName and LastName) or Employee Id
   • If we select Default(Email or FirstName and LastName) the system will match the user with Email or First Name and Last Name while syncing
   • If we select Employee Id the system will only match the Employee ID while syncing
7. Select Include Inactive Users to fetch all users while sync
   • If we select Yes all the Active status users along with Disabled status users will be added in the Matched users for Active Directory.
   • If we select No then only Active user will be added to the Matched users for Active Directory.
8. Include Entitlements Enabled as Yes to load the entitlements on application while syncing.

Configure Application

1. Provide the Office365 Tenent ID acquired from Configuration Details in Step 1.
2. Provide the Office365 Client Secret generated from Configuration Details in Step1
3. Provide the Office365 Client ID acquired from Configuration Details in Step 1

Ticketing System Configuration

For more information on Ticketing System Configuration, Click here.

Click Save once finished to add the connector

The post Set Up Office 365 appeared first on SecurEnds.

You will only need to follow the below steps if you don’t have Azure Active Directory set up.

If Azure Active Directory is already set up in your Azure Portal and/or configured as a connector in SecurEnds, you can use the Application (Client) ID, Tenant (Directory) ID, and Client Secret (Secret Value) from Azure Active Directory to setup your Office 365 connector.

Step 1: Application Registration

Get started with Office 365 Management APIs | Microsoft Docs

1. Sign into the Azure portal using your Azure account
   • https://portal.azure.com/
2. Office 365 is not at the Azure Portal. It is one level below, registered as an App under Azure AD
3. Select Azure Active Directory > App registration > New registration
4. Provide a Name for the application
5. Select the appropriate “Supported account types”
6. Under Redirect URL, select “Web” as the application type, and (optionally) specify a redirect URL if your application requires it
7. After setting the values, select Register. The application registration is created, and the Overview page is presented
8. Copy the Application ID for use in your application code. This value is also referred to as the Client ID and will be used in the configuration settings within
9. Copy the Tenant ID for use in your application code.
10. To generate a client secret/Key, select the Certificates & secrets page then select New client secret
11. Provide a description for the secret, and an expires duration.
12.  The Client Secret/key will be displayed when these settings are saved and compulsory, copy the key to the clipboard, once you leave the page the key will not be visible.
13. When done, select Add

Step 2: Azure Permissions

After registering SecurEnds as an application within the Azure portal, the next step is to make sure the application has the correct API permissions to access data within Microsoft Graph. To do this the user or administrator must grant the correct permissions via a consent process.

1. From the Home screen select App registration > Created App (under owned Applications) > API Permissions > Add Permissions
2. Under Microsoft Graph give the following Delegated and Application permissions. Totaling 7 permissions in all.
   • Delegated permissions:
     • User.Read
     • User.Read.All
     • User.ReadBasic.All
     • Directory.AccessAsUser.All
     • Directory.Read.All
   • Application permissions:
     • User.Read.All
     • Directory.Read.All

• Once added, click to grant admin consent for the permissions. Once complete, each permission will have a green checkmark as shown below

The post Configuration Details appeared first on SecurEnds.