Skip to main content

Articles in this section

See more
Print

Change History settings

  • Updated

Change History settings

Overview

Use the Change History settings to enable integration with third-party monitoring tools. Define archive database connection settings to automatically archive and clean up Change History details.

NOTE     For more information about Change History retention and archiving, see the following articles: Archive Change History rule and Change History Details from Archive rule.

Settings

Setting name Description
Change auditing
Write change audit events to Application event log Enable event collection, analysis, reporting, and alerting using third-party monitoring tools. Cayosoft Administrator records change details in full. Learn more about recorded events in the following article: List of events posted to Windows Event Log

Archive database connection settings

Instance Specify the SQL Server to store the Change History archive database. Use SERVERNAME, SERVER\INSTANCE_NAME, SERVER,PORT, or IP_ADDRESS.
Credentials

Specify the SQL Server credentials.

IMPORTANT    The specified account must use the SQL Server authentication.
Database

Define the database to Change History data..
Table

Specify the table to store Change History records. The table with the specified name will be created if it doesn't exist.

Change History for rules

Write Change History

Define Change History logging behavior when you use a supported rule:

  • Always. Log changes to objects every time you run the rule.

  • For post-action scenarios only. Log changes to objects every time the rule is used as a post-action rule.

  • Never. Do not log changes to objects made using the rule.

TIP    Some rules log changes to Change History by default; some supported rules log changes based on the in-rule settings. Refer to the list of rules provided in the article.

List of rules logging changes to Change History

The following rules have mandatory change logging enabled:

  • AD Groups | Process Scheduled Suspends (Legacy)

  • AD Groups | Process Scheduled Undo Suspends (Legacy)

  • AD Users | Process Scheduled Suspends (Legacy)

  • AD Users | Process Scheduled Undo Suspends (Legacy)

  • AD Groups Certification Review

  • Suspend | Office 365 User and Guest

  • Undo Suspend | Office 365 User

  • New User | Office 365 User Enforce License

  • Remote Linked Mailboxes | Enforce License

  • AD Users | Teams Direct Routing Assignment (DID Number Assignment)

  • Teams Voice Settings | Direct Routing Assignment

  • Text file | Create Microsoft 365 Contacts

  • Text File | Update Microsoft 365 Contacts

  • Office 365 Groups Certification Review

  • Microsoft Teams Certification Review

  • Cancel Expired Work Items

  • Restricted Groups | Process Memberships Start/End Time

  • Import Workday Data | Create or Update AD Users

The following rules allow you to define the logging behavior based on the global Write Change History setting or the local, rule-based setting:

  • AD Users | Set Attributes Value

  • AD Objects | Set Attribute Value

  • AD Computers | Add to Groups based on DynamicAttributes

  • AD Users | DynamicAttributes Add to AD Groups

  • New User | DynamicAttributes Add to AD Groups

Change history

Version Notes
13.1 The Write Change History setting has been added.
7.2.0 Archive Database Connection settings are added.
6.3.1 Change History settings are introduced as a separate item in the Administrator Console tree.

© 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.