Automation in system administration is experiencing a boom. The combination of Copilot, workflows, AI, and low-code platforms It's changing the way IT teams manage email, servers, user tasks, security, and integrations with other services. It's no longer just about chaining scripts together, but about designing intelligent processes that understand the context and adapt on the fly.
Thanks to Microsoft 365 Copilot, Copilot Studio, and Power Automate for desktop, it is possible Create complex workflows simply by describing in natural language what we want to happenReviewing priority emails, running PowerShell scripts, coordinating approvals, integrating Dataverse data, or connecting external services—all under the Microsoft 365 governance, security, and compliance umbrella.
The new wave of automation: AI, low code, and hyperautomation
The evolution of automation is no longer just about performing repetitive tasks. The artificial intelligence integrated into Microsoft 365 tools allows workflows to learn from data.They detect patterns and adjust when the situation changes. Instead of following a rigid script, processes can make real-time decisions: prioritizing urgent emails, classifying them, escalating incidents, or adapting actions based on user history.
With the advancement of generative AI and intelligent agents, Workflows cease to be mere sequences of steps and become "living" processes. capable of collaborating between systems, interpreting instructions in natural language, and remaining operational even when unforeseen cases arise in the initial design.
This approach leads to the so-called hyperautomationwhich consists of automating an organization's processes as much as possible by combining various technologies: AI, RPA, low-code/no-code platforms and process mining tools. In system administration, this translates into end-to-end flowsFrom the detection of an event (an email, an incident, a user request) to its resolution and registration, including approvals, notifications, and system updates.
Low-code and no-code platforms play a key role in this scenario. They allow non-technical profiles to participate in the creation and maintenance of workflowsThis reduces reliance on the IT team and accelerates the adoption of automation across the organization. With templates, pre-built connectors, and visual designers, it's much faster to translate a business process into an operational workflow.
Furthermore, process mining and task mining make it easier to understand how work is actually done on a daily basis. These tools identify bottlenecks, repetitive manual tasks (for example Convert CSV to Excel) and points susceptible to automationand allow you to measure the impact of the deployed workflows. For system administration, this means being able to prioritize what to automate first (recurring tickets, account management, email administration, etc.) and justify the improvements with data.
Workflows with the Microsoft 365 Copilot Workflows agent
Within the Microsoft 365 ecosystem, one of the pillars for creating workflows is the workflows agent integrated into CopilotThis agent allows you to define automations by describing in natural language what you want to achieve, without having to build the flow step by step from scratch.
Instead of manually adding each connector, condition, or action, Simply write an instruction like “every morning check my unread emails from the last 24 hours, classify them and send me a summary via Teams”Based on that description, the agent generates a workflow that combines Outlook, AI, Teams, and other necessary services.
With Workflows Agent you can Automate tasks in Outlook, SharePoint, Teams, Planner, and other Microsoft 365 servicesUsing data such as calendars, to-do lists, SharePoint lists, or adaptable cards in Teams to collect user information. All of this without writing code, relying on a visual designer where the generated flows can be reviewed, tested, and adjusted.
Prerequisites for using the workflow agent
To start creating workflows with Copilot, you need to meet certain requirements. The first step is to become part of the Frontier programbecause the workflow agent is initially distributed in this context. Once access is granted, the agent must be added from the Agent Store from Microsoft 365 Copilot.
The process is simple: Sign in to Microsoft 365 Copilot, and go to the “Agents” section in the sidebar.Find the workflow agent (Frontier) and add it. From then on, “Workflows” will appear as another agent in the side menu.
In terms of security, it is essential that The DLP directives include the AI Actions connector and the AI request feature in DataverseThis configuration is managed from the Power Platform admin center for the relevant environment. Additionally, to access all functionality, it's recommended to enable the SharePoint, Approvals, Teams, Planner, and Outlook connectors in your data policies.
Creating a workflow with natural language
Once the agent is available, creating a flow is a matter of a few steps. Access Microsoft 365 Copilot and select the workflow agent in the Agents section. and you write in the text box what you want to automate, with the greatest possible level of detail.
For example, we could define: “Every morning, review the unread emails in my inbox from the last 24 hours, identify the important ones, and send me a structured summary via Teams.”Copilot interprets this description and generates a workflow with a daily trigger, reading emails in Outlook, classification using AI, and sending a message to Teams.
The resulting flow includes all the necessary steps: trigger in the indicated time frame, consultation of unread emails, filtering by priority or urgency, categorization (for example, "Needs response", "FYI", "Other important ones") and compilation of a summary with sender, subject, brief description, deadlines and suggested next actions, which is sent to the user in Teams.
Once generated, the flow can be opened in the Workflows designer to review each action, adjust conditions, change the schedule, or enrich the logic with additional steps. Natural language serves as a starting point, but the designer allows for fine-tuning the automation. in detail when necessary.
Automatic connection to Microsoft 365 services
The workflow agent is capable of Detect which Microsoft 365 services to use based on what is written in the messageIf we mention "inbox" or "Outlook" in the request, it will link the flow to the user's mailbox; if we mention "Teams channel", it will ask us to choose the correct channel if there are several matches.
The description should specify the location of the Outlook inbox or mailbox where you read emails, the Teams chat or channel where the summary will be published and, if AI capabilities with Dataverse are used, the desired grouping or analysis type, for example: “group emails into categories based on whether they require a response, are informative or are relevant by deadlines”.
The agent uses the user's Microsoft 365 account to create the necessary connections. If the system does not unambiguously identify a SharePoint site or a Teams channel (because there are similar or ambiguous names), it will ask the user to confirm or select the correct resource before continuing.
Testing, monitoring, and management of workflows
Once the flow has been created, it is essential to validate it. From the workflow agent's activity tab, you can launch a manual test of the trigger.Review the execution history and check for potential errors.
When you save a flow, Copilot usually offers the option to test it immediately via chat. It is also possible to run the test from the "Test" button at the top of the designersimulating the trigger that activates the flow. After execution, it is recommended to review results, correct steps, and repeat the test until the behavior is as expected.
The activity page displays details of each instance in the flow: What trigger was executed, what actions were performed, the order in which they were processed, and at what step a failure occurred, if any.In addition, a specific execution can be opened to analyze the inputs and outputs of each action.
In the general list of workflows you can activate or deactivate each flow using the context menuThis is useful for pausing automations during maintenance or testing. From this same list, you can also permanently delete workflows, keeping in mind that the deletion cannot be undone and the automation will no longer be available.
Connectors and actions available for Workflows Agent
The workflow agent integrates with the Key Microsoft 365 services most common in management and productivity scenariosThrough connectors and predefined actions, tasks related to mail, files, lists, tasks, approvals, users, or AI capabilities can be combined.
The integrated connector includes actions such as repetition triggers or AI Actionswhich allow the application of AI models to classify, summarize, or transform information. With Outlook, you can search for meeting times, read emails, get events, create appointments, send and reply to emails, or create contacts.
In the case of SharePoint, flows can add items to lists, retrieve or delete items by filtering by different fieldsPlanner allows you to display or manage user tasks. The Approvals connector provides actions to create approval requests and await responses from approvers.
There are also actions for working with the Office 365 user connector, such as obtain a user's profile or their direct administratorand with AI-oriented Dataverse (AIB), where the AI Messaging action stands out for interacting with models and processing structured business data.
If more advanced workflows are needed or to connect to services outside of Microsoft 365, The recommendation is to use Power Automate and its extensive catalog of connectors, including those published by third parties.Workflows Agent covers the most common scenarios within the Microsoft ecosystem, while Power Automate allows you to extend automation to any compatible service.
Visibility, governance, and limitations of workflows
From the point of view of application governance and security, Administrators control the availability of workflows by configuring Microsoft 365 applications.In the Microsoft 365 admin center, within the Copilot > Settings > Agents section, you can decide whether the workflow agent is available to all users or only to specific groups.
Workflows are governed by the same security, compliance, and retention policies as the rest of Microsoft 365 applications. In the Power Platform admin center, administrators can view and manage these flows. applying standard ALM (application lifecycle) practices, such as version control, development or production environments, etc.
By default, the flows generated by the agent are hosted in the default environment of the organizationIf environment routing is enabled for Copilot Studio, these flows can be deployed in the creator's personal developer environment (PDE), thus separating testing and production more clearly.
Certain limitations must be taken into account: AI-generated workflows should be reviewed and tested before being used in production.Currently, workflows created directly in Workflows Agent cannot be shared; the set of supported connectors is limited to Microsoft 365 services and is not supported. custom connectors or from third parties through this agent.
Furthermore, Flows do not automatically correct errors present in other existing flowsAnd the use of natural language can lead to selecting the wrong SharePoint site or Teams channel if their names are very similar. Finally, in its current state, workflows from this agent are only available in English.
Agent workflows in Copilot Studio: advanced automation for administrators
Beyond the workflow agent integrated into Copilot, Microsoft offers Agent flows in Copilot Studio as a tool for orchestrating complex business processesThese are sequences of actions triggered by specific events or conditions that can act as tools for a conversational agent.
These flows are deterministic: Given the same inputs, they will always produce the same outputThis makes them very suitable for critical system administration processes where predictable and auditable behavior is required (user registration, permission management, queries to internal systems, etc.).
Copilot Studio distinguishes between “themes” and “agent flows”. The topics focus on managing the conversation with the user (questions, answers, dialogue branches) and can include background actions, while agent flows are optimized for the execution of non-conversational business processes, with deeper automation capabilities.
Although they may seem similar to Power Automate cloud flows, there are important differences. Agent workflows are designed to integrate natively with agents created in Copilot Studio.They focus on intelligent automation driven by AI and are managed under a pay-as-you-go billing model within Copilot Studio, without requiring individual Power Automate licenses.
Another key difference is sharing: Agent flows cannot be copied, shared, or assigned co-owners or execute-only permissions. In Copilot Studio, this is possible with cloud flows. However, the same agent flow can be used across multiple agents as a reusable action.
Relationship with Power Automate and premium connectors
Power Automate cloud flows remain the most flexible option when you want automate processes across multiple external services and applicationsThanks to their extensive catalog of connectors and actions, they can function independently or be called from agent flows to create comprehensive solutions.
In the case of agent flows, Premium connectors can be used without the need for additional Power Automate licenses.These are considered premium flows and their cost is managed via Copilot Studio. However, Power Automate desktop flows (desktop RPA) cannot currently be run directly from an agent flow.
If certain flows are not visible in the available list when working with Copilot Studio, it is most likely because were originally created in Power Automate and not as agent flowsTo make them appear in Copilot Studio, you need to convert them or recreate them with the specific trigger and action for agents.
To add a flow to a Copilot Studio agent, it must be a solution flow that includes the trigger “Execute a flow from Copilot” and the action “Respond to Copilot”, or its equivalent when working with agents (for example, "When an agent calls the flow" and "Respond to the agent", depending on the scenario).
Creating an agent flow as a tool for an agent
A typical case in system administration involves create a flow that acts as a tool for an agent to query external information or execute specific actionsMicrosoft documents this pattern with an example of weather forecasting using MSN Weather, which is easily extrapolated to internal system queries or monitoring APIs.
The agent flow must meet several requirements: Use the "When an agent calls the flow" trigger, include the "Respond to the agent" action, and be configured to respond in real time.To do this, the asynchronous response option must remain disabled, which means that the flow must return a response in less than 100 seconds.
Tasks that require more execution time may to be placed after the response actionWhile the workflow can continue for up to 30 days, the user interaction must be answered within that 100-second window. This is especially important for administrative automations that query slow APIs or process large volumes of data.
When you create a new agent flow directly from a topic (when adding a new tool), Copilot Studio automatically adds the necessary trigger and response actionSimply publish the flow, return to the agent, and save the changes so that the new action node is associated with the flow.
From there, the flow designer allows you to add actions such as Call APIs, query service connectors, process the received information, and prepare the response for the agent.In the weather example, input parameters such as "City" and "Postal Code" are added, along with actions that call the MSN Weather connector, ultimately responding with a summary of the day, location, and probability of rain.
Connection management and execution with user credentials
In authenticated agents, cloud flows used as part of generative orchestration plans or called from themes can to run with the user's own credentialsThis allows for respecting permissions and access scopes. In compatible channels, the use of these flows does not require additional agent-level configuration; users can manage their connections when interacting with the agent.
In Power Platform environments protected with customer-managed keys (CMK), There are restrictions when running cloud flows with user credentials in orchestration plans or from themes. In these cases, it is recommended to configure the run-only option to use specific connections and not the "User-provided run-only" mode.
Copilot in Power Automate for desktop: interface automation and scripts
In addition to cloud flows and agent flows, System administration can be supported by Copilot in Power Automate for desktop to generate automations that interact with the user interface, local files, Automate tasks in Excel, scripts, etc., using natural language.
This functionality allows Create new desktop workflows or add steps to existing workflows simply by describing what you want to dosuch as “reading data from an Excel spreadsheet and sending it by email” or “running a PowerShell script and saving the result to a file.” Copilot interprets the scenario, builds the necessary actions, and inserts them into the designer.
For now, the ability to “create flows with Copilot” on desktop is available in preview. for environments located in the United StatesWhile the capabilities to answer product questions and summarize actions and subflows are available in multiple regions (Europe, Asia Pacific, Latin America, etc.). Furthermore, only support is available for professional or educational accountsnot personal Microsoft accounts.
When working with desktop workflows, Copilot groups actions generated by functionality, marks them with start and end comments for easy identification, and, when it detects intent to automate interface or browser actions, Insert placeholders so the user can launch the recorder and capture real-world interactions with applications.
It is also possible Use Copilot to add new actions to an existing flowFrom the designer, the appropriate mode is selected in the side panel (for example, "Add a step"), the desired result is described, and Copilot inserts the actions at the end of the flow or just below the selected action.
How to write good applications for desktop copilot
The quality of the generated flows depends largely on the clarity of the message. It is recommended to be as specific as possible, including file paths, email accounts, subjects, and key parameters.A generic message like “Email an Excel file” can leave required fields blank and cause design errors.
In contrast, a request of the type “Send an email to sales@contoso.com from accounting@contoso.com with the subject 'Contoso Sales Data' and attach the file C:\\contoso\\contoso.xlsx” It allows Copilot to automatically complete the necessary parameters for email actions and avoid errors.
If the first attempts do not produce the expected result, it is advisable to Refine the instruction, add missing details, or divide the task into two or three more specific messages.Microsoft's own documentation offers example instructions for compressing folders, processing text files, working with SQL databases, or combining Excel and email into a single workflow.
Copilot in desktop workflows also includes a “generative responses” capability that allows ask questions about the product and receive explanations based on official documentationalways with links to the corresponding reference for further information.
Another interesting capability is that of “Summarize actions and subflows”This helps you quickly understand what a specific part of a desktop workflow does. You can request summaries of a single line, several actions, or entire subflows, adjusting the level of detail (a few sentences or a more extensive explanation) and referencing line numbers or subflow names.
Copilot limitations and governance in desktop workflows
Copilot in Power Automate for desktop still has several restrictions. It only supports a subset of the actions available on the platform (clipboard, databases, Excel, email, scripting, flow control, variables, etc.), and the supported language is English.
It cannot be used with personal accounts like someone@live.com; You need to authenticate with a professional or educational accountAdditionally, at present, only environments located in the United States can use all of Copilot's flow creation capabilities.
In the governance section, Power Platform administrators can Disable the ability to generate responses with Copilot from the corresponding settings, and even disable the sending of user feedback to Microsoft from the tenant settings.
Regarding privacy and rights, administrators can View, export, and delete user-submitted comments From the Microsoft 365 admin center, in the Health > Product feedback section, which helps to meet internal or regulatory requirements.
If you want to completely prevent users from using any Copilot features within the organization, It is possible to coordinate this with Microsoft support.although it is normally managed through standard product configurations and licensing.
By integrating Agent Workflows, agent flows in Copilot Studio and Copilot in Power Automate for desktop, system administration teams have a wide range of options to automate everything from simple user tasks to complex business processes. The challenge is no longer so much the available technology, but designing good processes, governing them correctly, and writing clear requests that allow Copilot to build robust, secure, and truly useful workflows. in the day-to-day operations of the organization.
