Overview
This article describes how to integrate an ELK M1 Gold intrusion panel with the Azure access control driver. This integration allows Azure readers to control ELK alarm areas, enabling unified access and intrusion workflows.
The ELK M1 Gold supports:
- Up to 8 Areas (Partitions)
- Up to 16 Keypads / Readers
Each ELK Area can be mapped to Azure access logic using Access Control Reader Groups (ACRGs).
Prerequisites
Before beginning, ensure the following:
- ELK M1 Gold panel is online and communicating
- Azure controller and readers are already configured and functional
- You know the ELK controller address
Step 1: Enable ELK Automation in Hardware Manager
- Open Hardware Manager
- Select your Azure Driver
- Enable ELK Automation for the Azure driver
- Save changes
This step allows Azure to send a disarm command to the ELK panel.
Step 2: Assign ELK Areas to Readers
Each Azure reader that should control or reflect an ELK Area must be explicitly mapped.
- In Hardware Manager, select an ELK reader/keypad
- Locate the Area property
- Assign an ELK Area number (1–8) to the reader
- Save the configuration
Notes
- ELK supports 8 Areas total
- Multiple readers can be assigned to the same ELK Area
- Each reader represents a logical association, not a physical ELK keypad
Step 3: Create an ACRG (Access Control Reader Group)
ACRGs are used to link Azure readers and ELK Areas together for access decisions.
- Navigate to Access Levels
- Create or edit an ACRG and associate the Alarm icon to it
- Add:
- One or more Azure readers
- The corresponding ELK Area
How ELK Areas Are Addressed
ELK Areas are added to an ACRG by adding a reader reference using the following format:
ControllerAddress.AreaNumber
Example:
12.0-5
Where:
12.0= ELK controller address5= ELK Area number
This example maps ELK Area 5 on controller 12.0 into the ACRG.
Supported Capacity (ELK M1 Gold)
| Feature | Limit |
| ELK Areas (Partitions) | 8 |
| ELK Keypads / Readers | 16 |
| Azure Readers per Area | Multiple |
| ACRGs per Area | Multiple |
Common Use Cases
- Disarm ELK Areas using Azure credentials
- Synchronize intrusion status with access control events
- Centralize access and alarm management in Azure
Troubleshooting Tips
- If an ELK Area does not respond, confirm:
- ELK Automation is enabled
- The reader has an Area assigned
- The Area is correctly referenced in the ACRG
- The Azure reader is assigned to the same ACRG as the ELK Area.
- Area numbers must be 1–8
- Changes require a save to take effect