Redirect URL
This parameter is deprecated and is never used! Therefore it can be ignored.
Technical Name |
redirect_url |
Category |
Functional |
Type |
String |
Default Value |
n/a |
Example Values |
Fetch Sign-ins
This parameter is deprectated! This parameter is used to activate or deactivate the collection of sign-ins.
Technical Name |
fetch_sign_ins |
Category |
Functional |
Type |
Boolean |
Default Value |
false |
Example Values |
false |
Sign-ins Since
This parameter is deprectated! This parameter is used to define a date. All sign-ins since the defined date will than be collected. This parameter uses the ISO 8601 format.
Technical Name |
sign_ins_since |
Category |
Functional |
Type |
String |
Default Value |
PT24h |
Example Values |
PT24h |
Since the sign-ins can take a long time, fetching less sign-ins can considerable speed up the overall execution time.
Sign-ins Request Interval
This parameter is deprectated! This parameter is used to define the duration of the interval per request. This parameter uses the ISO 8601 format.
Technical Name |
sign_ins_request_interval |
Category |
Functional |
Type |
String |
Default Value |
PT1h |
Example Values |
PT1h |
to speed up download of the sign-ins, the requests are parallelized. For example: If Sign-ins Since is 'PT10h', and Sign-ins Request Interval is 'PT2h', then there will be five parallel requests. A shorter interval always means more parallel requests, which means the complete time will be reduced, unless the high parallelization leads to the API's refusal to answer the requests. Thus, the optimal value for this parameter is unknown.
Fetch Conferencing Data (PSTN)
This parameter is used to activate or deactivate the collection of conferencing data.
Technical Name |
fetch_pstn |
Category |
Functional |
Allowed Types |
Boolean |
Default Value |
false |
Example Values |
false |
Fetching conferencing data can take a long time.
Conferencing Data Since
This parameter is used to define a date. All conferencing data since the defined date will than be collected. This parameter uses the ISO 8601 format.
Technical Name |
pstn_since |
Category |
Function |
Allowed Types |
String |
Default Value |
PT24h |
Example Values |
PT24h |
|
Be aware: Reducing this value can considerably speed up the total execution time of the collector. |
Conferencing Data Request Interval
This parameter defines the duration of the interval per request using the ISO 8601 format.
Technical Name |
pstn_request_interval |
Category |
Functional |
Type |
String |
Default Value |
PT1h |
Example Values |
PT1h |
In order to speed up the download of the conferencing data, the requests are parallelized.
Example: If Conference Data since is set to PT12h and Conferencing Data Request Interval is set to PT3h, there will be 4 parallel requests. A shorter interval always means more parallel requests and will therefore lead to a reduced overall time unless the API refuses to answer the request due to the high parallelization. The optimized value for this parameter is unknown.
Fetch App Usage
This parameter is used to activate or deactivate the collection of app usage data.
Technical Name |
fetch_app_usage |
Category |
Functional |
Type |
Boolean |
Default Value |
false |
Example Values |
false |
Fetch Exchange, OneDrive and Sharepoint Usage
This parameter is used to activate or deactivate the fetching of OneDrive usage data.
Technical Name |
fetch_one_drive_usage |
Category |
Functional |
Type |
Boolean |
Default Value |
false |
Example Values |
false |
Fetching OneDrive usage data can take a long time.
Exchange, OneDrive and Sharepoint Usage Since
This parameter is used to define the timeframe for which to fetch OneDrive usage data.
Technical Name |
one_drive_usage_since |
Category |
Functional |
Type |
String |
Default Value |
P30D |
Example Values |
P30D, P7D, P90D, P180D |
Reducing this duration can considerably speed up the total execution time of the connector. The duration should be one of four presented as examples which are represented in the 'PnD' ISO: https://docs.microsoft.com/en-us/graph/api/reportroot-getonedriveusageaccountdetail?view=graph-rest-beta.
Additional User Fields
The API allows custom fields for users. Set the additional fields here. They are then written to a separate file.
Technical Name |
additional_user_fields |
Category |
Functional |
Type |
Array |
Default Value |
{empty} |
Example Values |
extension_123456789abcd_shoesize, accountEnabled |