Microsoft 365 connector
The Microsoft 365 connector gathers data about users from Office 365.
In order to connect MIcrosoft 365 to Ivanti Cloud, you must create an application in Azure Active Directory first. The app must have permissions to read report information (Reports.Read.All). For information on creating the application, see the article in the Community:
- User's display name
- Email address
- Licensing status, license assignment date, and last activity date for Exchange, OneDrive, SharePoint, Skype for Business, Yammer, and Teams
- Account deleted state and date of deletion
- Products assigned to the user
- The count of devices on which the user has activated Office 365
A Microsoft 365 connector has the following options:
- Connector name: A name for the connector.
- Connector server name: The name of the connector server that this connector is associated with. Each connector can only be associated with one connector server. If you added the connector to a specific connector server, this field may be populated for you. Otherwise, you can select the connector server from the list.
- Directory (tenant) ID: The ID of the tenant you created in Azure.
- Application (client) ID: The ID of the application you created in Azure.
- Date filter: To limit the amount of data that is gathered for Ivanti Cloud, set a threshold for a specific number of days. The connector will not include records unless the user has checked in or otherwise changed during that time.
- Client secret: The client secret associated with the application you created in Azure.
- Repeats: How often the connector should gather data.
- Start time: The time of day the connector should start running. To minimize the impact on your network and applications, we recommend that connectors generally run at night or on weekends.
- Active: Whether the connector is active or not. While the connector is active, it runs according to the schedule you create. If you clear the check box, the connector is inactive and will not gather data until the check box is enabled again and the connector is saved.
For details on configuring or using connectors, see Setting up connectors.