Freshservice is cloud-only with no on-premises deployment option. The management console is hosted on Freshworks' infrastructure with data center options in the US, EU, India, and Australia. There is no agent to install on endpoints for basic ITSM. Asset discovery uses a Discovery Probe that scans the network and imports hardware, software, and user data into the CMDB. The Discovery Probe integrates with SCCM, Azure AD, and network scanning protocols to populate the asset inventory.
Integration depth with Microsoft 365 environments is one of Freshservice's practical strengths. Azure AD integration handles user provisioning via SCIM and virtual asset discovery. The Microsoft Teams integration supports ticket creation, status updates, and approvals directly within Teams channels. SCCM integration syncs hardware and software inventory into Freshservice's CMDB. For organizations standardized on the Microsoft stack, these integrations reduce the implementation effort required to connect the ITSM platform to the existing identity and device management infrastructure.
Workflow automation uses a drag-and-drop builder with conditions, actions, and parallel approval chains. Orchestration transactions, which power integrations and automated actions beyond basic routing, are capped per tier. Teams that rely heavily on automation should model their expected orchestration volume against the tier caps before committing. Exceeding the cap means either paying overage charges or upgrading tiers for capacity rather than features.
The service catalog is available from the Growth tier upward and supports multi-department service delivery beyond IT. HR onboarding workflows, facilities requests, and legal intake forms can all be configured as service catalog items with their own approval chains and SLAs. This enterprise service management capability is a real expansion path, but it increases agent count and orchestration volume, which affects the commercial model. Plan the ESM expansion scope before locking in the tier and agent count.