2026 Update: How To Build A Helpdesk Ticketing System With The Power Platform

This document serves as your definitive 2026 companion guide to Stacy Deere's highly regarded session, "How To Build A Helpdesk Ticketing System With The Power Platform." If you have recently reviewed her original demonstration, you already understand the core architectural philosophy. The fundamental logic of the solution remains identical today in our modern enterprise environments. You capture user data via Microsoft Forms, store those records securely in Microsoft Lists, route the operational logic using Power Automate, and visualize the resulting trends within Power BI.

However, the Microsoft 365 ecosystem has evolved dramatically over the last three years, rendering many of the manual steps from the original recording obsolete. The interfaces you observed in the 2023 recording have been completely modernized and, in some cases, entirely deprecated. Microsoft Copilot is now deeply embedded into every application layer, shifting the development paradigm from manual "click-ops" configuration to natural language generation.

Furthermore, key architectural integrations—such as the legacy SharePoint list visualization mechanism in Power BI—have been completely retired and replaced with more robust enterprise methodologies. We are now operating in the era of "Wave 3" of Microsoft 365 Copilot, which introduces agentic capabilities powered by advanced models like GPT-5.4 Thinking. These agents can execute long-running, multi-step work across your tenant, fundamentally changing how we approach citizen development.

Think of this comprehensive report as your technical translation layer. We are going to take the exact business outcomes Stacy achieved and reconstruct them using the current, production-ready interfaces available in April 2026. We will walk through each of the five demonstrations step-by-step. I will provide the precise menu paths, button names, and AI prompts you need to deploy this helpdesk system today, ensuring your approach aligns with current Microsoft governance and licensing standards.

What's Changed Since This Session

Before we begin the build process, you must understand the structural shifts that have occurred across the Power Platform and Microsoft 365. The ecosystem is no longer reliant on manual schema definition or static integration points. The table below maps the specific technologies and workflows shown in the original session to their current 2026 reality.

As you can see, almost every manual configuration step demonstrated in 2023 has been superseded by an AI-assisted counterpart. Our focus today is on leveraging these new agents to accelerate deployment while maintaining strict architectural governance.

How to Build This Today

We will now recreate all five of the core demonstrations from the original session. The overarching goal remains the same: capturing intake data, storing it reliably, routing it efficiently, and visualizing the operational metrics.

For each module below, I will explain exactly how to achieve the same result using the updated April 2026 interface. I will highlight where the new Microsoft 365 Copilot agents can save you hours of manual clicking and configuration. I will also provide direct guidance on navigating the new user interfaces introduced in the recent Fluent 2 design updates.

Demo 1: Creating a New Microsoft Form

The session showed Stacy Deere building a helpdesk intake form from scratch. She navigated to the app launcher, manually added a title and description, uploaded a logo image, and created choice fields for ticket priority with AI-suggested options.

Here is how you build that exact same form today in April 2026. Microsoft has significantly upgraded the intelligence of Forms, embedding Copilot directly into the creation experience. You no longer need to type out individual questions or manually configure choice matrices unless you explicitly want to. The entire structure can be generated through a single, well-crafted prompt.

Furthermore, Microsoft Purview Data Loss Prevention (DLP) now safeguards web searches and prompts within these Copilot experiences. This means that when your users interact with Copilot to build forms, sensitive organizational data is protected at the prompt layer.

Step-by-Step Build:

• Navigate to the Microsoft 365 App Launcher (the waffle icon in the top left corner of your browser) and select Forms.
• Do not immediately click the traditional "New Form" dropdown button. Instead, look for the Draft with Copilot prompt box prominently displayed at the top of the screen.
• Type the following prompt to generate your structure instantly: "Create an IT Helpdesk Ticket intake form. Include fields for the user's name, email, department, a detailed description of the issue, and a choice field for Priority (High, Medium, Low)."
• Click Generate. The underlying Copilot model will build the entire structure, including appropriate field types, in seconds.
• Review the generated questions. You can click on any question block to manually edit the text or adjust the settings.
• Ensure your "Priority" field is configured correctly. Click the question to expand its settings and verify the Options are strictly defined as High, Medium, and Low.
• Toggle the Required switch at the bottom of both the "Priority" and "Issue Description" questions to ensure users cannot submit blank tickets.
• To add your company logo, click on the Form Title at the top of the page.
• Click the Insert Image icon (it resembles a small mountain landscape) located to the right of the title text.
• Select Upload to browse your local machine and insert your corporate logo.

If you are building complex intake processes, you may also want to explore branching logic. In the current iteration of Forms, branching allows you to link an answer to a question that is not directly next in the linear sequence. For example, if a user selects a specific department, you can branch them to hardware-specific questions relevant only to that team. To branch the form, simply choose the "Add branching" option found in the three dots at the bottom right of any question block.

Quick Win: Lock Down The Form To prevent spam and ensure you seamlessly capture the submitter's exact Microsoft Entra ID credentials, you must adjust the form's sharing settings. Click the three dots (More form settings) in the top right corner of the screen. Select Settings. Ensure the option Only people in my organization can respond is checked, and tick the Record name box. This critical step eliminates the need for users to manually type their email addresses, reducing friction and data entry errors. Note that Microsoft Forms does not currently support making prefilled fields read-only; therefore, capturing identity via Entra ID is the most secure method.

Demo 2: Styling the Form

The session showed Stacy styling the form by selecting from a list of standard themes, applying a black color scheme, and previewing the form to ensure a professional appearance before deployment.

In 2026, the visual customization engine in Microsoft Forms is much more robust, aligning with the broader organizational branding updates rolling out across the suite. The legacy "Themes" pane has been replaced by an AI-driven "Style" pane. This new interface generates custom backgrounds and cohesive color palettes based on the context of your questions.

While the AI suggestions are impressive, corporate IT environments often require strict adherence to brand guidelines. You must know how to bypass the AI to apply specific corporate colors.

Step-by-Step Build:

• In the top right corner of your form designer, locate and click the Style icon (it resembles an artist's palette or a paintbrush).
• The modern Style pane will slide open on the right side of the screen.
• You will see several pre-generated visual suggestions based on the keywords detected in your form (e.g., tech-focused backgrounds triggered by the "help desk" terminology).
• To apply a clean, professional black theme like Stacy used, scroll to the very bottom of the Style pane and click the Customized Theme option (often represented by a '+' icon).
• Under the Color section of the customized menu, enter the exact hex code for black (#000000) or your organization's specific primary brand color. This action will update the submit buttons and core UI elements instantly.
• Under the Background section, you can upload a custom branded image or choose a minimalist geometric pattern. I advise against overly busy images, as they distract from the intake questions.
• Once styled, click the Preview button (the eye icon) at the top right of the command bar.
• Test the layout using both the Computer and Mobile view toggles at the top of the preview screen. This ensures the form remains highly legible and accessible on all devices.

By utilizing the Custom Theme feature, you ensure your helpdesk interface projects authority and aligns with your corporate identity. Remember that the user experience begins the moment they open the form; a clean, branded interface builds trust in the support process.

Demo 3: Setting up Microsoft Lists

The session showed Stacy creating a new Microsoft List from scratch to act as the primary database for the helpdesk system. She manually defined the columns, selected data types, and applied formatting to ensure the list matched the questions asked in the intake form.

Building database schemas manually is a tedious process prone to human error. Today, you can utilize the new SharePoint List Agent directly within Microsoft 365 Copilot Chat to generate your database structure using plain language. This feature, which rolled out to general availability between December 2025 and February 2026, represents a massive leap forward in rapid deployment.

Furthermore, you must be aware that the standalone Microsoft Lists mobile applications for iOS and Android were officially retired in November 2025.5 If your field technicians need to access this ticketing system on their mobile devices, they must now use the optimized browser-based experience by navigating to office.com/launch/Lists.

Step-by-Step Build (The 2026 Copilot Method):

• Open Microsoft Teams or Outlook and navigate to your unified Copilot Chat interface.
• Invoke the specific agent by typing @SharePoint list agent into the chat box. Note that if your organization is part of the Frontier program, this may display as "(Frontier)".12
• Provide a highly specific prompt that exactly matches the fields you created in your Form. Type: "@SharePoint list agent Create a SharePoint list called 'IT Helpdesk Tickets'. Include the following columns: 'Ticket Title' (Single line of text), 'Requester Email' (Person or Group), 'Issue Description' (Multiple lines of text), 'Priority' (Choice: High, Medium, Low), 'Status' (Choice: New, In Progress, Resolved), and 'Date Submitted' (Date and Time)." 12
• The agent will process the request and draft the list structure. Review the proposed columns presented within the chat window.
• If the schema is correct, instruct Copilot to save the resulting list to your IT department's primary SharePoint site or to your OneDrive.

Step-by-Step Build (The Manual Method):

If your tenant administrators have disabled the SharePoint List Agent, or if you do not currently hold a Microsoft 365 Copilot license, you must use the manual path.

• Navigate to your department's SharePoint Site or open the Lists app directly from the M365 App Launcher.
• Click the + New list button prominently displayed at the top of the screen.
• Select Blank list from the common dialog box. Name it "IT Helpdesk Tickets" and click Create.
• By default, your new list will have a single "Title" column. Click the + Add column button located to the right of "Title".
• Select Multiple lines of text from the dropdown menu and name the column "Issue Description".16 Click Save.
• Click + Add column again and select Choice. Name this column "Priority". In the column settings pane on the right, define your choices exactly as you did in the form (High, Medium, Low). Assign distinct colors to each (e.g., Red for High, Yellow for Medium). Click Save.
• Add another Choice column named "Status". Define these choices as "New", "In Progress", and "Resolved". It is critical that you set the default value to "New" so that incoming tickets are categorized correctly. Click Save.

Quick Win: Formatting the Status Column Visual cues drastically speed up the triage process. Click the down arrow next to your new "Status" column header. Select Column settings, then select Format this column. Choose the Choice pills option. This configuration applies highly visible, color-coded badges to your tickets automatically, making the list instantly readable for your technicians at a glance.

Once your list is established, you have successfully created the storage backend for your ticketing system. The next step is to stitch the front-end form to this back-end list using automated workflows.

Demo 4: Integrating Power Automate

The session showed Stacy using Power Automate to stitch the entire system together. She created a flow from a blank canvas that triggered when a form was submitted, captured the response data, created a new item in the SharePoint list, and sent out automated email notifications.

In 2026, the Power Automate home page and the flow designer interface have been completely overhauled. The legacy method of manually searching for triggers and actions has been superseded. The "Describe it to design it" feature is now powered by a mature Copilot model that not only builds the complex flow logic but also handles the underlying connection configurations on your behalf.

This is part of a broader push toward "Agentic apps," bringing Microsoft 365 Copilot directly into the flow of business processes. You must also be aware of the new Model Context Protocol (MCP) integrations, which allow applications to deliver live, interactive experiences directly within chat interfaces. While we are building a standard cloud flow today, understanding that Power Automate is moving toward these dynamic, agent-driven architectures is crucial for future-proofing your skills.

For direct guidance, refer to the official documentation on creating cloud flows using Copilot: Create a cloud flow using Copilot.

Step-by-Step Build:

• Navigate to Power Automate (make.powerautomate.com). Upon signing in, look at the left navigation pane and ensure you are on the Home tab.
• Verify you are operating in the correct environment by checking the Environment Switcher in the top right header. Flows created in one environment are isolated from others.
• Locate the large input field at the top of the page titled Create your automation with Copilot.
• To achieve the best results, you must utilize the "When X happens, do Y" semantic framework and explicitly name your intended connectors. Type the following prompt exactly into the field: "When a new response is submitted in Microsoft Forms, get the response details. Then, create a new item in my SharePoint list, and send an email notification via Outlook." 3
• Click Generate. Copilot will process the intent and present a suggested visual structure for your flow.
• Review the proposed structure carefully. It should clearly display the Forms trigger, followed sequentially by the Forms data extraction action, the SharePoint creation action, and the Outlook notification action. If this looks correct, click Keep it and continue.
• Configure Connections: The subsequent screen will verify your authentication to Forms, SharePoint, and Outlook. Ensure all icons display a green checkmark. If you see a red exclamation mark indicating a connection issue, you must select it and authenticate. Once verified, click Create flow.
• You are now operating within the modern Flow Designer. The Copilot pane will remain persistently open on the right side of the screen to assist you with further modifications.
• Configure the Trigger: Click on the first node, labeled When a new response is submitted. In the left-hand settings pane, click the dropdown for Form ID and select your "IT Helpdesk Ticket" form from the list.
• Configure the Get Response Details: Click the second node. Select the exact same Form ID. For the Response ID field, click inside the empty box. A dynamic content window will immediately appear. Select the Response Id token that is generated by the initial trigger.
• Configure the SharePoint Action: Click the Create item node.
• Select your target Site Address and your newly created "IT Helpdesk Tickets" List Name from the available dropdowns.
• The node will dynamically expand to display all the columns you created in your SharePoint list. You must now map the dynamic content from your form into these specific fields.
• Click inside the list's "Issue Description" field and select the form's "Issue Description" question from the dynamic content pop-up. Map the "Priority" form question to the "Priority" list column.
• Configure the Notification: Click the final Send an email (V2) node.
• In the To field, enter the shared email address or specific channel address of your IT support team.
• In the Subject line, type "New Ticket: " and then select the Priority dynamic content token to ensure urgency is immediately visible in the inbox.
• In the Body, compose a brief standardized message and insert both the Issue Description and Responder's Email tokens to provide full context.
• Click Save in the top command bar.
• It is highly recommended to verify the workflow logic. Click Test in the upper right corner, select Manually, and submit a test response through your live Microsoft Form to ensure the data flows seamlessly into your list and triggers the email.

Quick Win: Copilot Error Fixing Diagnosing save errors can severely disrupt your build process. In 2026, if you map a field incorrectly (such as attempting to push text into a date field) and click save, Copilot will intervene. The new runtime troubleshooting experience allows you to directly ask the Copilot pane, "Why did this save fail?" The agent will pinpoint the exact mismatched data type and offer a guided, one-click resolution, allowing you to focus on building rather than deep troubleshooting.

With the flow active, your helpdesk is now fully functional from an operational standpoint. Data is being captured and routed. The final requirement is to visualize this operational data for management review.

Demo 5: Visualizing Ticket Data Trends in Power BI

The session showed Stacy taking the raw ticket data stored in Microsoft Lists and visualizing the operational trends in Power BI dashboards. Crucially, she achieved this directly from the SharePoint interface using a built-in visualization button.

WARNING: Major Architecture Change If you are attempting to replicate this step exactly as it was shown in the 2023 recording, you will encounter a hard blocker. Microsoft officially retired the "Visualize the List" and "Visualize the Library" features from SharePoint Online in December 2025.2 You can no longer click a single button to auto-generate a transient report overlay inside the list view.

You must now transition to the modern Semantic Model Export workflow. This is not merely a workaround; it is a vastly superior enterprise methodology. The new process creates a true, persistent Power BI artifact (a semantic model) within your workspace. This allows for rigorous governance, scheduled data refreshes, and much deeper analytical capabilities than the legacy feature ever provided.

For comprehensive details on this transition, refer to the official guidance:(https://learn.microsoft.com/power-bi/connect-data/create-dataset-sharepoint-online-list).

Step-by-Step Build:

• Navigate back to your "IT Helpdesk Tickets" list within SharePoint.
• Look to the command bar at the top of the list interface. Click the Export dropdown, and then explicitly select Export to Power BI.
• A dialog box will immediately appear. You must provide a clear naming convention for your semantic model (e.g., "Helpdesk_Ticket_Model_Prod").
• Select the specific Power BI Workspace where you intend to save this model. Note: If you are operating on a free Fabric license, you are restricted to saving the model exclusively in your personal "My workspace".2
• Click Continue. Power BI will launch in a new, authenticated browser tab.
• If you are prompted regarding connection credentials, select My current credentials. This ensures the semantic model pulls the data exactly as your current account sees it within the SharePoint list.
• You will land on the details page of your newly minted semantic model.
• Click the Explore this data dropdown menu and select Auto-create report.
• Power BI's internal AI algorithm will instantly analyze your ticket data, identify mathematical patterns, and generate a comprehensive multi-visual dashboard. It will intelligently select fields like "Priority" and "Status" to build the initial chart distributions.
• Customize the Visuals: Direct your attention to the Your Data pane located on the right side of the screen. You can check or uncheck fields here to provide "hints" to the AI. If you require a specific chart showing the volume of tickets segmented by priority, simply ensure the "Priority" field and "Ticket ID" (or a standard count of items) are checked. The visuals on the canvas will regenerate dynamically to reflect your hints.
• To fine-tune a specific chart generated by the AI, hover your cursor over it and click the Personalize this visual icon. Within this sub-menu, you can alter the fundamental visual type (e.g., changing a standard bar chart into a pie chart) or adjust the aggregation logic (e.g., changing a Sum calculation to a Count).
• Once the dashboard accurately reflects your required KPIs, click Save in the top ribbon interface.
• Name the report "Helpdesk KPI Dashboard" and save it permanently to your team's designated workspace.

This report is now a live, manageable asset. Because it is backed by a dedicated semantic model, your database administrators can configure scheduled refreshes to ensure the IT management team is always looking at up-to-date metrics without manual intervention.

Furthermore, if your helpdesk requires advanced interactivity, you should explore the newly available Translytical task flows (General Availability as of March 2026). These flows allow end-users to perform actions—such as updating records or initiating workflows—directly within the Power BI report without navigating away. While this requires connecting to Fabric SQL databases or Dataverse rather than a simple SharePoint list, it represents the next evolution of operational reporting.

Licensing Quick Reference

The helpdesk solution built in this session relies heavily on the native, interconnected integrations within the Microsoft 365 ecosystem. Stacy originally built this architecture utilizing a Microsoft 365 Business Basic license. This tier remains a highly cost-effective foundation for this specific architecture, provided you rigorously understand the boundaries of the included use rights and the upcoming pricing adjustments.

Please note that Microsoft announced a global price and packaging update for these commercial suites, which will officially take effect in July 2026.23 You must factor these operational costs into your IT budget planning.

It is imperative to address the Power BI licensing gap before deployment. If your organization operates on a higher tier, such as Microsoft 365 E5, the Power BI Pro license is already included for those users, eliminating the need for the standalone add-on. Conversely, if you rely entirely on Business Basic, you must procure Power BI Pro licenses for any technician or manager who needs to consume the shared dashboard.

By following these updated 2026 procedures, you leverage the unprecedented speed of conversational Copilot agents while safely navigating the pitfalls of deprecated features. The result is a highly robust, automated, and governed helpdesk system built entirely upon your existing Microsoft infrastructure.