Rule description
This rule queries the specified Oracle data source and suspends Microsoft 365 user accounts according to the Microsoft 365 user account suspend configuration.
When to use this rule
Use this rule when you need to suspend Microsoft 365 user accounts based on the data in the external data source, for example, the HR system.
Rule Settings
Query Section
Setting name | Description |
---|---|
Hostname |
Specify the Oracle server hostname (or its IP address) to which the Cayosoft Administrator will connect.
Note: for more information, please read the Connecting to Oracle Database article.
|
Service Name |
Specify the Oracle database service name. |
Port |
Specify Oracle SQL*Net Listener port number; the default is 1521. |
Table |
Specify a Table or View from the selected database. Click the Selector button to display a list of tables from which to choose. |
Credentials |
Specify the Oracle user account name and password. |
Data Source Filter |
You can use the point-and-click filter builder for the specified data source. Note: If the Where Clause is also specified, it will be applied and the DataSource Filter will be ignored.
|
Data Source Anchor attribute |
UserPrincipalName must be used as a DataSource Anchor attribute. It must be a unique value. |
Office 365 Anchor attribute |
UserPrincipalName must be used as a DataSource Anchor attribute. Note: Microsoft best practices assume the Active Directory and Office 365/Azure AD UPNs will match. |
More options | |
Return These SQL Columns
|
Specify columns returned by the data source. |
Where Clause |
Define a WHERE statement in the SQL query sent to the data source to limit the rows returned by the Oracle Server. |
Properties to display |
Select properties to display for each object found by the query. |
Filter SQL Data
|
Set the filtering conditions to only return objects or data that need to be processed by the rule. |
Filter Office 365 users |
To hide unwanted data set the filtering conditions here. |
Initialization script |
|
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 the 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 the initialization script, in the query scope, it must be global: $global:<variable name>.
Example: Update AD users, created in the last ten days.
{$global:DatePeriod = (Get-Date).AddDays(-10)}
|
Action Section
Setting name | Description |
---|---|
Microsoft 365 Suspend configuration |
Specify the existing Microsoft 365 Suspend configuration that should be applied during the Microsoft 365 user suspend. It is possible to use the default Microsoft 365 User Suspend configuration or create a custom Suspend configuration. |
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 |
---|---|
10.3.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.