Rule description
This rule queries Microsoft Teams and lists all Teams with their properties. You can customize the report and add a query condition, pick the list of visible columns and define sorting.
When to use this rule
Use this rule to get a list of all the Teams with its settings and ownership. You can use this report to build an inventory of your Microsoft Teams environment, and analyze it for possible optimization and restructuring.
Rule Settings
Query Section
| Setting name | Description |
|---|---|
|
Query criteria |
Query criteria are sent to the target platform with other query parameters to reduce the number of returned objects and may improve query performance. Tip: For different samples on the criteria builder, see KB20180410-1.
|
|
Other Query Settings |
|
|
Properties to display |
To display additional properties for each object found by the query, add those properties to the list. |
|
System properties |
List of properties required for this rule to be executed correctly. |
|
Post-query filter |
To hide unwanted data based on criteria, not supported by the target system in the query criteria, set the filtering conditions here. Example: filter by the found object Distinguished Name. Tip: For optimal performance, use Query criteria above to filter objects whenever possible.
|
|
Sort by |
Sort result object list. |
|
Limit result set |
The maximum number of Teams returned from Office 365. The default value is taken from Maximum returned results setting on HOME > CONFIGURATION > Microsoft Office 365 settings. |
|
MS Graph query condition (OData) |
By default Query criteria is used. But when it is specified, it overrides the Query criteria setting. Example: find all Teams with displayname starting from 'Team.' (startswith(displayName,'Team')) |
|
Initialization script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. Important: To use a variable, declared in initialization script, in the query scope, it must be global: $global:<variable name>.
|
|
MS Graph advanced queries |
Enables consistency level eventual which uses an index that might not be up-to-date with recent changes to the object. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Enforce/Schedule section article.
Change History
| Version | Notes |
|---|---|
| 8.2.0 |
MS Graph advanced queries setting is added. |
| 5.4.2 | The rule was introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.