Azure IoT Hub is the Microsoft cloud service that connects large numbers of devices: sensors on pumps, gateways in plant rooms, controllers in remote substations. Each device has a twin that holds its tags, the settings you want it to use and the properties it last reported. Equipment makers, utilities and facilities teams use it to manage their devices from one place. The trouble is that the hub was built for developers. A supervisor who wants to know which pump controllers are offline has to ask someone who can write a twin query.
Agentic CMMS puts Claude, ChatGPT and other AI agents in front of your IoT hub. Operations and maintenance staff ask about devices in their own words, and the agent reads the registry and twins for them.
What your AI agent can do with Azure IoT Hub
- Find silent devices. "Which devices at the Rotterdam site have not connected since yesterday?" The agent checks connection state and last activity time.
- Read reported properties. "What firmware version and battery level does every flow meter report?" The agent lists the values and points out the outliers.
- Group devices by tag. "How many devices do we have per building, and how many of them are disconnected?"
- Check a configuration. "Is the sampling interval on gateway GW-0412 the same in the desired and reported properties?" A mismatch often means a device did not accept a setting.
- Spot fault flags. "List every device whose twin reports a fault code right now."
- Update desired properties. "Set the reporting interval on the three test sensors in Hall B to five minutes." With write access, the agent changes the twins and tells you which devices confirmed.
- Prepare a site visit. "Give me the devices at the Swindon depot with their location tags and last contact time."
Azure IoT Hub with your other systems
- When a pump controller drops offline, open a work order in UpKeep for the site technician, with the device ID and last contact time.
- Ask the agent to raise an incident in ServiceNow when a gateway that serves many devices disconnects, so IT and maintenance see the same facts.
- Post a morning summary of offline and faulted devices to your maintenance channel in Microsoft Teams.
- Compare devices reporting low battery with the planned site rounds in Limble CMMS and add a battery change to the next visit.
When devices outnumber people
A hub can hold far more devices than any team can watch. The agent does the checking on request and answers with names, tags and places instead of long device IDs. That turns the hub from a developer tool into something a shift supervisor can use before the morning meeting.
Reading a twin and changing one are different tools with different rules. Owners and admins decide who may do each, every person approves their own agent, and the activity log keeps a record of every twin update.