Microsoft Office 365
The JSA DSM for Microsoft Office 365 collects events from Microsoft Office 365 online services.
The Service Communications API endpoint is no longer available for use because it was deprecated by Microsoft.
The following table describes the specifications for the Microsoft Office 365 DSM:
Specification |
Value |
---|---|
Manufacturer |
Microsoft |
DSM name |
Microsoft Office 365 |
RPM file name |
DSM-Microsoft Office365-JSA_version-build_number.noarch.rpm |
Supported versions |
N/A |
Protocol |
Office 365 REST API |
Event format |
JSON |
Recorded event types |
Exchange Audit, SharePoint Audit, Azure Active Directory Audit |
Automatically discovered? |
No |
Includes identity? |
No |
Includes custom properties? |
No |
More information |
To integrate Microsoft Office 365 with JSA, complete the following steps:
-
If automatic updates are not enabled, download and install the most recent version of the following RPMs from the https://support.juniper.net/support/downloads/ onto your JSA console:
-
Protocol Common RPM
-
Office 365 REST API Protocol RPM
-
Microsoft Office 365 DSM RPM
-
-
Configure a Microsoft Office 365 account in the Microsoft Azure portal.
-
Add a Microsoft Office 365 log source on the JSA console. The following table describes the parameters that require specific values for Microsoft Office 365 event collection:
Table 2: Microsoft Office 365 Log Source Parameters Parameter
Value
Log Source type
Microsoft Office 365
Protocol Configuration
Office 365 REST API
Log Source Identifier
A unique identifier for the log source.
The Log Source Identifier can be any valid value and does not need to reference a specific server. The Log Source Identifier can be the same value as the Log Source Name. If you have configured multiple Microsoft Office 365 log sources, you might want to identify the first log source as MSOffice365-1, the second log source as MSOffice365-2, and the third log source as MSOffice365-3.
Client ID
In your application configuration of Azure Active Directory, this parameter is under Client ID.
Client Secret
In your application configuration of Azure Active Directory, this parameter is under Value.
Tenant ID
Used for Azure AD authentication.
Event Filter
The type of audit events to retrieve from Microsoft Office.
-
Azure Active Directory
-
Exchange
-
SharePoint
-
General
-
DLP
Use Proxy
For JSA to access the Office 365 Management APIs, all traffic for the log source travels through configured proxies.
Configure the Proxy Server, Proxy Port, Proxy Username, and Proxy Password fields.
If the proxy does not require authentication, keep the Proxy Username and Proxy Password fields empty.
EPS Throttle
The maximum number of events per second.
The default is 5000.
Show Advanced Options
Show optional advanced options for event collection. The Advanced Options values are in effect whether they are shown or not.
Management Activity API URL
Specify the Office 365 Management Activity API URL. Default is https://manage.office.com.
Azure AD Sign-in URL
Specify the Azure AD sign-in URL. Default is https://login.microsoftonline.com.
-
Configuring a Microsoft Office 365 Account in Microsoft Azure Active Directory
Before you can add a log source in JSA, you must run the Azure Active Directory PowerShell cmdlet and then configure Azure Active Directory for Microsoft Office 365.
-
Run the Azure Active Directory PowerShell cmdlet. For more information , see How to install and configure Azure PowerShell.
-
Identify the Tenant ID of the tenant that is subscribed to Microsoft Office 365 by typing the following commands:
import-module MSOnline
$userCredential = Get-Credential
Connect-MsolService -Credential $userCredential
Get-MsolAccountSku | % {$_.AccountObjectID}
Use the Tenant ID value for the Tenant ID value when you configure a log source in JSA.
-
To use Azure Active Directory to register an application, log in to the Azure Management Portal with the credentials of the tenant that is subscribed to Microsoft Office 365.
-
From the navigation menu, select Azure Active Directory.
-
From the Overview pane, select App registrations, and then click New registration.
-
In the Supported account types section, select the type of account to use the application or to access the API.
-
In the Redirect URI (optional) section, select Web, and type http://localhost in the Web field
-
Click Register, and then copy and store the Application (client) ID value. Use this value for the Client ID value when you configure a log source in JSA.
-
-
Generate a client secret for the application.
-
From the Manage pane, select Certificates & secrets > New client secret.
-
Select an expiry period, and then click Add.
-
Copy and store your client secret key value because it can't be retrieved later. Use this value for the Client Secret value when you configure a log source in JSA.
-
-
Specify the permissions that the Microsoft Azure application must use to access Microsoft Office 365 Management APIs.
-
From the Manage pane, select API permissions.
-
Click Add a permission > from the API list, choose Office 365 Management APIs > Delegated permissions, and then select the following options:
Table 3: Delegated Permissions Permission
Values
Activity Feed
ActivityFeed.Read
ActivityFeed.ReadDlp
ServiceHealth
ServiceHealth.Read
-
Click Application permissions, and then select the following options:
Table 4: Application Permissions Permission
Values
Activity Feed
ActivityFeed.Read
ActivityFeed.ReadDlp
ServiceHealth
ServiceHealth.Read
-
Click Add permssions.
-
In the API permissions window, go to the Grant consent section, click Grant admin consent > Yes.
-
Sample Event Messages
Use these sample event messages as a way of verifying a successful integration with JSA.
The following table provides sample event messages when using the Office 365 REST API protocol for the Microsoft Office 365 DSM:
Event name |
Low level category |
Sample log message |
---|---|---|
Update user-fail |
Update Activity Failed |
|
Site permissions modified |
Update Activity Succeeded |
|