We need to set up a helpdesk system for our commercial company's government cloud tenant. Ideally, we'd like to use something included with our Microsoft 365 G5/E5 licensing rather than purchasing another platform. I've heard that Azure DevOps can be adapted for ticketing, but I'm also considering SharePoint Lists with Power Automate. Has anyone implemented either approach, or found a better option for a basic helpdesk in this environment?
4 Answers
Before choosing a tool, define what you actually need: email or portal intake, approvals, routing, service-level tracking, asset records, reporting, knowledge articles, and audit requirements. If this is only a first ticketing system with simple intake and assignment, a SharePoint-based solution may be enough. If you need a full IT service management platform, a commercial product will usually be less painful than extending lists and workflows indefinitely.
Azure DevOps can technically be used for tickets, but it is designed around development work items rather than support operations. It may feel awkward for end users and technicians unless your organization already relies heavily on it. SharePoint and Power Automate are more natural choices if you want to stay within the existing licensing.
SharePoint Lists with Power Automate is probably the most practical built-in approach for basic ticket intake, assignment, notifications, and status tracking. Just keep in mind that you’re building and maintaining the application yourself, including forms, permissions, searching, reporting, and security trimming. It can work well for a small operation, but the effort tends to grow once people request more advanced features.
If the helpdesk is business-critical, I’d strongly consider buying a purpose-built service management platform instead of building one from scratch. Products with appropriate government-cloud or FedRAMP-authorized offerings may be a better fit, although they add licensing costs. The compliance details and available integrations can vary considerably in a GCC High environment, so verify the exact service authorization and tenant compatibility before committing.
Agreed. The cloud environment narrows the list of usable products, and getting the security, compliance, and integration setup right from the beginning is worth the cost of experienced implementation help.
That’s why I’d be cautious about treating it as a quick project. A list and a flow are easy to start, but the long-term maintenance and reporting requirements can turn it into a custom application.