Use the new Import SQL Data | Suspend Office 365 Users rule instead.
Rule description
This rule queries the specified Microsoft SQL data source and suspends Office 365 user accounts according to the Office 365 user account suspend settings.
When to use this rule
Use this rule when you need to suspend Microsoft Office 365 user accounts based on the data in the external data source, for example, the HR system.
Remember to configure the Office 365 user account suspend settings in the Suspend | Office 365 User rule.
Rule Settings
Query Section
| Setting name | Description |
|---|---|
|
SQL Instance
|
Specify the name of the SQL Instance as defined in the Utils Extension SQL Server configuration. Using the Default SQL Instance setting will retrieve the current setting from the SQL Connection settings of the Utils extension.
Note: For more information, please see Connecting to Microsoft SQL Server data source article.
|
|
SQL Database Name |
Specify database name from selected SQL Instance. |
|
SQL Table |
Specify SQL Table or View from the selected database. Click the [...] button to display a list of tables from which to choose. |
|
SQL Credentials |
Specify the database from the data source SQL Instance. Click the [...] button to enter SQL Credentials.
Note: Cayosoft Administrator does not support Windows Authentication for connecting to a Microsoft SQL Server database. The database connection must use SQL Server Authentication, where the credentials (username and password) are created and managed within SQL Server itself. Mixed Mode refers to the SQL Server configuration that allows both SQL Server Authentication and Windows Authentication, but only SQL Server Authentication is supported by Cayosoft.
|
|
Data Source Filter |
You can use the point-and-click filter builder for the specified data source. Note: If Where Clause is also specified, it will be applied and 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 SQL 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. Example: filter by Name column.
|
|
Filter Office 365 users |
To hide unwanted data set the filtering conditions here. |
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 |
|---|---|
| 7.3.0 | Data Source filter is added. |
| 6.3.1 | The rule is introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.