Azure Environment Profile
This parameter defines the selected Azure Environment profile.
Technical Name |
azure_environment |
Category |
Functional |
Type |
String |
Default Value |
"AZURE" |
Example Values |
"AZURE", "AZURE_US_GOVERNMENT", "AZURE_GERMANY", "AZURE_CHINA" |
The Azure Cloud profile sets the cloud environment on which to execute all the queries (i.e. authentication and management endpoints etc.).
Available profiles are: "AZURE", "AZURE_US_GOVERNMENT", "AZURE_GERMANY","AZURE_CHINA".
Profiles can be also set as lower case or first letter capitalized (`azure`, `Azure_Germany`).
More information about Azure Cloud profiles can be found here.
Subscription IDs
This parameter specifies the subscriptions from which data will be fetched. When set to null, the data for all subscriptions of the tenant will be fetched.
Technical Name |
subscription_ids |
Category |
Functional |
Type |
Array null |
Default Value |
null |
Example Values |
null |
Skip steps that cause errors
When set to true, the connector continues to execute even after encountering an error while fetching data. If an error occurs, the subscription id, the workspace id, and additional information will be logged. It is advisable to always check the log for warnings and error messages to identify potential issues that may lead to incomplete data (e.g., lack of permissions).
Technical Name |
skip_on_error |
Category |
Functional |
Type |
Boolean |
Default Value |
false |
Example Values |
false |
Fetch Usage Details Period
This parameter defines the period for which the usage details will be fetched. When left empty, the current month is fetched. If this field is set to null, it will override the default value. The interval has to conform to the ISO-8601 standard. Repeating intervals are not supported.
Technical Name |
time_interval |
Category |
Functional |
Type |
String null |
Default Value |
null |
Example Values |
null, 2020-10-01T14:15Z/2020-11-20T16:00Z, 2020-10-01T14:15Z/P2DT5H45M, P1DT1H45M/2020-11-01T14:15Z, PT21H45M |
|
Note: During testing, the API turned out to be unstable for large data sets. If there are a lot of "504 Gateway Timeout" and "500 Internal Server Error", consider reducing the time interval. By default the API returns the full current month. A time interval of a few days (e.g. 'PSD') seemdd to work pretty well during testing. |
The interval has to conform to the ISO-8601 standard. Repeating intervals are not supported.
•Example 1: For setting an interval with 'start date' and the 'end date' we use '2020-10-01T14:15Z/2020-11-20T16:00Z'.
•Example 2: For setting an interval with 'start date' and 'duration' we use '2020-10-01T14:15Z/P2DT5H45M'.
•Example 3: For setting an interval with 'duration' and the 'end date' we use 'P1DT1H45M/2020-11-01T14:15Z'.
•Example 4: For setting an interval with only 'duration' which will go in past from instance of now we use 'PT21H45M'.