This section outlines the core requirements and recommendations for Microsoft SQL Server when hosting the Activate database. Meeting these requirements ensures reliable performance, full functionality, and compatibility with Activate components.

Activate uses Microsoft SQL Server to store configuration data, workflows, and historical information. SQL Server can be installed locally on the Activate Server or hosted remotely on shared database infrastructure, provided the connection offers reliable performance.

A supported version of SQL Server must be available—either installed locally or provided as part of a shared SQL Server instance. For test or UAT environments, SQL Server Express is an appropriate and lightweight option.

The SQL server host requires configuration to allow either 

The Activate Administrators Group connection access to the Activate DB 

and\or direct connection rights granted to 

For information on using Azure SQL Database please refer to 

Database Configuration – IDENTITY_CACHE Setting

Activate requires SQL Server 2017 or newer. After creating the Activate database, run the following command to disable identity caching:

ALTER DATABASE SCOPED CONFIGURATION SET IDENTITY_CACHE = OFF

This change prevents gaps in identity values that can occur if the SQL Server service restarts unexpectedly. Continuous identity sequences are required for Activate’s data integrity and internal processes. This setting is mandatory for all Activate installations on SQL Server 2017 or above.

Smaller Organisations may choose to use Microsoft SQL Express – please refer to Microsoft’s knowledge article on the limits of SQL Express. Activate is supported on SQL Express provided the Database size limits are not exceeded.  This is not recommended for organisations with large folder structures or other large data sets.

The Activate Orchestrator and Web Service Accounts (see the Active Directory Requirements section above) must be able to remotely connect to the SQL Server and the Activate Database. These Active Directory accounts must have SQL connection rights to the SQL Server hosting the Activate Database.

The database can be created in two ways: 

:  The database is pre-created on the SQL Server prior to the installer being run.

The Activate Database Collation must match the collation of the TempDB on the SQL Server hosting the Activate DB. 

Activate recommends that the account used to install Activate have explicit DBO rights to the SQL database. 

:  The database is automatically created using default settings during the installation.  The installation account must have SQL rights to create a database on the selected SQL Server.

During the Activate installation, a SQL Database Role will be created for the Activate Database named Activate Administrator and the selected AD Group for Activate Administrators during the installation wizard will be added as a member of this role.

Please ensure the Microsoft SQL Server Management Studio is installed on the Activate Provisioning Server. 

Server Requirements

SQL Server Requirements

Microsoft’s cloud platform providing infrastructure, networking, storage, and application services. In Activate, it’s used as the hosting environment or for integration with Microsoft 365 and Entra ID services.

Azure

DotNetVersion

Microsoft Entra Connect (formerly Azure AD Connect) is a tool that syncs on-premises Active Directory identities with Microsoft Entra ID, enabling hybrid identity and seamless access to cloud resources.

Microsoft_Entra_Connect

Active Directory (AD) is Microsoft’s directory service that stores and manages user accounts, devices, and permissions, enabling secure authentication and centralized access control within a Windows network.

Active_Directory

ActivateJobService

ActivateAdministrator

SupportedPowerShellVersions

SupportedOSVersions

SupportedSQLVersions

Name that identifies the instance of Activate.  This is only used by Administrators and isn't displayed to end users.

instance_name

An installation type of Activate where there is no local domain connection, all authentication, authorisation and identity management is handled by Entra ID.

Cloud_Only

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service, providing secure authentication, user lifecycle management, and access control for Microsoft 365 and other apps.

Microsoft_Entra_ID

A software switch that enables or disables functionality at runtime without redeploying code. In Activate, they are configured under //Resources/Configuration/FeatureFlags.

feature_flag

Microsoft module for managing Exchange Online, using modern authentication and REST API–based cmdlets for faster, more reliable automation of mailboxes, compliance, and organisation settings.

EXO_V3_PowerShell_Module

An Organizational Unit (OU) is a container in Active Directory used to organise users, groups, computers, and other objects within a domain. OUs help structure resources logically and apply group policies for easier management and administration.

A User Type is a template in Activate that defines rules, attributes, and behaviours for a category of users (e.g., Employee, Contractor), ensuring consistent user account setup and configuration.

User_Type

A resource object in Activate representing a physical or virtual Exchange Server

Exchange_Server_Resource

Defines the object type that the resource will emulate or operate as.

Class_parameter

Clonesthe selected inherited parameter to make a local copy to override the value

Override

Runs the Activate Provisioning Server and performs actions across target systems.

Orchestrator_Account

A complete, immutable log of identity-related events, including provisioning actions, access approvals, and policy evaluations.

Audit_Trail

An integration module that enables Activate to read/write data from external systems (e.g., provisioning accounts in Azure AD).

Connector

A periodic process where managers or data owners validate that users still require their existing access — critical for compliance.

Access_Certification_and_Review

A user-initiated process to gain access to new systems or roles, often requiring manager or system owner approval.

Access_Request

Any downstream application or service where identities need access (e.g., Active Directory, Okta, Salesforce).

Target_System

The authoritative system from which identity data is imported (e.g., HRIS like Workday or SAP SuccessFactors).

Identity_Source

An access control model that uses user, resource, or environment attributes (e.g., department = "HR", location = "US") to make access decisions dynamically.

ABAC_Attribute-Based_Access_Control

An access control model where users receive permissions based on assigned roles. This model helps enforce least privilege.

RBAC_Role-Based_Access_Control

A collection of entitlements assigned based on a user’s job function or department. Roles simplify access management and are often tied to policies (e.g., "Finance Analyst Role").

Role

A specific access right or permission within a system (e.g., "Read-only access to Salesforce Reports"). Entitlements can be grouped into roles.

Entitlement

The removal or disabling of user accounts and access when they are no longer required — for example, when an employee leaves the organization.

Deprovisioning

The automated process of creating accounts and granting access to systems or applications based on a user’s role or attributes.

Provisioning

A digital representation of a user (employee, contractor, service account, etc.) within an organization. Each identity is typically linked to a unique identifier, such as an email address or employee ID.

Identity

This is the process of bringing on a new user

Onboarding

Hierarchical Role-Based Provisioning automates user access by assigning roles based on organisational structure, ensuring users inherit the correct permissions and resources aligned to their position or function.

Hierarchical_Role-Based_Provisioning

A group email address that automatically forwards messages to all its members, allowing you to send emails to multiple recipients at once.

Distribution_List

An expression is a conditional statement using Activate expression syntax.

expression

AzureProductName

Exchange Requirements

Activate Knowledge Centre

For Engineers

For Architects

For Service Desk

For C-Suite and Decision Makers

For Partners & Analysts

Welcome to Activate Knowledge Centre

What is Activate?

Key terms

System Overview