Product · Platforms · Azure
Azure Job Scheduling for Hybrid Cloud Environments
JAMS Scheduler runs in your own Azure subscription and keeps scheduling jobs on-premises while you migrate. Run Azure Data Factory pipelines and Blob Storage jobs, and pull credentials from Azure Key Vault, from the same console as the rest of your batch work.
Move to Azure Without Re-Platforming Your Job Scheduler
JAMS Scheduler is an Azure job scheduler and an on-premises job scheduler at the same time. It runs on a Windows Server VM in Azure the same way it runs on Windows Server in your data center, and JAMS Agents can sit in either place, so you can run hybrid for as long as the migration takes.
A cloud migration rarely happens in one weekend. For months, some servers are in the data center and some are in Azure, and the nightly batch still has to run in the right order across both. With agents in both places reporting to one scheduler, that batch keeps its dependencies no matter which side of the move a server is on.
JAMS Scheduler Architecture in Azure
A JAMS Scheduler deployment in Azure has five components: the scheduler, the database, agents, the Web Client, and the Desktop Client. The scheduler, database, and Web Client can each run on their own VM or be consolidated onto one. Agents go wherever the work runs, and the Desktop Client runs on a workstation or VDI.
Your Azure subscription
JAMS Scheduler
Windows Server VM, 3 services
Database
Azure SQL Database, Azure SQL Managed Instance, or SQL Server on a VM
JAMS Web Client
Windows Server VM
JAMS Agents
Azure VMs
Azure services JAMS Scheduler works with
Azure Data Factory
Azure Blob Storage
Azure Key Vault
Network link
On-premises data center
JAMS Agents: Windows, Linux, IBM i
Other clouds
JAMS Agents
Users
JAMS Desktop Client
Windows workstation or VDI
JAMS Web Client
Any browser
Where Each JAMS Scheduler Component Runs
Use this table with the diagram above to plan VMs, the database, and network access for each part of the deployment.
| Component | Where it runs in Azure | Notes |
|---|---|---|
| JAMS Scheduler | Windows Server VM | Three services make up the scheduling engine |
| Database | Azure SQL Database, Azure SQL Managed Instance, or SQL Server on a VM | See the Azure SQL setup guide |
| JAMS Agents | Any server that runs work: Azure VMs, on-premises, or other clouds | Needs network connectivity to the scheduler |
| JAMS Web Client | Windows Server VM | Browser access for remote users, no workstation install |
| JAMS Desktop Client | Windows workstation or VDI | Performance depends mostly on the connection to the scheduler, so plan for VPN access |
Azure Services JAMS Scheduler Works With
JAMS Scheduler has native job types for Azure Data Factory and Azure Blob Storage, uses Azure Key Vault for credentials, and runs its database on Azure SQL.
Azure Data Factory
Run and monitor Azure Data Factory pipelines as JAMS jobs, with dependencies on the on-premises jobs that feed them or wait on them. Native execution method since V7.8.1 (October 2025).
Azure Blob Storage
Upload, download, and delete blobs from a job step, with connection details stored once in the Connection Store. Added in V7.8.3 (February 2026).
Azure Key Vault
Use Azure Key Vault as a secret provider for JAMS Credentials, so passwords and keys stay in the vault your security team already manages. Added in V7.9.0 (July 2026).
Azure SQL
Host the JAMS database on Azure SQL Database or Azure SQL Managed Instance, at install or by moving an existing database later. The installer detects Azure SQL Managed Instance as of V7.8.3 (February 2026).
JAMS Scheduler also sends job notifications through the Microsoft Graph API, runs PowerShell jobs, and exposes a REST API for scripts and integrations. See every Azure release in the release notes.
Cross-Platform Job Scheduling Beyond Azure
JAMS Scheduler schedules jobs across Azure and the platforms and applications that stay outside it, from one console. The same scheduler that runs your Azure Data Factory pipelines runs jobs on Linux, Unix, IBM i, and z/OS systems and in applications like SAP and Oracle E-Business Suite, with dependencies that cross all of them.
A nightly run can pull data from an on-premises SAP system, load it into SQL Server, and start an Azure Data Factory pipeline as one chain of dependent jobs, with the full history in one place.
See Azure Data Factory Pipelines and On-Premises Jobs in One Monitor
Security Controls That Carry Over to Azure
JAMS Scheduler can pull credentials from Azure Key Vault, keeps encrypted variables encrypted when they’re copied between servers, and uses TLS between agents and the scheduler.
See the Information Security Summary for the full list of controls.
SOC 2® Examination Completed
JAMS Scheduler in Azure: Common Questions
Does JAMS Scheduler run in Microsoft Azure?
Can JAMS Scheduler coordinate Azure Data Factory pipelines with on-premises batch jobs?
Which Azure services does JAMS Scheduler integrate with?
Can one scheduler manage jobs across Windows, Linux, on-premises, Azure, and AWS?
Can we move an existing JAMS Scheduler database to Azure SQL?
Is JAMS Scheduler an alternative to Azure Scheduler?
How does JAMS Scheduler compare to Azure Logic Apps?
