Integrations Overview

On this page

The integrations of Alloy Navigator are not all the same kind of thing, and they behave differently: some are part of the product code, some are configuration supplied with the product that you can change, and some are published procedures that you carry out by hand.

Kinds of integration

Kind What it means If you replace your workflow configuration
Built-in product code A compiled part of the product: a component, a service, an endpoint, or a schema object. Unaffected.
Supplied configuration Content of the Default Workflow: workflow actions, scheduled tasks, workflow parameters, or a mobile application record. You can change this content, and an administrator may already have changed it. Lost, unless you import it again.
Instructions only A procedure you carry out by hand, using generic product features together with a third-party product. Nothing ships for it. Nothing to lose, and nothing to find on your system either.

The distinction decides what you can expect to find on a system. A supplied-configuration integration is missing from a database whose workflow configuration was replaced. An instructions-only integration is missing from every database until someone follows its procedure. An upgrade does not necessarily add every supplied integration: a system that was upgraded rather than newly installed may have no configuration record for the Microsoft Teams bot. For version-specific upgrade behavior, see the individual integration articles.

The built-in components and the supplied integrations share one piece of product code: the link between an Alloy Navigator record and its item in a third-party product is kept in one place that both use alike. It holds one link per record and application, with the third-party identifier or data and a time stamp, and a record's links are removed when the record is deleted.

Available integrations

Integration Kind
Microsoft Teams – Self-Service Assistant bot Supplied configuration, plus a vendor-hosted Teams app
Microsoft Teams – incoming webhook Instructions only
Microsoft Teams – Office 365 connector Instructions only, superseded
Zapier Instructions only, plus a Zapier app
TeamViewer Supplied configuration
Microsoft Intune Supplied configuration
Microsoft SCCM/MECM Supplied configuration
Dell Warranty Supplied configuration
Adobe License Management Supplied configuration
Availability monitoring Supplied configuration
NinjaOne Supplied configuration
Microsoft Azure Translator Supplied configuration
Microsoft Azure AD (Entra ID) user import Supplied configuration
Google Analytics Instructions only
Microsoft Word knowledge base import Instructions only, plus a separately downloaded utility
Active Directory import and synchronization Built-in product code
AlloyScan and Alloy Discovery synchronization Built-in product code
Single sign-on (SSO/OIDC) providers Built-in product code
AI providers Built-in product code

NOTE: Microsoft Azure AD (Entra ID) user import is a supplied-configuration integration, built the same way as Microsoft Intune and Microsoft SCCM/MECM. It is a different mechanism from the on-premises Active Directory import described in Active Directory Synchronization.

Active Directory import and synchronization, and AlloyScan and Alloy Discovery synchronization, are built-in product code. In a new 2026.1 database created with the Default Workflow, Workflow Configuration carries an Integrations category for each of them, and one for the Mail Connector, but those settings configure the built-in components. For these components, see Active Directory Synchronization, AlloyScan Synchronization, and Alloy Discovery Synchronization.

How supplied integrations work

This section describes the supplied integrations as they are in a new 2026.1 database created with the Default Workflow; see Default Workflow Configuration. A database that was upgraded need not have this content, and an administrator may have changed it.

The Microsoft Teams bot ships as a single mobile application record. Every other supplied-configuration integration is assembled from the same parts, in some combination: a workflow parameter category under Integrations that holds its settings and credentials; a workflow scheduled task, whose logic is an embedded workflow function, with a matching Scheduled Task Agent job; and, for the interactive integrations, a workflow step action on a ticket class. Nothing about a supplied integration is compiled into the product.

The scheduled tasks of the integrations are disabled, and TeamViewer Status is set to Disabled. Such a database makes no call to a third-party service until an administrator enters credentials and enables a feature.

Network access

The calls to third-party services are made by the integration's own workflow steps. The supplied integrations reach these addresses:

Integration Address
Microsoft Intune, Microsoft Azure AD graph.microsoft.com, login.microsoftonline.com
Dell Warranty apigtwb2c.us.dell.com
Adobe License Management ims-na1.adobelogin.com, usermanagement.adobe.io
NinjaOne app.ninjarmm.com
TeamViewer webapi.teamviewer.com
Microsoft Azure Translator api.cognitive.microsofttranslator.com
Microsoft SCCM/MECM No web address: the integration reads the SCCM/MECM SQL Server database directly.

Two other third-party addresses occur in the supplied workflow content but belong to no integration: api.openai.com, which the AI completion and embeddings calls use unless the AI provider type is Azure (then the configured Azure endpoint is called instead), and translate.google.com, which is opened in the technician's browser and carries no credential.

The supplied integrations are available on-premises and in Alloy Navigator Cloud; whether a Cloud system can reach a server on your own network, such as your SCCM/MECM database, is a question of network connectivity.

Safe Mode and debug switches

Six of the seven integrations that run as scheduled tasks have a Safe Mode parameter; availability monitoring has none. For Microsoft Intune, Microsoft SCCM/MECM, Microsoft Azure AD, Adobe License Management, and NinjaOne, the parameter is described as: the job will run and produce a session log, but no data will be added or modified.

The Safe Mode values are not the same for every integration, and they decide what the first run after you enable the task does:

Integration Kind of value Safe Mode is set to First run after you enable the task
Microsoft Intune A list of two values Safe Mode Off Writes data
Microsoft SCCM/MECM A list of two values Safe Mode Off Writes data
Microsoft Azure AD A list of two values Safe Mode Off Writes data
Adobe License Management On or off On Runs and produces a session log, but adds or modifies no data
NinjaOne On or off On Runs and produces a session log, but adds or modifies no data
Dell Warranty On or off No value Writes data

Microsoft Intune, Microsoft SCCM/MECM, Microsoft Azure AD, and Dell Warranty also have a debug switch. NinjaOne has a Log API Response parameter instead, and Adobe License Management has neither.

Credentials

Credentials for these integrations are workflow parameter values that you enter on the integration's settings page; they are not stored with your accounts or mail profiles. When you save a parameter of the encrypted type in the Settings App, its value is stored encrypted, and the product decrypts it for use. The client IDs and secrets of Microsoft Intune, Microsoft Azure AD, Adobe License Management, and NinjaOne, the Dell API secret, the SCCM/MECM SQL Server password, and the Microsoft Azure Translator key are encrypted parameters. The TeamViewer script token, the Dell API client ID, and the SCCM/MECM SQL Server username are plain-text parameters. Treat an exported workflow file as sensitive: the plain-text values are readable, and the encrypted values can be decrypted by the product.

NinjaOne

NinjaOne is supplied as a scheduled task whose steps call the NinjaOne RMM API. Its parameters are NinjaOne Client ID, Client Secret, Organization Name, Create Organizations, Create Locations, Create Assets, Auto Unrelate Unlisted Users, Log API Response, and Safe Mode.

Microsoft Azure Translator

Microsoft Azure Translator has no scheduled task. Its parameters are Status, Key, Subscription Region, Default Language, Incoming E-mail Translation, and Self-Service Portal Activity Translation. It is used in two ways:

  • On incidents and service requests, the Azure Translate action is shown when Status is set to Enabled.
  • When the two translation parameters are set, the create and update actions of the Mail Connector and the Self Service Portal actions translate the incoming content.

Technician tools in the Integrations action group

Integrations is also the name of an action group of technician tools that run from a record. Among its actions are the TeamViewer and Microsoft Azure Translator actions and these tools:

  • Ping Device, Telnet to Device (Telnet to device on a computer), and Remote Desktop, network tools for the device of the record. Ping Device and Telnet to Device are offered on computers and hardware, and Remote Desktop on computers, when the record has a primary IP address. On incidents, problems, change requests, and work orders they are offered when a related configuration item is set, Remote Desktop only when that item is a computer, and Telnet to Device only when it is hardware.
  • Search Google and Search Microsoft, web searches, on incidents, problems, change requests, and work orders.
  • Windows Password Reset, a password reset, on incidents, service requests, and persons.
  • Google Translate, which opens Google Translate, on incidents and service requests.

Each of these tools logs an activity on the record. In the Web App, they run on the technician's own computer: Search Google, Search Microsoft, and Google Translate open a web page in the browser, and Ping Device, Telnet to Device, Remote Desktop, and Windows Password Reset run a command through the Alloy Integration Launcher. For what happens when the Launcher is missing or outdated, see Operations Reference.

Prepare Active Directory for Windows Password Reset

Windows Password Reset resets the password of a Windows account in Active Directory. It runs on the technician's computer, passes no credentials of its own, and acts with the rights of the Windows account it runs under, so the technicians who run it need the right to reset passwords of those accounts in Active Directory. Delegate that right to a security group on the organizational unit (OU) that holds the user accounts, and add the technicians to the group.

The group needs these permissions, applied to the descendant User objects of the OU:

  • Reset Password, to set a new password without knowing the current one.
  • Read and write pwdLastSet, to make the user change the password at next logon.
  • Read and write lockoutTime, to unlock an account that is locked out.

To delegate the permissions in Active Directory Users and Computers:

  1. Create a security group for the technicians, or choose an existing one. Use a Global group when the technicians' accounts are all in one domain, and a Universal group when they come from more than one domain of the forest.
  2. In Active Directory Users and Computers, on the View menu, select Advanced Features.
  3. Right-click the OU that holds the user accounts, and then select Properties.
  4. On the Security tab, select Advanced.
  5. In the advanced security settings of the OU, add a permission entry for the security group.
  6. In the permission entry, apply the entry to descendant User objects, and allow Reset Password.
  7. For the same descendant User objects, allow reading and writing the pwdLastSet and lockoutTime properties.
  8. Select OK to save the entry, and then close the dialog boxes with OK.

For Microsoft's description of delegated permissions and of how to review them, see Implement delegated privileges. For the choice between Global and Universal groups, see Delegating Administration of Account OUs and Resource OUs.

Where you set up an integration

In a new 2026.1 database created with the Default Workflow, each integration that has settings has its own settings page in Workflow Configuration, named after the integration, for example Integrations > Microsoft Intune. The page shows each parameter with its label and, where the parameter has one, its help text. The Microsoft Teams bot has no such page: its supplied configuration is a mobile application record. In both the Settings App and the Admin Center, Workflow Configuration is under Workflow and Business Logic. For the two tools, see Admin Center and Settings App.

The integration's scheduled task is enabled, run, and its sessions read on the Scheduled Tasks pages of the Settings App and the Admin Center; see Scheduled Tasks.

In the Settings App

  1. Under Workflow and Business Logic, open Workflow Configuration. You need the administrative right to manage Workflow Configuration.
  2. In the category tree, select Integrations, and then the integration. While Integrations is selected, the right pane also lists each integration as an entry that you can click to select it. For the integration, the right pane shows one control per parameter, with its description. If no workflow parameters are defined, the pane shows only "There are no configuration options for your workflow."
  3. Enter the values and save your changes. Only the changed values of the selected category are saved.

Workflow Configuration sets parameter values only. The parameters and their categories are defined in Configuration Parameters under Advanced in the Settings App.

In the Admin Center

  1. Under Workflow and Business Logic, open Workflow Configuration. You need the Workflow Configuration permission.
  2. Select the integration's category. The page shows one control per parameter.
  3. Enter the values, and then click Save. Save and Cancel appear once you change a field. If you leave the page with unsaved changes, the Admin Center asks: "You should save you changes before leaving this page. Do you want to leave this page?"

The Admin Center does not check the values you enter against the parameter's type or declared validation rules.