Skip to main content

Articles in this section

Print

Import Oracle Data | Update Office 365 Users

  • Updated

Import Oracle Data | Update Office 365 Users

Rule description

This rule queries the specified Oracle data source and updates Microsoft 365 user accounts according to the Action section settings.

When to use this rule

Use this rule when you need to perform bulk user account update from HR/ERP/SIS system into Microsoft 365.

Rule settings

Query section

Setting name Description

Hostname 

Specify Oracle server hostname (or its IP address) to which Cayosoft Administrator will connect.

NOTE: For more information, please read 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 Table or View from the selected database. Click the Selector button to display a list of tables from which to choose.

Credentials

Specify 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 DataSource Filter will be ignored.

Data source anchor attribute

  Select a column in the data source that contains the attribute value for identifying and mapping a computer.

Office 365 anchor attribute

UserPrincipalName must be used as a DataSource Anchor attribute. 

NOTE: Microsoft best practices assume the Active Directory and Microsoft 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 Oracle Server.

Filter Oracle data

 

Set the filtering conditions to hide unwanted data based on criteria not supported in the Query criteria setting.

Example: filter by the found object Distinguished Name.

TIP: For optimal performance, use the Query criteria setting above to filter objects whenever possible.

Filter Office 365 users

To hide unwanted data set the filtering conditions here.

Properties to display

Each object property defined in this setting matches the column that will be displayed in the Web Portal for this web query.

To display additional columns, add the required properties to the Properties to display list.

To add extension attribute 1 that is synchronized from AD, you need to use a value like:

Copy
"OnPremisesExtensionAttributes/extensionAttribute1~Extension Attribute 1"
Empty field in data source If the record in the Oracle column is empty, you can skip updating the attribute or clear its value.

Action section

Setting name Description
Account

First name (FirstName)

If the Data Source contains a field named FirstName, ignore this setting. Otherwise, use the Selector button to choose a field from the Data Source or just skip this setting.

Last name (LastName)

If the Data Source contains a field named LastName, ignore this setting. Otherwise, use the Selector button to choose a field from the Data Source or just skip this setting.

Display name

 

Specify DislpayName format.

Settings

Password

Specify the password for the updated Microsoft 365 user account. This value can be static text or a field from the Data Source chosen using the Selection button or just skip this setting.

Usage location

Specify the usage location for the updated Microsoft 365 user account or just skip this setting.

Must change password at next logon

 

Specify if a user must change password at next logon or just skip this setting.

Account status

Specify if an updated user account will be enabled or disabled or just skip this setting. 

Organization

  • Job title (Title)

  • Department

  • Office

If the Data Source contains one of these field names, ignore this setting. Otherwise, manually enter a static text value or use the Selector button to choose a field from the Data Source or just skip this setting.

Contact Info

  • Alternate email

  • Office phone (telephoneNumber)

  • Mobile phone (mobile)

  • Fax

  • Street address

  • City

  • State

  • Country

  • Postal code

If the Data Source contains a field with one of these names, ignore this setting. Otherwise manually enter a static text value or use the Selector button to choose a field from the Data Source or just skip this setting.

 

Virtual and other attributes

Virtual attributes

 Map column names from the data source to the virtual attributes.

Attribute mapping script

Set up attribute mapping using scripts. Refer to the following examples:

  • If you want every provisioned user to have a virtual attribute populated with some string value, use the following line:

    {@{'csvaAttribute1'='YourString'}}

    The csvaAttribute1 value is a name of a virtual attribute in Configuration > Virtual Attributes in the Cayosoft Administrator Console.

  • If you want every provisioned user to have a virtual attribute populated with the corresponding value from the column in your data source, use the following line

    {@{'csvaAttribute1'=$_.VAName}}

    The VAName value is the name of the column from the data source.

Example 1:

{@{'csvaAttribute1'='YourString1';'csvaAttribute2'='YourString2'}}

Example 2 using regular attributes:

{@{'MailNickName'=$_.MailNickName;'EmployeeType'=$_.EmployeeType}

Output section

This section defines the output format of this rule.

To get more information about this section, please see the Rule 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 Rule Enforce/Schedule section article.

© Copyright 2013-2026 Cayosoft Inc. All rights reserved.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top

Related articles

Comments

0 comments

Please sign in to leave a comment.