o365.yaml
file as part of the integration. Its recommended to disable any products you dont want to monitor to avoid usage of additional metrics.username
and password
parameters to the o365.d/o365.yaml
configuration file. username
should be the email address (UPN) of the Office 365 user created in step 1.Add a permission
, Microsoft Graph
, and then Application Permissions
. Add the following permissions:Add a permission
, Office 365 Management APIs
, and then Application Permissions
. Add the following permissions:Add a permission
, Microsoft Graph
, and then Delegated Permissions
. Add the following permissions:Grant Admin Consent for {Organization}
to give consent to the app registration to consume the configured API permissions.Overview
, add the Application (client) ID
and Directory (tenant) ID
values to the o365.d/o365.yaml
file as client_id
and tenant_id
, respectively.Certificates & secrets
and New client secret
. It's recommended to use Never
for expiration unless you are actively managing the secret for your agent installation. Copy the client secret value promptly from the Microsoft Azure UI as the secret will be masked after a short period of time.client_secret
value to the o365.d/o365.yaml
file.dd-agent-synthetic
. The integration specifically looks for a Group/Teams called dd-agent-synthetic
.dd-agent-synthetic
. The synthetic check will use the default General
channel to send and reply to messages.[email protected]
. Optionally set your email forwarding configuration to disable copies of forwarded email.enable_email_synthetics: true
and set the target email address configured in step 5 by adding email_address: {[email protected]}
in the o365.d/o365.yaml
.o365.d/o365.yaml
file to enable collection of SharePoint performance metrics. Ten (10) sites can be added under the configuration section sharepoint_sites
. See the configuration example for syntax. The configured username and password for the performance synthetic user is used for the sharepoint login and the SharePoint site(s) must be readable by the configured user.probe_mode: true
, which will operate with application performance synthetics only. For your primary integration location, change probe_mode: false
in the configuration yaml to enable report metrics and your tenant's Office 365 incident events.office
tag to the integration configuration in o365.d/o365.yaml
file to correspond to each office location from which the integration will be running synthetic checks, e.g.: